-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 16 March 2004 23:27, Jim Radford wrote: > Ok. Seeing as I've been using this ADSL for over a year, with the same > network cable - I could be right in saying it's not the cable or the > connector, right? You can't get to there from here. "It used to work" doesn't give it a free pass from ever failing. > How could I check for a Dos from a Trojan? Would a tcpdump show me? I think the DoS idea was before the ifconfig errors were discovered. tcpdump is a cool tool that puts your ethernet adapter into promiscuous mode, where it responds to every packet on the wire no matter what the packet type or IP address. To the extent that your PC can keep up, it then filters in software the packets you are interested in (by default, all) and displays them in the console. Using this from a second PC on a hub, you can then see if the long delays in the test PC were preceeded by a DNS lookup, ICMP actions, etc. Many times it has given me a clue when I was clueless :-) But with the wire errors, I don't think that's where your problems are coming from. Can you describe more fully the network topology on your side, exactly what kind of routers, hubs or switches, etc are in use. - -Andy - -- Find your answer without waiting for replies.... Searchable list archives at http://marc.theaimsgroup.com/?l=fedora-list&r=1&w=2 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAV+NnjKeDCxMJCTIRAgayAJ9+GujijTzGH3KDM9MaGUIgIsfTVgCdGGWl T2MWe5b/pCGGonpKpiDEdqI= =m8Cc -----END PGP SIGNATURE-----
