Networking issue ?

I send 2 attachements one of the host
and one screenshot of the VM 105
its a screenshot because i have no network, cut and paste
does not work in the IE console.

when i do ifconfig -a in the VM i also see a venet0,
but that is also on my other hosts.
 

Attachments

seems ok, try to debug with 'tcpdump':

tcpdump -i vmbr0 -l -n host 192.168.100.12

Maybe you can see where packages gets lost?

- Dietmar
 
output of tcpdump

pm01:~# tcpdump -i vmbr0 -l -n host 192.168.100.12
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vmbr0, link-type EN10MB (Ethernet), capture size 96 bytes
15:33:08.900589 arp who-has 192.168.100.12 tell 192.168.100.2
15:33:08.900696 arp reply 192.168.100.12 is-at 00:18:51:70:43:12
15:33:36.935002 arp who-has 192.168.100.12 tell 192.168.100.2
15:33:36.935030 arp reply 192.168.100.12 is-at 00:18:51:70:43:12
15:34:04.972487 arp who-has 192.168.100.12 tell 192.168.100.2
15:34:04.972514 arp reply 192.168.100.12 is-at 00:18:51:70:43:12
15:34:33.020186 arp who-has 192.168.100.12 tell 192.168.100.2
15:34:33.020215 arp reply 192.168.100.12 is-at 00:18:51:70:43:12
15:34:52.443055 IP 192.168.100.12.138 > 192.168.100.255.138: NBT UDP PACKET(138)
15:34:52.443090 IP 192.168.100.12.138 > 192.168.100.255.138: NBT UDP PACKET(138)
15:35:01.067034 arp who-has 192.168.100.12 tell 192.168.100.2
15:35:01.067061 arp reply 192.168.100.12 is-at 00:18:51:70:43:12
15:35:29.115441 arp who-has 192.168.100.12 tell 192.168.100.2
15:35:29.115469 arp reply 192.168.100.12 is-at 00:18:51:70:43:12
14 packets captured
14 packets received by filter
0 packets dropped by kernel
 
brctl show:

pm01:~# brctl show
bridge name bridge id STP enabled interfaces
vmbr0 8000.0015c55e536a no eth0
veth105.0
 
if i ping the gateway (router) from within my VM105

i see this on the host.

15:58:31.861978 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:32.861976 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:33.861976 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:34.869977 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:35.869976 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:36.869993 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:37.877978 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:38.877979 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:39.877976 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:40.885976 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:41.885982 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:42.885981 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:43.893977 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:44.893978 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:45.893977 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:46.526977 IP 192.168.100.12 > 192.168.100.200: ICMP echo request, id 26114, seq 19, length 64
15:58:46.526979 IP 192.168.100.12 > 192.168.100.200: ICMP echo request, id 26114, seq 20, length 64
15:58:46.526980 IP 192.168.100.12 > 192.168.100.200: ICMP echo request, id 26114, seq 21, length 64
15:58:46.902003 IP 192.168.100.12 > 192.168.100.200: ICMP echo request, id 26114, seq 22, length 64
15:58:47.902007 IP 192.168.100.12 > 192.168.100.200: ICMP echo request, id 26114, seq 23, length 64
15:58:48.901999 IP 192.168.100.12 > 192.168.100.200: ICMP echo request, id 26114, seq 24, length 64
15:58:49.901998 IP 192.168.100.12 > 192.168.100.200: ICMP echo request, id 26114, seq 25, length 64
15:58:50.901999 IP 192.168.100.12 > 192.168.100.200: ICMP echo request, id 26114, seq 26, length 64
15:58:51.901976 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:51.902006 IP 192.168.100.12 > 192.168.100.200: ICMP echo request, id 26114, seq 27, length 64
15:58:52.901977 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:52.902024 IP 192.168.100.12 > 192.168.100.200: ICMP echo request, id 26114, seq 28, length 64
15:58:53.901975 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:53.902005 IP 192.168.100.12 > 192.168.100.200: ICMP echo request, id 26114, seq 29, length 64
15:58:54.905982 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:55.905978 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:56.905981 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:58.905981 arp who-has 192.168.100.200 tell 192.168.100.12
15:58:59.905979 arp who-has 192.168.100.200 tell 192.168.100.12
15:59:00.905981 arp who-has 192.168.100.200 tell 192.168.100.12
15:59:02.905982 arp who-has 192.168.100.200 tell 192.168.100.12
15:59:03.905983 arp who-has 192.168.100.200 tell 192.168.100.12
15:59:04.742066 IP 192.168.100.12.138 > 192.168.100.255.138: NBT UDP PACKET(138)
15:59:04.742112 IP 192.168.100.12.138 > 192.168.100.255.138: NBT UDP PACKET(138)
15:59:04.905985 arp who-has 192.168.100.200 tell 192.168.100.12


15:58:45.893977 arp who-has 192.168.100.200 tell 192.168.100.12

the 192.168.100.200 is my adslrouter

is that the correct answer ?
 
host 192.168.100.200 does not answer - find out why. Is there a log on the rooter? Maybe the rooter only allows specific macs?
 
i know this thread must drive you crazy also and i appreciate your help
so far, but on this host is also a kvm guest (windows xp)
and that one is running fine. so my dsl router
cannot be the problem i think.
 
as far as i can see no dublicate mac address

this is route on the VM (looks ok)

Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.100.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.100.200 0.0.0.0 UG 0 0 0 eth0
 
suddenly i see when i do a ifconfig eth0:
interupt: 16

its an on board GB nic on a Dell machine.

is it possible that because venet is working ok,
that the configuration of the bridge differ from the interface ?
 
Hai Dietmar,

i'm think there is a issue with the network card on the dell server.
interupt 16.

venet is working fine, but bridged has a problem with that.

I'm looking for a solution for that right now.
 
You must log in or register to reply here.
Top Bottom