As you can see, if the routing is set up it is quite possible to
have a local eth0 interface up and running and the ppp link via
martian_modem talking to the Internet - which is why I was a bit confused
by insistence you must take the other interfaces down for `martian' to
work.
root@emma:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:08:02:68:5B:1D
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::208:2ff:fe68:5b1d/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:43424 errors:0 dropped:0 overruns:0 frame:0
TX packets:29994 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:50523450 (48.1 MiB) TX bytes:2539610 (2.4 MiB)
Interrupt:10
irda0 Link encap:IrLAP HWaddr 00:00:00:00
NOARP MTU:2048 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:8
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
LOOPBACK MTU:16436 Metric:1
RX packets:767 errors:0 dropped:0 overruns:0 frame:0
TX packets:767 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:42896 (41.8 KiB) TX bytes:42896 (41.8 KiB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:80.189.151.152 P-t-P:80.189.66.8
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:56 errors:1 dropped:0 overruns:0 frame:0
TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:7501 (7.3 KiB) TX bytes:5987 (5.8 KiB)
sit0 Link encap:UNSPEC HWaddr
00-00-00-00-FF-FF-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
root@emma:~# ping www.linmodems.org
PING www.linmodems.org (192.203.178.7) 56(84) bytes of data.
64 bytes from www.linmodems.org (192.203.178.7): icmp_seq=1 ttl=54
time=251 ms
64 bytes from www.linmodems.org (192.203.178.7): icmp_seq=2 ttl=54
time=247 ms
64 bytes from www.linmodems.org (192.203.178.7): icmp_seq=3 ttl=54
time=243 ms
64 bytes from www.linmodems.org (192.203.178.7): icmp_seq=4 ttl=54
time=250 ms
--- www.linmodems.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 243.486/248.272/251.528/3.151 ms
root@emma:~# ping kirsten
PING kirsten (192.168.1.7) 56(84) bytes of data.
64 bytes from kirsten (192.168.1.7): icmp_seq=1 ttl=64 time=0.892 ms
64 bytes from kirsten (192.168.1.7): icmp_seq=2 ttl=64 time=0.166 ms
64 bytes from kirsten (192.168.1.7): icmp_seq=3 ttl=64 time=0.178 ms
--- kirsten ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.166/0.412/0.892/0.339 ms
root@emma:~#
root@emma:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
ap01-s08.dial.g * 255.255.255.255 UH 0 0 0
ppp0
localnet * 255.255.255.0 U 0 0 0
eth0
default * 0.0.0.0 U 0 0 0
ppp0
It's still temperamental about which modem cable it will
believe in (and no, I haven't mixed up a USB Robotics cable with a
standard one).
Anyhow, back to seeing if I can do anything with that IRDA
interface - for no particularly other good reason than it's hurting my
head pondering on whether the separation between kernel and userspace will
really work in practise.
PS Patrick: the bash seems to be working fine thus far.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-|message from the cookie daemon|
The formulation and solution of problems change throughout
history, throughout our own lifetimes, and even through our
re-readings of texts.
--
John Pate <johnny@xxxxxxxxxx>
Edinburgh, Scotland (home PC)
Disclaimer: I've probably changed my opinions by the time you read this
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
