Subject: Re: TCP to linux side
From: Brian Foddy (bkfoddy@soc.nwa.com)
Date: Fri Feb 04 2000 - 11:55:03 MST
First I don't know much about ethertap, but just looking
at your notes, what is your route set to. You should
have a default route to eth0 otherwise it won't know
how to get out of the Linux machine.
Jeff Whitaker wrote:
>
> Hi: I'm also having trouble getting the IPMASQ/ethertap connection working.
>
> I've compiled IP MASQ and ethertap into the kernel (2.2.15pre4), and followed
> the instructions given by Takashi Oe. On the linux side, here is what
> ifconfig, netstat and ipchains report:
>
> ifconfig gives:
>
> eth0 Link encap:Ethernet HWaddr 00:50:E4:45:3C:08 inet
> addr:140.172.156.40 Bcast:140.172.156.255 Mask:255.255.255.0 UP
> BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:24150
> errors:0 dropped:0 overruns:0 frame:0 TX packets:19496 errors:0
> dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100
> Interrupt:42 Base address:0x1000
>
> lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP
> LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:10 errors:0 dropped:0
> overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0
> carrier:0 collisions:0 txqueuelen:0
>
> tap0 Link encap:Ethernet HWaddr FE:FD:00:00:00:00 inet
> addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 UP
> BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0
> dropped:0 overruns:0 frame:0 TX packets:644 errors:0 dropped:0
> overruns:0 carrier:0 collisions:0 txqueuelen:0
>
> netstat -rn gives:
>
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt Iface
> 192.168.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 tap0
> 140.172.156.40 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
> 140.172.156.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 tap0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 140.172.156.200 0.0.0.0 UG 0 0 0 eth0
>
> ipchains -L gives:
>
> Chain input (policy ACCEPT):
> Chain forward (policy DENY):
> target prot opt source destination ports
> MASQ all ------ 192.168.0.0/24 anywhere n/a
> Chain output (policy ACCEPT):
>
> I've created the ethertap device:
>
> jsw]# ls -l /dev/tap0 crw-rw-rw- 1 root root 36, 16 /dev/tap0
>
> But, when I run MOL (0.9.39) with enet_interface: tap0 (and the TCP/IP settings
> suggested by Takashi) I can't connect to anything. I can ping 192.168.0.0, but
> nothing else. If I use normal networking in MOL (eth0) I can telnet to the
> linux side (192.168.0.1), so I think the ip masq part is working. I know quite
> a few people have this working, so can anyone give me any ideas?
>
> -Jeff
>
> --
> Jeffrey S. Whitaker Phone: (303)497-6313
> NOAA-CIRES Climate Diagnostics Center FAX : (303)497-7013
> 325 Broadway, Mail Code R/CDC1 Email: jsw@cdc.noaa.gov
> Boulder, CO, USA 80303-3328 Web : http://www.cdc.noaa.gov/~jsw
This archive was generated by hypermail 2a24 : Wed Mar 01 2000 - 00:06:20 MST