Menu
▾
▴
Re: [coLinux-users] Colinux ping all windows ifaces, cannot ping itself nor any external address
|
From: Mitch B. <wm...@ag...> - 2004-10-30 22:40:38
|
Try enabling the loopback interface "lo". To do that in Debian, you need these two lines in /etc/network/interfaces= : auto lo eth0 iface lo inet loopback Salvador Vicente Petit Mart=ED wrote: >Hi, I just installed colinux 0.6.1 with tap networking in an windows 200= 0 box. > >Basically, I have managed to ping the windows cap interface (192.168.224= .1) and >the windows external network interface (158.42.52.78). The windows machi= ne >pings the colinux interface (192.168.224.40) and I managed to telnet to = the >daytime port and get a return string from the colinux. > >Now the weird things... > >Colinux cannot ping itself (it gives error) and also is not able to teln= et >itself also. It is also not able to ping any external address (hangs for= ever) >with the exception of the windows external network address. > >This is a excerpt of the tap networking of the conf file: > ><network index=3D"0" type=3D"tap" /> > >I do not think it has nothing to do with it but... > >The "ifconfig" and "route" results in the colinux: > >eth0 Link encap:Ethernet HWaddr 00:43:4F:4E:45:30 > inet addr:192.168.224.40 Bcast:192.168.224.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > >Destination Gateway Genmask Flags Metrics Ref Use Iface >192.168.224.0 * 255.255.255.0 U 0 0 0 Eth0 >default 192.168.224.1 0.0.0.0 UG 0 0 0 Eth0 > >The "ipconfig" and "route print" results in the windows 2000: > >Tap adaptor: > > DNS suffix..........................:. > IP Address..........................: 192.168.224.1 > Network mask........................: 255.255.255.0 > Gateway.............................: > >Ethernet adaptor: > > DNS suffix..........................:upv.es > IP Address..........................: 158.42.52.78 > Network mask........................: 255.255.252.0 > Gateway.............................: 158.42.55.250 > > >Iface list: >0x1........................................MS TCP Loopback iface >0x2...00 ff 0c f2 7c 0c TAP VPN Adapter (Microsoft Packet Scheduler) >0x3...00 02 a5 d9 eb 59 Compaq Ethernet NIC > >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D >Rutas activas: >Destino de red M scara de red Puerta de acceso Interfaz Mtri= ca > 0.0.0.0 0.0.0.0 158.42.55.250 158.42.52.78 = 1 > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 = 1 > 158.42.52.0 255.255.252.0 158.42.52.78 158.42.52.78 = 1 > 158.42.52.78 255.255.255.255 127.0.0.1 127.0.0.1 = 1 > 158.42.255.255 255.255.255.255 158.42.52.78 158.42.52.78 = 1 > 192.168.224.0 255.255.255.0 192.168.224.1 192.168.224.1 = 1 > 192.168.224.1 255.255.255.255 127.0.0.1 127.0.0.1 = 1 > 192.168.224.255 255.255.255.255 192.168.224.1 192.168.224.1 = 1 > 224.0.0.0 224.0.0.0 158.42.52.78 158.42.52.78 = 1 > 224.0.0.0 224.0.0.0 192.168.224.1 192.168.224.1 = 1 > 255.255.255.255 255.255.255.255 192.168.224.1 192.168.224.1 = 1 >Puerta de enlace predeterminada: 158.42.55.250 >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D >Rutas persistentes: > ninguno > >I think that it is the windows route list what is weird, but i am not su= re... > >Thanks in advance, >Salvador > > > =20 > |
