PPP dialin (pppd) not routing some of our IPs. Help!

Tony Toole (linuxlists@usa.net)
Fri, 17 Apr 1998 07:47:49 -0700


Hello there, we are a small ISP and are moving from NT to Linux. We have
some very frustrating problems with PPP dialin (via pppd) and need some
assistance.

We have a class 'C' network, currently allocating 16 IPs to the new Linux
box, which will be used for dialin lines. (Via an Equinox modem pool, which
works great)
The problem we are having is that some of our IPs are not being routed when
we dial into them, using Win95's TCP/IP dialout. (IE. We can't ping the
net, only the host dialin server).

The IPs are active, and work as expected in the NT server.

For instance, here are the IPs we have tried, and the results we got:
Netmask used: 255.255.255.224, however 255.255.255.0 produce identical
results.
Host computer: 207.81.87.190
Gateway: 207.81.87.161

207.81.87.170: Won't route.
207.81.87.171: Works fine.
207.81.87.172: Works fine.
207.81.87.173: Won't route.
207.81.87.174: Works fine.
207.81.87.175: Works fine.
207.81.87.176: Works fine.
207.81.87.177: Works fine.
207.81.87.178: Won't route.
207.81.87.179: Won't route.
207.81.87.180: Won't route.
207.81.87.181: Won't route.
207.81.87.182: Works fine.

All the tests were performed using a Win95, WinNT4, MAC and another Linux
computer, and all have the same problems when connected.

All the IPs in question are not being used by any equipment and work fine
when used in other computers, and even work as the Linux dialin server's
host IP.

The software we've tried (all produce the exact same results):
RedHat 5.0, 4.2, 4.1.
pppd dialing versions 2.3.2, 2.3.3, 2.3.4.
Linux kernels (using RH5 and RH4.2 as base installs) 2.0.27, 2.0.30,
2.0.31, 2.0.32, 2.0.33, 2.1.91, 2.1.95 and 2.1.96.

The pppd options file:
asyncmap 0
proxyarp
lock
crtscts
modem
asyncmap 0
ms-dns 207.81.87.190
ms-dns 205.206.217.33

The additional command line parameters added for PAP logins:
-chap +pap auth login :<port ip>

This is added for scripted logins:
-chap

The ethernet adapter us fully functional and works great under Linux. This
problem ONLY happens for dial-in PPP connections, the IPs work in any other
situation.

If this is a pppd bug, please let me know if there is a patch available, or
perhaps an alternative PPP daemon.

Please! If anybody can help, or know what is happening, please contact me.
This is rather urgent, deadlines are a bummer.
If all possible, reply to tony.t@cyberdude.com and/or tony@valemount.com

Thanks for any help in this matter.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu