Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Networking problems

Status
Not open for further replies.

Sen7inel

IS-IT--Management
Feb 14, 2001
90
FI
Hello,

I'm pretty new to Linux, and just finished installing Debian 3.0 r1. The problem is that I can't connect to anything. It doesn't seem to route correctly, and I can't even ping my own vlan.

Let's say my ip is 61.58.26.213, netmask 255.255.255.192, and gw 61.58.26.161. Now, when I check out the routing table it only shows localnet with "*" gw. Also, I can't ping any other computers near me, like 61.58.26.215. Ok then, when I connect my laptop (Win98) with a cross-over cable and set its ip to 61.58.26.212, I can ping it just fine from the Linux box and everything else also works between these machines. Then, when I disconnect the x-over cable and plug the one which goes to the switch downstairs, I get exactly _ONE_ ping reply from this .215 machine I know should be responding.

The normal cable is ok and the NIC should be ok.

What gives?
 
first, make sure that networking is at least working.

type ifconfig and make sure there is a entry for lo and an entry for each nic.

ie eth0.


 
You also need to add a default route to your routing tables
[tt]
route add default gw 61.58.26.161
[/tt]
so that [tt]'route -n'[/tt] will show something that looks like
[tt]
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 61.58.26.161 0.0.0.0 UG 0 0 0 eth0
[/tt]
jaa
 
> route add default gw 61.58.26.161

This gives me SIOCADDRT: Network is unreachable.

As for ifconfig, there are valid(looking) entries for both eth0 and eth1. eth1 works fine (192.168.0.1), and I use it all the time to get to the box (no i/o devices)..

This problem with the 61.58.26.192-network was there before I installed the second nic.
 
Yet some more hints.. I have a Windows machine and the Linux machine here. If I unplug the network cable from Windows computer, connect the freshly booted Linux to the network, I can once again ping ONCE a host in my own network (61.58.26.193-254). Now, after this the Linux system is silent, so I switch the cable back to the Win computer. I can now ping all computers in my own network succesfully from Windows, but can't go any further untill I explicitly ping 61.58.26.193, which apparently is a router of some sort.. Ok, so I check out the arp table and what do I find out: both 61.58.26.193 and .161 have the same MAC address. Setting the .193 as gw on the Linux box doesn't help.

Anyone? (or just tell me if I'm making a damn fool out of myself)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top