Very late summary here. Thanks to Kurt Ludwig for responding. The solution
that I ended up using to get a route added when the defaultroute option for
pppd didn't work was to add this to my connect script:
route add -net 192.168.1 192.168.1.1
and this to my hangup script:
route delete -net 192.168.1 192.168.1.1
These commands add/delete a route for the 192.168.1.0 network. The message:
default route ioctl(SIOCADDRT): File exists
meant that there was already a default route configured. As there was
already a default route configured it would not let me add another, go
figure. As for why the netmask was different between the different DU
boxes, I still don't know. My dial-up works so I am not inclined to chase
it down at present,but if I can find an answer I will update. Orignal post
below.
############################################################################
###########
Hello there I have a dial up connection that I am troubleshooting. I
have
two DU 4.0d boxes that dials into a modem and the connection is working
properly. Here is an ifconfig of boxa after the connect script is run:
ppp0: flags=51<UP,POINTOPOINT,RUNNING>
inet 10.110.3.9 --> 192.168.1.1 netmask ffffff00 ipmtu 1500
Here is the connect script:
pppd -d user username /dev/tty01 19200 connect 'chat -v "" atdt5551234
CONNECT "\c"' defaultroute
Boxa works fine. I can telnet to another box on the other side, no
problem.
I have the same connect script on another computer, same OS.
Here is the ifconfig of boxb:
ppp0: flags=51<UP,POINTOPOINT,RUNNING>
inet 10.110.3.9 --> 192.168.1.1 netmask ff000000 ipmtu 1500
The netmask is different. I don't think that this is a problem,
however, I
did use the netmask flag to set it to 255.255.255.0 and still I could
not
connect to a computer on the other side of the modem. Why would the
netmask
be different with the same script and same dial-in source? Also there
is a
line that shows up in the ppp-log file that is different:
default route ioctl(SIOCADDRT): File exists
This line does not show up in boxa, but does in boxb, the one that does
not
work. Why doesn't the defaultroute option add a route? It does on
boxa. I
guess it is because of this line, but what 'File' exists? I did a:
traceroute 129.168.1.19
traceroute to 192.168.1.19 (192.168.1.19), 30 hops max, 40 byte
packets
1 10.110.0.1 (10.110.0.1) 5 ms 3 ms 4 ms
2 192.168.2.29 (192.168.2.29) 51 ms 43 ms 35 ms
3 192.168.35.10 (192.168.35.10) 123 ms 101 ms 122 ms
So, obviously it is trying to reach 192.168.1.19 through its default
gateway
and not through the ppp interface with the same network. If I do:
route add -host 192.168.1.19 192.168.1.1
I can telnet, ping etc. but shouldn't this be covered by the
defaultroute
option on my connect script? This is going to be an automated dialup
operation that will be on many boxes so I want to know why it works on
one
and not the other. I don't want to have to make up different work
arounds
for every box.
Thanks,
Trevor Osatchuk
Process Solutions Canada Ltd.
Support and Integration Analyst
(780) 452-2227 Ext. 286
trevor.osatchuk_at_pscl.com
Received on Thu May 24 2001 - 16:02:08 NZST