2-way dial-on-demand ppp problems
Steven Freed
under BSD/OS 4.0.1. What I mean by this is I have a machine at a
remote site. When there is traffic destined from it to our network,
it brings up the ppp link to us, if we have traffic destined to
the remote machine, then we bring up the link to it.
I have set up many "one directional" dial-on-demand links with no
problems. It is this dual direction that is got me stumped.
The ppp.sys file on the remote machine has the following demand entry in
it:
magic:\
:interface=0:\
:debug-all:\
:idle-timeout=300:\
:device=/dev/tty03:\
:phone-number=@magic:\
:s0=\r:e0=ogin:f0=\r:\
:s1=Pacme\r:e1=word:\
:s2=xxxxxx\r:\
:tc=Demand:
This is my standard dial-on-demand entry and it works fine.
When we bring up the link from our local net to the remote host, the
following ppp.sys entry is used:
Pacme:\
:idle-timeout=300:\
:debug-all:\
:tc=Dialin:
After the first time we bring up the link from our end and after
it idles out, we can no longer bring up the link from the remote
side. In the beginning, it was because the "Dialin.down" script
was doing a "ifconfig $INTERFACE inet -remove down" so the ppp0
interface was being removed. I commented out this stuff and now
the "Dialin.down" script is basically a NULL script. Now the interface
not removed, but is marked "down". I cannot, for the life of me,
figure out what is causing this.
Any hints or suggestions would be welcome.
Other useful information:
The local network has a Portmaster PM-2 that handles all the local
inbound and outbound ppp connections. Its IP address is 204.134.12.13.
No problems there.
The remote machine has a default route to 204.134.12.13 that is
added after the "daemon ppp -bd magic" in the /etc/netstart file.
/etc/netscripts/addr-map on the remote machine has the following lines:
LOCAL 192.168.169.1
magic 204.134.12.13
Pacme 204.134.12.13
When the remote machine is booted, an ifconfig -a looks like this:
(with no ppp links established)
exp0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
link type ether 0:90:27:2e:35:e9 mtu 1500 speed 100Mbps
media auto (100baseTX) status active
inet 192.168.169.1 netmask 255.255.255.0 broadcast 192.168.169.255
lo0: flags=8009<UP,LOOPBACK,MULTICAST>
link type loop mtu 4352
inet 127.0.0.1 netmask 255.0.0.0
ppp0: flags=8051<UP,POINTOPOINT,MULTICAST>
link type ppp mtu 1500 speed 115.2kbps
inet 192.168.169.1 --> 204.134.12.13 netmask 255.255.255.0
It stays like this and the remote machine can connect into us untill after
the first time our network dials into it. After that connection times out,
then an ifconfig on the remote machine looks like this:
exp0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
link type ether 0:90:27:2e:35:e9 mtu 1500 speed 100Mbps
media auto (100baseTX) status active
inet 192.168.169.1 netmask 255.255.255.0 broadcast 192.168.169.255
lo0: flags=8009<UP,LOOPBACK,MULTICAST>
link type loop mtu 4352
inet 127.0.0.1 netmask 255.0.0.0
ppp0: flags=8010<POINTOPOINT,MULTICAST>
link type ppp mtu 1500 speed 115.2kbps
inet 192.168.169.1 --> 204.134.12.13 netmask 255.255.255.0
As you can see, ppp0 is no longer "UP". This is in where the problem lies.
How can I make this all work?
TIA,
--
Steven.
--
To unsubscribe, send 'unsubscribe' to bsdi-user...@mailinglists.org
Archives of this list can be found at: http://www.nexial.com/mailinglists/