Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After much searching and quite a bit of frustration(read hair ripped out by the root). I have decided to come here.
For about two weeks now I have been running linux as my server. One of my NIC cards has a F%*KING problem with staying up. It seems that after about 8 hours of inactivity I have to reboot my server to get my network card to respond again. Its the DFE-550TX. It acts like that card goes to sleep, but its more like it dies completely. Nothing seems to wake it(much like that Uncle that comes over around Thanksgiving, and falls asleep on the couch and no matter what you try he stays asleep). Its about to turn me back to M$. Winduhs has its problems, but at least I only had to reboot it once a week.
for most distros you would look in /var/log/messages but there may be some other interesting stuff in /var/log so check it out.
I have some other questions:
1 What distro do you use?
2 when the nic is failing what is returned by the ping command? ping the device and loopback then maybe your gateway if the other 2 respond.
3 Any other nics in the system?
4 Was that output from while it was failing?
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.301 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.210 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.205 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.204 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.205 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.201 ms
On the machine attempting to connect
"Request timed out"
Um loopback(127.0.0.1)? gateway?
3)yes
eth0 - internet connection
eth1 - failing one
eth2 - second machine connected. No problems with it.
lspci -v
Quote:
00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at d400 [size=256]
Memory at ea141000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at e7000000 [disabled] [size=64K]
Capabilities: [50] Power Management version 2
00:09.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
Subsystem: Intel Corp. EtherExpress PRO/100+ Management Adapter
Flags: bus master, medium devsel, latency 64, IRQ 5
Memory at ea142000 (32-bit, non-prefetchable) [size=4K]
I/O ports at d800 [size=64]
Memory at ea000000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at e8000000 [disabled] [size=1M]
Capabilities: [dc] Power Management version 2
00:0a.0 Ethernet controller: D-Link System Inc DL10050 Sundance Ethernet (rev 12)
Subsystem: D-Link System Inc DFE-550TX
Flags: bus master, medium devsel, latency 64, IRQ 9
I/O ports at dc00 [size=128]
Memory at ea140000 (32-bit, non-prefetchable) [size=512]
Expansion ROM at e9000000 [disabled] [size=64K]
Capabilities: [50] Power Management version 2
4)yes that was what was listed by ifconfig
in /var/log/syslog
Quote:
Aug 15 22:01:13 ip<my ip> kernel: IN=eth0 OUT= MAC= SRC=<hidden>.0.179.161 DST=(Mostly my ipending in 255) LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=520 DPT=520 LEN=32
Aug 15 22:01:13 ip<my ip> kernel: IN=eth1 OUT= MAC= SRC=192.168.1.1 DST=(Mostly my ipending in 255) LEN=72 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=520 DPT=520 LEN=52
Aug 15 22:01:25 ip<my ip> kernel: IN=eth0 OUT= MAC= SRC=<hidden>.0.179.161 DST=(Mostly my ipending in 255) LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=32773 DPT=137 LEN=58
Aug 15 22:01:26 ip<my ip> last message repeated 2 times
Aug 15 22:01:26 ip<hidden>-0-179-161 kernel: IN=eth1 OUT= MAC= SRC=192.168.1.1 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=32773 DPT=137 LEN=58
Aug 15 22:01:26 ip<hidden>-0-179-161 kernel: IN=eth1 OUT= MAC=00:90:27:a3:45:64:00:10:dc:f0:7b:84:08:00 SRC=192.168.1.4 DST=192.168.1.1 LEN=90 TOS=0x00 PREC=0x00 TTL=128 ID=41332 PROTO=UDP SPT=137 DPT=32773 LEN=70
Aug 15 22:01:26 ip<hidden>-0-179-161 kernel: IN=eth1 OUT= MAC= SRC=192.168.1.1 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=32773 DPT=137 LEN=58
I havent been able to find a definate answer on this but from I gather, this error you are recieving is saying that the kernel is dropping the packet because it beleives that the source is invalid.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.