On Fri, 7 Jan 2000, Rajiv Ghai wrote:
|For example in my set-up the local address is 192.168.0.13 and the remote
|bogus IP address is 192.168.0.1. Now when I boot-up, pppd daemon is started
|with interface ppp0 and I get the following routes:
|
|Destination Gateway Interface
|192.168.0.1 0.0.0.0 ppp0
|127.0.0.0 0.0.0.0 lo
|0.0.0.0 192.168.0.1 ppp0
|
|I use an ipchains firewall to deny output from my linux box so that
|although the routes for the interface ppp0 is up, my DNS server (running on
|the same box) does not actually fire-up the demand dialing connection to
|the net.
|
|Now if and when a user connects to my box, I assign him a dynamic address
|192.168.0.21 and get the following additional route
|
|192.168.0.21 0.0.0.0 ppp1
|
|Now my linux box also runs a Apache server, so if the user requests a local
|page he gets it from my box. If he wants a site on the internet then I open
|the firewall and demand dialing establishes a link ppp0 to the internet.
|
|I find my original default route 192.168.0.1 replaced by dynamic ip-address
|assigned by the ISP.
So at this point you have
Destination Gateway Interface
xxx.xxx.x.x 0.0.0.0 ppp0
127.0.0.0 0.0.0.0 lo
0.0.0.0 xxx.xxx.x.x ppp0
192.168.0.21 0.0.0.0 ppp1
where xxx.xxx.x.x is the remote IP address at the ISP.
|Upto this point everything works fine until the user disconnects and I find
|that the route from 192.168.0.21 (ppp1) gets deleted - no problem. But
And here you have
Destination Gateway Interface
xxx.xxx.x.x 0.0.0.0 ppp0
127.0.0.0 0.0.0.0 lo
0.0.0.0 xxx.xxx.x.x ppp0
|after some time my default route gets deleted and demand dialing doesnt
|work. I think this is because the next incoming connection from
|192.168.0.21 is now automatically assigned interface ppp0. I find I have
|only two entries for routing ie.
|192.168.0.21 0.0.0.0 ppp0
|127.0.0.0 0.0.0.0 lo
This is where I'm lost. The ppp0 interface shouldn't be deleted until
the pppd process running in the demand mode is explicitly killed.
That pppd process shouldn't die just because a call-in disconnects
and the call-in pppd process dies. If the demand pppd process is
still alive when the second call-in connection is made then the ppp0
interface should still be up and the second call-in should use ppp1
interface.
|I tried to run routed and it seemed to help in keeping the interfaces alive
|but I kept getting error messages that there were packets from an unknown
|router. Based on your advice I have now disabled routed.
You shouldn't need a routing daemon with the possible exception of
complex networks.
|Hence my questions on how to control the routes which are automatically
|deleted. Like I said, maybe my understanding of how it is supposed to work
|is completely wrong and I would really appreciate any advice.
I believe you are certainly justified in assuming that the demand pppd
would remain running and that the ppp0 interface would not be deleted
when the pppd process servicing an incoming connection terminates.
But I'm not set up to make tests to verify that belief or to verify
your results.
---
Clifford Kite Not a guru. (tm)
[EMAIL PROTECTED] Not even close.
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
