Can't ping outside of DSL modem with Linux machine

[tankman1989]

I just did a new install of Linux and i'm having trouble pinging outside of my network. I am able to with windows machines but not from my Linux box. I tried rebooting the router and Linux machine but I get the same thing - nothing.

The machine has 4 gigabit ports, 2 onboard and 2 on a card. Only 2 are active, the onboards and they both have an IP via DHCP. Both are hooked into the gigaswitch.

[teksquad]

Post:

ifconfig

route-n


Also are both active nic's receiving ip's ,receiving ip's via dhcp on the same subnet? What is the ICMP error your are getting? "Destination Unreachable"? Are you pinging by ip address or by host name?

Can you ping your own interface? 127.0.0.1

[tankman1989]

Wow, I got it to work by pulling out one Cat5 cable and restarting the network on the Linux machine. Does that make sense? Why would 2 network cards on one network be interfering with anything outside the DSL modem? I have a Windows machine that has 2 NIC's plugged in and it works fine. I had another linux box plugged in with 2 NIC's hooked up as well and it was fine.

Any ideas?

[teksquad]

May be an issue with both nic's configured with the same default gateway. Normally you wouldnt put both nic's on the same machine in the same subnet unless your where bridging or bonding them together to make one "logical" interface. So the box may be confused on which nic to send traffic from. I can't see the routing table on the linux box, but I am curious if it tries to put 2 default routes in there since both nic's are configured with the same default gateway.

[nightkingdoms]

You might also have problems if both cards are the same brand. It happens sometimes.

[StableSolutions]

I've seen this with windows before, where it pulls a notorious 169.x.x.x IP (frozen / invalid) Ip address... 2 network cards both fighting for an IP at the same time on the network could foul that up for you. Seems you got it fixed though.

[SouthernTech]

Originally Posted by StableSolutions

I've seen this with windows before, where it pulls a notorious 169.x.x.x IP (frozen / invalid) Ip address... 2 network cards both fighting for an IP at the same time on the network could foul that up for you. Seems you got it fixed though.

The 169 IP range is just a failsafe mechanism, rather then a frozen/invalid. The reasoning behind is that any IP address is better then no IP address. APIPA is the name of the mechanism and can be disabled via registry. But yes, its a DHCP error usually.

I guess I'm just nitpicking to contribute somewhat >.>