Click to See Complete Forum and Search --> : LAN works, PPP doesn't (route.conf?!)


ZacMacCrac
11-02-2000, 12:41 PM
Hi,
I'm on a dial-up ISDN connection with dynamic IP address and also have a LAN. I'm using SUSE 6.4.
I've configured the LAN with IPs 192.168.0.x, thats necessary. The dial up internet connection is using dynamic IPs, so I need 192.168.0.99 as dummy for PPP and 192.168.0.1 as point to point partner for PPP (for dyn. IP assignment).
Problem is, I'm already using 192.168.0.x for LAN, so I wonder if that's allowed, I don't think so.
Well, now I deactivated the LAN conn, dialed in just for testing, everything fine until it comes to exchanging packets, I can't surf the internet, I can't ping anyone in the net. (Yes, nameserver's IP is correct.)
Someone told me it would be the routing table that caused the problems. I have no idea how to configure the route.conf properly, nor do I know how to fix the LAN<->PPP<->IP problem. I'm completely lost, please help me.... ;'(

knute
11-02-2000, 12:48 PM
I have a similar setup, though, I'm not trying to share the connection yet...

I have a ppp connection w/a regular modem and also a lan w/my wifes computer....

the PPP connection has a different netmask than my lan connection...
The 192.168.0.x is a class C network (netmask 255.255.255.0), whereas my dialup connection is a class A (i think) (netmask 255.255.255.255)....

ifconfig will tell you the netmasks and such...

I am curious why you are trying to set up the internet connection on your internal network... You can use ipmasking to share the connection...

------------------
Knute
Email: knuteh@yahoo.com
ICQ: 53979509

[This message has been edited by knute (edited 02 November 2000).]

ZacMacCrac
11-02-2000, 01:07 PM
I'm not setting up the isp connection on the LAN... I'll be using squid to set my machine up as a proxy. But I just NEED the LAN's IPs to be 192.168.0.x, cause the LAN is a bit bigger...
so if I use 255.255.255.0 as netmask for the LAN, and 255.255.255.255 for the dial up (you always use that one for internet, don't you?!), will I then be able to use 192.168.0.x on both networks without getting into trouble?