Re: networking, looking for pointers [message #13661 is a reply to message #13637] |
Fri, 01 June 2007 08:27   |
dev
Messages: 1693 Registered: September 2005 Location: Moscow
|
Senior Member |

|
|
I'm unsure I understand fully your networking settings, but
even when I add IP 192.168.101.12 to the *host*, it still doesn't work:
[1]+ tcpdump -n -i eth2 host 194.87.0.50 &
debian:~#
debian:~# ping 194.87.0.50
PING 194.87.0.50 (194.87.0.50) 56(84) bytes of data.
09:26:31.617338 IP 192.168.101.12 > 194.87.0.50: ICMP echo request, id 30851, seq 1, length 64
09:26:32.618705 IP 192.168.101.12 > 194.87.0.50: ICMP echo request, id 30851, seq 2, length 64
09:26:33.618754 IP 192.168.101.12 > 194.87.0.50: ICMP echo request, id 30851, seq 3, length 64
09:26:34.618822 IP 192.168.101.12 > 194.87.0.50: ICMP echo request, id 30851, seq 4, length 64
09:26:35.618878 IP 192.168.101.12 > 194.87.0.50: ICMP echo request, id 30851, seq 5, length 64
09:26:36.618951 IP 192.168.101.12 > 194.87.0.50: ICMP echo request, id 30851, seq 6, length 64
09:26:37.619004 IP 192.168.101.12 > 194.87.0.50: ICMP echo request, id 30851, seq 7, length 64
--- 194.87.0.50 ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6001ms
i.e. no replies.
Can you reask your admin whether it is actually VLAN or simply a network IP's range which you can directly use and assign to your ethX devices?
if it is a vlan, then it should have an ID 
|
|
|