ethernet error?
Just recently, I'm getting a most peculiar message popping up on my screen about once every 30 seconds or so: DROPPED IN= OUT=eth0 SRC=192.168.0.2 DST=192.168.0.255 LEN=129 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=631 LEN=109 I have three machines on my network, and only this machine (192.168.0.2) is displaying this message. It only shows up when I'm at the console - I don't see it in X, not even in an Xterm. I'm beginning to suspect a hardware error. Some of you might recall that last week I also asked about another message that was popping up on my screen (but very infrequently): spurious 8529A interrupt: IRQ7 A couple of people wrote back that this was a hardware error. I don't know if there is any relationship between this spurious error and the ethernet error. I'm curious if anybody has a clue about what's going on. thanks in advance, Robert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ethernet error?
On Mon, 2003-12-22 at 20:39, Robert Storey wrote: Just recently, I'm getting a most peculiar message popping up on my screen about once every 30 seconds or so: DROPPED IN= OUT=eth0 SRC=192.168.0.2 DST=192.168.0.255 LEN=129 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=631 LEN=109 this is a firewall log, iptables or ipchains. I have three machines on my network, and only this machine (192.168.0.2) is displaying this message. It only shows up when I'm at the console - I don't see it in X, not even in an Xterm. I'm beginning to suspect a hardware error. Some of you might recall that last week I also asked about another message that was popping up on my screen (but very infrequently): spurious 8529A interrupt: IRQ7 you can work with this. i had once this kind of error, but worked fine for days. A couple of people wrote back that this was a hardware error. I don't know if there is any relationship between this spurious error and the ethernet error. I'm curious if anybody has a clue about what's going on. thanks in advance, Robert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ethernet error?
Hello Robert Storey ([EMAIL PROTECTED]) wrote: Just recently, I'm getting a most peculiar message popping up on my screen about once every 30 seconds or so: DROPPED IN= OUT=eth0 SRC=192.168.0.2 DST=192.168.0.255 LEN=129 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=631 LEN=109 I have three machines on my network, and only this machine (192.168.0.2) is displaying this message. It only shows up when I'm at the console - I don't see it in X, not even in an Xterm. Looks like some software is trying to broadcast using udp and source port 631. This is used be the internet printing protocol, so I guess Cups or some other printing server software is causing the traffic, and your firewall is dropping it. If you use Cups on that machine, check the configuration file /etc/cups/cupsd.conf. best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 Registered Linux User #267976 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ethernet error?
On 22 Dec 2003 at 19:39, Robert Storey wrote: I'm beginning to suspect a hardware error. Some of you might recall that last week I also asked about another message that was popping up on my screen (but very infrequently): spurious 8529A interrupt: IRQ7 A couple of people wrote back that this was a hardware error. I don't know if there is any relationship between this spurious error and the ethernet error. I'm curious if anybody has a clue about what's going on. I get those spurious interrupt errors on boot too. Doesn't seem to be a problem for me. I wouldn't worry about it personally. -- Martin J Hooper http://www.martinjh.pwp.blueyonder.co.uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ethernet error? [SOLVED]
Ahhh, that's it, the firewall! I am my own worst enemy. I installed Guarddog, and I was blocking IPP (Internet Printing Protocol). Unblocking it made the nasty messages go away. Thanks to everyone who replied. Without your help, I probably would have replaced my motherboard instead! I still highly recommend Guarddog. regards happy holidays, Robert On Mon, 22 Dec 2003 13:22:14 +0100 Andreas Janssen [EMAIL PROTECTED] wrote: Hello Robert Storey ([EMAIL PROTECTED]) wrote: Just recently, I'm getting a most peculiar message popping up on my screen about once every 30 seconds or so: DROPPED IN= OUT=eth0 SRC=192.168.0.2 DST=192.168.0.255 LEN=129 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=631 LEN=109 I have three machines on my network, and only this machine (192.168.0.2) is displaying this message. It only shows up when I'm at the console - I don't see it in X, not even in an Xterm. Looks like some software is trying to broadcast using udp and source port 631. This is used be the internet printing protocol, so I guess Cups or some other printing server software is causing the traffic, and your firewall is dropping it. If you use Cups on that machine, check the configuration file /etc/cups/cupsd.conf. best regards Andreas Janssen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Ethernet Error
Try as root /sbin/route add -net 192.168.1.0 netmask 255.255.255.0 window 16384 eth0 assuming your eth0 has an IP in the range 192.168.1.1 to 192.168.1.254 If that works fine then add it to something in /etc/init.d -- From: Steve[SMTP:[EMAIL PROTECTED] Sent: Wednesday, 31 May 2000 1:32 PM To: Ron Rademaker Cc: debian-user@lists.debian.org Subject:Re: Ethernet Error Ok. That sounds like a plan. When I run route, I see an entry for the localnet associated with eth0 and an entry for the lo (no gateway assigned to either). I'm not completly familiar with route tables. Could I get a hand with them? What shows for route is: DestinationGatewayGenmaskFlagsMetricRef UseIface locatnet* 255.255.255.224U 0 01 eth0 127.0.0.0 * 255.0.0.0U 0 01 lo I might also add that the activity LED for the on the card ON solid. - Original Message - From: Ron Rademaker [EMAIL PROTECTED] To: Steve [EMAIL PROTECTED] Cc: debian-user@lists.debian.org Sent: Tuesday, May 30, 2000 6:10 PM Subject: Re: Ethernet Error Why do you think the problem is with the card? What about your route table, is all correct there? And ipchains, you don't have them so you can't get anything out or in can you? What exactly does it say when you try to ping? Sound like a route problem to me! Ron Rademaker On Tue, 30 May 2000, Steve wrote: Hello, I'm using Slink on an AMD-233 powered computer. I have a 3Com905-TX Ethernet card installed. The modules appears to be loading with the kernel as eth0. When I run ifconfig I can see the the eth0 card with the correctly assigned IP information. The problem: I can't ping to the cards IP address, but I can ping localhost. Any ideas on troubleshooting the card further? Thanks in advance. -Steve -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Ethernet Error
Your netmask doesn't look good to me, try editing your /etc/init.d/network (or /etc/network/interfaces, I don't know which one you are using) and change the netmask of your localnet to 255.255.255.0 Ron Rademaker On Tue, 30 May 2000, Steve wrote: Ok. That sounds like a plan. When I run route, I see an entry for the localnet associated with eth0 and an entry for the lo (no gateway assigned to either). I'm not completly familiar with route tables. Could I get a hand with them? What shows for route is: DestinationGatewayGenmaskFlagsMetricRef UseIface locatnet* 255.255.255.224U 0 01 eth0 127.0.0.0 * 255.0.0.0U 0 01 lo I might also add that the activity LED for the on the card ON solid. - Original Message - From: Ron Rademaker [EMAIL PROTECTED] To: Steve [EMAIL PROTECTED] Cc: debian-user@lists.debian.org Sent: Tuesday, May 30, 2000 6:10 PM Subject: Re: Ethernet Error Why do you think the problem is with the card? What about your route table, is all correct there? And ipchains, you don't have them so you can't get anything out or in can you? What exactly does it say when you try to ping? Sound like a route problem to me! Ron Rademaker On Tue, 30 May 2000, Steve wrote: Hello, I'm using Slink on an AMD-233 powered computer. I have a 3Com905-TX Ethernet card installed. The modules appears to be loading with the kernel as eth0. When I run ifconfig I can see the the eth0 card with the correctly assigned IP information. The problem: I can't ping to the cards IP address, but I can ping localhost. Any ideas on troubleshooting the card further? Thanks in advance. -Steve -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Ethernet Error
Hi folks, It's possible that the original poster has been allocated a block of 32 IP addresses from someone in which case the mask of 255.255.255.224 is correct, changing from a 27-bit to 24-bit mask would cause more problems than it cures. Your netmask doesn't look good to me, try editing your /etc/init.d/network (or /etc/network/interfaces, I don't know which one you are using) and change the netmask of your localnet to 255.255.255.0 DestinationGatewayGenmaskFlagsMetricRef UseIface locatnet* 255.255.255.224U 0 01 eth0 127.0.0.0 * 255.0.0.0U 0 01 lo Cheers, Tom
Ethernet Error
Hello, I'm using Slink on an AMD-233 powered computer. I have a 3Com905-TX Ethernet card installed. The modules appears to be loading with the kernel as eth0. When I run ifconfig I can see the the eth0 card with the correctly assigned IP information. The problem: I can't ping to the cards IP address, but I can ping localhost. Any ideas on troubleshooting the card further? Thanks in advance. -Steve
Re: Ethernet Error
Why do you think the problem is with the card? What about your route table, is all correct there? And ipchains, you don't have them so you can't get anything out or in can you? What exactly does it say when you try to ping? Sound like a route problem to me! Ron Rademaker On Tue, 30 May 2000, Steve wrote: Hello, I'm using Slink on an AMD-233 powered computer. I have a 3Com905-TX Ethernet card installed. The modules appears to be loading with the kernel as eth0. When I run ifconfig I can see the the eth0 card with the correctly assigned IP information. The problem: I can't ping to the cards IP address, but I can ping localhost. Any ideas on troubleshooting the card further? Thanks in advance. -Steve -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Ethernet Error
Ok. That sounds like a plan. When I run route, I see an entry for the localnet associated with eth0 and an entry for the lo (no gateway assigned to either). I'm not completly familiar with route tables. Could I get a hand with them? What shows for route is: DestinationGatewayGenmaskFlagsMetricRef UseIface locatnet* 255.255.255.224U 0 01 eth0 127.0.0.0 * 255.0.0.0U 0 01 lo I might also add that the activity LED for the on the card ON solid. - Original Message - From: Ron Rademaker [EMAIL PROTECTED] To: Steve [EMAIL PROTECTED] Cc: debian-user@lists.debian.org Sent: Tuesday, May 30, 2000 6:10 PM Subject: Re: Ethernet Error Why do you think the problem is with the card? What about your route table, is all correct there? And ipchains, you don't have them so you can't get anything out or in can you? What exactly does it say when you try to ping? Sound like a route problem to me! Ron Rademaker On Tue, 30 May 2000, Steve wrote: Hello, I'm using Slink on an AMD-233 powered computer. I have a 3Com905-TX Ethernet card installed. The modules appears to be loading with the kernel as eth0. When I run ifconfig I can see the the eth0 card with the correctly assigned IP information. The problem: I can't ping to the cards IP address, but I can ping localhost. Any ideas on troubleshooting the card further? Thanks in advance. -Steve -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
potato ethernet error
I'm running potato (i386) with the 2.2.10 kernel primarily for samba and netatalk services. It appears that one Mac on the network (a 9500/120 with OS 8.1) causes the same error message to start popping up on the console - eth0: tx interrupt but no status - and file transfers slow to a crawl. /proc/net/dev shows an increase in transmit collisions but no errors. The Linux ethernet card is an Intel EtherExpress 16 and the Mac is using the built-in ethernet. Does anyone have any suggestions on how I can try to fix this? Thanks, Craig Daniels [EMAIL PROTECTED]
ethernet error
Hi, i just run 'modconfig' to install the network driver, it found the problem. My ethernet is called SMC8000 16-Bit ISA(10Mbp), which it can run Novell IPX and TCP/IP software. SMC9194: You shouldn't use auto-probing with insmod! loading device 'eth0' ... /lib/modules/2.0.29/net/smc9194.o :init_modules Device or resource busy Installation failed. Any clue? Kam -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: ethernet error
Hi Kam, you have to specify io port and interrupt for your ethernet card. Via 'modconf': Under net/your_card/Install in the box below Please enter bla bla bla write the parameters io=0 irq=n (replace xxx and n with the proper values, maybe you can even omit irq) Via '/etc/conf.modules: Open the file and give the following parameters alias eth0 name of ethernet module without trailing '.o' options wd io=0 irq=n with xxx and n as above Regards, Andree -- | Institute of Geophysics phone: +49 40 4123 4389 ANDREE LEIDENFROST | University of Hamburg fax: +49 40 4123 5441 Geophysicist | Bundesstrasse 55 e-mail: [EMAIL PROTECTED] | D-20146 Hamburgwww: www.app-geoph.dkrz.de -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
pppd and ethernet error (dialup)
Hi, I'm trying to get my new debian system fully configured, i've setup everything fine so far. I thought everything was going fine till i tried to dialup my isp to run dselect to update some things this is what i got out of the log file. Feb 18 20:46:36 uk pppd[1065]: Serial connection established. Feb 18 20:46:37 uk pppd[1065]: using interface ppp0 Feb 18 20:46:37 uk pppd[1065]: Connect: ppp0 -- /dev/ttyS1 Feb 18 20:46:41 uk pppd[1065]: local IP address 194.247.41.27 Feb 18 20:46:41 uk pppd[1065]: remote IP address 194.247.41.30 Feb 18 20:46:41 uk pppd[1065]: ppp not replacing existing default route to eth0[0.0.0.0] Feb 18 20:46:41 uk pppd[1065]: Cannot determine ethernet address for proxy ARP So the connection establishes ok, it something to do with internal network running on 10.0.0.1 on eth0. Has anybody got any ideas how i can get around this or fix it ? Thanks, Chris. -- Chris Bond [EMAIL PROTECTED] SysOp of Logics BBS, Hereford, UK. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: pppd and ethernet error (dialup)
Feb 18 20:46:41 uk pppd[1065]: ppp not replacing existing default route = to eth0[0.0.0.0] Feb 18 20:46:41 uk pppd[1065]: Cannot determine ethernet address for = proxy ARP You have the option 'proxyarp' added, either in your ppp/options file or in diald configuration file (if you're using diald). just remove (comment it) that options, and you're home free. Ørn Einar Hansen [EMAIL PROTECTED] [EMAIL PROTECTED] home+fax; +46 035 217194 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: pppd and ethernet error (dialup)
Feb 18 20:46:37 uk pppd[1065]: Connect: ppp0 -- /dev/ttyS1 Feb 18 20:46:41 uk pppd[1065]: local IP address 194.247.41.27 Feb 18 20:46:41 uk pppd[1065]: remote IP address 194.247.41.30 Feb 18 20:46:41 uk pppd[1065]: ppp not replacing existing default route to eth0[0.0.0.0] So the connection establishes ok, it something to do with internal network running on 10.0.0.1 on eth0. Has anybody got any ideas how i can get around this or fix it ? Yes, it does have something to do with your internal network. Since you probably already have a route in the routing table, ppp won't add a new one. Try doing this after ppp is up and running: route add default gw 194.274.41.30 metric 1 This should make net trafic go over ppp by default, but your local net should (hopefully) still work. Feb 18 20:46:41 uk pppd[1065]: Cannot determine ethernet address for proxy ARP Sorry, don't know anything about that error -- - John Larkin - [EMAIL PROTECTED] - http://aij.st.hmc.edu/~jlarkin -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: pppd and ethernet error (dialup)
On Tue, 18 Feb 1997 21:12:47 GMT Fingers ([EMAIL PROTECTED]) wrote: I'm trying to get my new debian system fully configured, i've setup everything fine so far. I thought everything was going fine till i tried to dialup my isp to run dselect to update some things this is what i got out of the log file. Feb 18 20:46:36 uk pppd[1065]: Serial connection established. Feb 18 20:46:37 uk pppd[1065]: using interface ppp0 Feb 18 20:46:37 uk pppd[1065]: Connect: ppp0 -- /dev/ttyS1 Feb 18 20:46:41 uk pppd[1065]: local IP address 194.247.41.27 Feb 18 20:46:41 uk pppd[1065]: remote IP address 194.247.41.30 Feb 18 20:46:41 uk pppd[1065]: ppp not replacing existing default route to eth0[0.0.0.0] Feb 18 20:46:41 uk pppd[1065]: Cannot determine ethernet address for proxy ARP So the connection establishes ok, it something to do with internal network running on 10.0.0.1 on eth0. Has anybody got any ideas how i can get around this or fix it ? You probably have your default route going through your ethernet before starting pppd, and pppd doesn't remove it. Either: 1) Remove the ether defaultroute (it's not necessary if you've got only one network, and if you've just got a few of them, add manual routes) 2) Set up the defaultroute in an ip-up script and re-establish the previous one in an ip-down script. Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
