I've done what I suspect many have, which is to build a 2.2.x kernel
on top of slink, making the minimal changes outlined below. I have no
problems except with the one machine at work that is connected to the
ethernet and has a modem. If this machine runs 2.0.36 (all my others
run 2.2.10), PPP between home and work works; if it runs 2.2.10,
there's some sort of ARP failure (and the mask is wrong, lines marked ^).
At work 2.0.36 (I've removed the packet/collision/memory lines)
eth0 Link encap:Ethernet HWaddr 00:A0:24:B8:63:B5
inet addr:888.888.92.23 Bcast:888.888.93.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
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
ppp0 Link encap:Point-to-Point Protocol
inet addr:888.888.92.23 P-t-P:888.888.92.28 Mask:255.255.254.0
UP POINTOPOINT RUNNING MTU:1500 Metric:1
888.888.92.28 0.0.0.0 255.255.255.255 UH 0 0 1 ppp0
888.888.92.0 0.0.0.0 255.255.254.0 U 0 0 70 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 1 lo
0.0.0.0 888.888.92.1 0.0.0.0 UG 1 0 143 eth0
? (888.888.92.1) at 08:00:02:07:04:66 [ether] on eth0
? (888.888.92.21) at 00:60:97:51:31:05 [ether] on eth0
? (888.888.92.26) at 00:A0:24:93:4D:8E [ether] on eth0
? (888.888.92.29) at 00:10:4B:46:4B:C2 [ether] on eth0
? (888.888.92.28) at 00:A0:24:B8:63:B5 [ether] PERM PUP on eth0
At work 2.2.10
eth0 Link encap:Ethernet HWaddr 00:A0:24:B8:63:B5
inet addr:888.888.92.23 Bcast:888.888.93.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
ppp0 Link encap:Point-to-Point Protocol
inet addr:888.888.92.23 P-t-P:888.888.92.28 Mask:255.255.255.255
/^^^^^\
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
/^^^^^\
888.888.92.28 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
888.888.92.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0
0.0.0.0 888.888.92.1 0.0.0.0 UG 1 0 0 eth0
? (888.888.92.1) at 08:00:02:07:04:66 [ether] on eth0
? (888.888.92.26) at 00:A0:24:93:4D:8E [ether] on eth0
? (888.888.92.28) at * PERM PUP on eth0
/^\
The machine at home has a similarly strange ifconfig for ppp0, but
that doesn't stop it working on the internet. But I haven't tested
whether the laptop can work through its ethernet link.
At home 2.2.10
eth0 Link encap:Ethernet HWaddr 00:10:4B:45:46:E2
inet addr:888.888.92.28 Bcast:888.888.93.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
eth0:1 Link encap:Ethernet HWaddr 00:10:4B:45:46:E2
inet addr:777.777.197.254 Bcast:777.777.197.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
ppp0 Link encap:Point-to-Point Protocol
inet addr:888.888.92.28 P-t-P:888.888.92.23 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
888.888.92.23 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
777.777.197.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 888.888.92.23 0.0.0.0 UG 0 0 0 ppp0
? (888.888.92.23) at * PERM PUP on eth0
I've read www.debian.org/releases/2.1/running-kernel-2.2
and installed www.debian.org/~rcw/2.2/netbase/netbase_3.12-2_i386.deb
but am not using the other things like dhcp, pcmcia, isdn, bootpc,
diald.
I've removed the redundant route commands from /etc/init.d/network.
At home, I delete the redundant route to the .92 network that
2.2.x makes, and resolv.conf is filled/emptied by ip-up/down.
I've noticed that /proc/sys/net/ipv4/ip_forward is set to 1 in 2.0.36
and 0 in 2.2.10 by default so I changed it to 1 but with no effect.
What have I missed?
Cheers,
--
Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151
Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA
Disclaimer: These addresses are only for reaching me, and do not signify
official stationery. Views expressed here are either my own or plagiarised.
