Linux-kernel mailing list archive 1997-48,: 2.1.X PPP/routing problem

# 2.1.X PPP/routing problem

Jimmie Farmer (calvin@malchick.com)
Sun, 30 Nov 1997 13:32:53 -0800 (PST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Chris Powell: "Re: 2.0.29 is it time to upgrade?"
- Previous message: Doug Ledford: "Re: Triton DMA"

I have noticed this since I started using 2.1.X, and just though I
would ask here about why this is happening.

I have a dedicated PPP connection, and I just leave my box logged
in 24/7. I am now getting a weird NETMASK, even though the one I want to
use is plainly listed in my /etc/ppp/options file. Even thought the
netmask is incorrect, I can still get out to the 'Net, though. The
netmask is properly reported in 2.0.X.

Here is the output of my ifconfig:

lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:140 errors:0 dropped:0 overruns:0 frame:0
TX packets:140 errors:0 dropped:0 overruns:0 carrier:0 coll:0

ppp0 Link encap:Point-to-Point Protocol
inet addr:204.122.18.33 P-t-P:204.122.16.25 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:552 Metric:1
RX packets:20410 errors:2 dropped:0 overruns:0 frame:0
TX packets:23824 errors:0 dropped:0 overruns:0 carrier:0 coll:0

ppp0:0 Link encap:Point-to-Point Protocol
inet addr:204.122.18.34 Bcast:0.0.0.0 Mask:255.255.255.240
UP RUNNING NOARP MULTICAST MTU:552 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0

Notice that my VIF (invoked from /etc/ppp/ip-up) does have the
correct netmask, even though ppp0 doesn't.

I am using ppp2.3.1, and here is what I see in "dmesg":

pppd forgot to specify netmask

even though it is in my /etc/ppp/options file:

/dev/modem
57600
crtscts
netmask 255.255.255.240
defaultroute 204.122.18.33:
mtu 552
mru 552
asyncmap 0x0
persist
connect /usr/sbin/ppp-on

I am *fairly* certain that I have made all the neccessary changes
to my rc script, and I am using net-tools 1.421, but I have been wrong
before. ;-)

Another thing I see on bootup is:

SIOCADDRT no such device

so this leads me to believe I have FOBAR'ed something, but I can't
find it, so I am asking you folks for suggestions.

Yes, I have read the Changes file, as well as routing.txt and
policy-routing.txt, and have made the correct adjustments, as far as I can
tell.

P133
currently running 2.1.67
all required upgrades met, as per Doncumentation/Changes
ppp 2.3.1
my assigned IP range is 204.122.18.32-48, hence the
255.255.255.240 netmask

Thanks in advance for any tips.

Sincerely,
Jimmie Farmer

Jimmie Farmer | It is by the fortune of God that, in this country,
Techno Geek/Musician | we have three benefits: freedom of speech, freedom
calvin@malchick.com | of thought, and the wisdom never to use either.
http://www.malchick.com/ | -- Mark Twain

- Next message: Chris Powell: "Re: 2.0.29 is it time to upgrade?"
- Previous message: Doug Ledford: "Re: Triton DMA"