Re: [SLE] Re: 6.4 > Routing Problems?

This looks very strange indeed!!! What you are trying to do is to tell your system that the ROUTE specified is the ROUTE TO the the interface for all IP packets FOR/TO that particular IP network (logical network) The default is for everything else to go to ppp0 Type route -n you should have something like 123.456.789.012 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 192.168.0.0 0.0.0.0 255.255.255.0 ... eth0 ... 0.0.0.0 123.456.789.012 ... ppp0 That is a route TO the ppp0 interface and the default route TO the ppp0 interface. Type ifconfig ppp0 If there is a result then THAT is the interface, not pppd!!! Ping each interface to test your routing THEN ping distant nodes. Regards, Bruce.

Do you have your network defined in /etc/networks? I had the exact same problem and it was because I overlooked that particular file.

Christopher Reimer

On Thu, 21 Sep 2000, j b wrote:

...

Thanks. That cleaned up the /etc/route.conf. I still cannot ping the ISP. It dials, and sends out packets, but nothing comes back.

/etc/route.conf 127.0.0.1 0.0.0.0 255.0.0.0 lo 192.168.0.0 0.0.0.0 255.255.255.0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 eth1 default pppd

IP forwarding is set to "yes"

--- Bruce wrote:

...

Likewise, this is a mess.

Your default is pointing to (routing) to 192.168.99.99 when the IP address is 38.26.whatever...

Be consistent.

on eth0 192.168.0.2/255.255.255.0 <--- note the zero. Below you are two different versions. on eth1 192.168.1.2/255.255.255.0 <--- DIFFERENT NETWORK...

You are confusing your system. For example, unless you specify explicit routes for each IP address (a nightmare), your system won't know where to send the packets.

Suggestion...

Specify NETWORK 192.168.0.0 on eth0 and 192.168.1.0 on eth1 Both have netmasks of 255.255.255.0 Enable the ethernet cards with these parameter.

/sbin/ifconfig eth0 inet 192.168.0.1 netmask 255.255.255.0 up /sbin/ifconfig eth1 inet 192.168.1.1 netmask 255.255.255.0 up

(The broadcast address will be established from the netmask)

route add -net 192.168.0.0 dev eth0 route add -net 192.168.1.0 dev eth1

Now you should be able to ping any local IP address. Tidy your /etc/hosts and test again LOCALLY.

Set up your ppp interface and as part of it specify the default ROUTE to that interface.

route add default dev ppp0

ping your ISP as a test rather than a web site. Quicker.

Be careful. You both should be looking at IP chains to protect yourselves. Do this asap. Regards, Bruce.

...

I have the same problem but did get ping to an external ISP to dial the ISP by changing the /etc/route.conf to something like:

default 192.168.99.1 # modem 192.168.0.0 255.255.255.0 192.168.0.2 eth0 # local net 127.0.0.0 255.255.255.255 192.168.0.2 lo

The FAQ on http://www.sangoma/fguide.htm is more useful than the others.

But I still need help. I can reach the net, but get no reply for ping or http requests. here is my info:

I am not able to get my linux gateway set up correctly. It is SuSE linux 6.3 acting as gateway for Windows machines. Ping from either machine seems to work. But it fails to dial the ISP.

configuration files are /etc/hosts 192.168.0.2 linux.box 192.168.0.3 windows.box 192.168.0.9 linux.box extra ethernet card 192.168.99.99 pppd

/etc/route.conf 127.0.0.0 0.0.0.0 255.255.255.0 lo 192.168.0.2 0.0.0.0 255.255.255.255 eth0 default 192.168.99.99 192.168.0.3 192.168.0.2 255.255.255.255 192.168.0.0 192.168.0.2 255.255.0.0

ifconfig shows eth0, eth1, ppp0 (on 38.26.183.153)

the windows machine is set as: IP: 192.168.0.3 dns: 207.217.126.81 netmask: 255.255.255.255 gayeway: 192.168.0.2

What am I doing wrong?

...

Hello Kester,

Thanks for your reply. However resolv.conf only comes into play when you start using DNS rather than IPs, (although resolv.conf is set up as well). I have no trouble resolving names to IPs, as 192.168.1.1 (the gateway) runs a local caching nameserver. My trouble is even if I just use IP addresses, I can't access anything on the Internet.

ping 192.168.1.1 --> no problem at all } LAN IP ping 192.168.1.2 --> no problem at all } LAN IP (etc. etc.)

As soon as I try to reach an external (Internet) host:

ping 212.67.203.133 --> ping: sendto: Network is unreachable ping www.suse.com --> ping: sendto: Network is unreachable ping www.linux.org --> ping: sendto: Network is unreachable

I hope that clarifies what my problem is?

--Lee

Monday, August 21, 2000, 11:15:11 AM, you wrote:

KC> I could be wildy wrong, but doesn't /etc/resolv.conf need to have IP KC> addresses in it even if it accesses the net via another machine? Maybe you KC> forgot it? Just a hopeful guess...

KC> On Thursday, September 21, 2000 9:41 AM, Lee Smallbone KC> [SMTP:lee@smallbone.com] wrote:

...

> Hi there, > > Having bought SuSE 6.4 about 3 months ago I finally freed up

--- Lee Smallbone wrote: the

...

...

> machine I have been waiting to install it on. The installation went > relatively smoothly. I have got it to recognize my network card and > traffic flows freely within the LAN. > > However: As soon as I try to access the Internet with the machine, it > complains Network Unreachable (if using ping for instance.) I've set > the default gateway to 192.168.1.1, which is the other SuSE (6.0) > machine that does the dialing and the NAT'ing. Every other machine > (Win9x) can access the Internet ok, so I know it's a problem with the > SuSE 6.4 machine. As I say I can ping and telnet (where applicable) > any machine on the local network, just I can't seem to reach ANYWHERE > on the Internet, even whilst using IP addresses. > > What am I doing wrong? > > > Best regards, > Lee Smallbone > lee@smallbone.com > > > > -- > To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com > For additional commands send e-mail to suse-linux-e-help@suse.com > Also check the FAQ at http://www.suse.com/support/faq

KC> -- KC> To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com KC> For additional commands send e-mail to suse-linux-e-help@suse.com KC> Also check the FAQ at http://www.suse.com/support/faq

Best regards, Lee mailto:lee@smallbone.com

__________________________________________________ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com

Also check the FAQ at http://www.suse.com/support/faq

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq