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 Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Linux routing problem.

Status
Not open for further replies.

jxfish2

Technical User
Jan 24, 2002
183
US
I finally got rid of my RedHat 7.2, and installed SuSE 8.1... ( I really hate RedHat... Even more than windows... )

My router came up on the first attempt... Incredible... ( I've always like SuSE better... I only use it, because it's so widely used here in the U.S... )

However, I still have 2 issues remaining...

1) I have 2 windows machines, 2 other linux machines, a Solaris box, and an HP-UX box on the internal LAN...

Both of the windows machines are making it out to the internet just fine, through my newly installed router...

But, for some reason, neither of my remaining linux boxes seem to be able to ping the internal gateway, let alone make it out to the internet... ( I can ping the gateway from both windows boxes... ) ( I haven't even tried to turn the Solaris or HP boxes on lately... )

Any ideas of why I can't see the gateway from my linux boxes?

2) Getting the router to accept my VPN connections... ( So far, I haven't tried... One thing at a time... I want to get access to the internet, from each of the linux boxes, before I go that next step... )

TIA

JCF
 

Can you show us a 'netstat -rn' output??
And a traceroute output??

Thanks
Cheers Henrik Morsing
IBM Certified AIX 4.3 Systems Administration
 
thumbs up to SuSE 8.1.. i am a SuSE user myself.. and it's phat!!!!... i don't know why people still use Dead Rat...

to answer your question, we need to see your routing table on your other Linux boxes... they could have cached the previous default router, although i have only seen this on FreeBSD.. but, u never know..

like Morsing asked...send us your netstat -rn output..

good luck..
 
One of the other linux boxes is another SuSE 8.1 system, and the other is a RedHat 7.1 system...

Both of these boxes are at home, and I'm currently at work...

I'll have to wait until this evening to check them...

Just so you know...

All 4 of these systems ( Both Windows boxes and both Linux boxes ) were working with the LinkSys router that I had on here previously.

Unfortunately, the LinkSys router wouldn't work with the VPN router at my place of work... And, since I have to support various systems at work, I decided to try using Linux as the router, as it's much more versatile, and configurable, than an off-the-shelf hardware product...

TIA

JCF
 
Good morning,

As requested, here's the output of a "netstat -rn" and a "traceroute", from one of the internal linux boxes:

netstat -rn

Destination Gateway Genmask Flags MSS Window IRTT IFACE
192.168.0.0 0.0.0.0 255.255.255.0 U 40 0 0 ETH0
127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo
0.0.0.0 192.168.0.1 0.0.0.0 UG 40 0 0 ETH0

traceroute 192.168.0.1

1 TKredhat.my.domain (192.168.0.175) 3000.334 ms !H 3012.048 ms !H 3002.001 ms !H

In short,

My internal workstation address is: 192.168.0.175

My internal gateway is: 192.168.0.1

My netmask is: 255.255.255.0

My internal network is set to: 192.168.0.0

My broadcast address is set to: 192.168.0.255

These same settings, where applicable, are set on my windows machines also.

But, the windows machines are going out through the router / gateway just fine...

It's only the internal linux boxes that aren't going out...

They can't even ping the gateway: 192.168.0.1

I checked /etc/sysconfig/network-settings/ifcfg-eth0, and each of the settings listed above are correct...

( I can't remember if the directory is called "network-settings" or "network-something"... But, I did check the file; ifcfg-eth0. )

Any help would be much appreciated...

TIA

JCF
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top