[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] I can't access to my VM via network!!
I changed the MAC address to "mac=00:16:17:a5:67:89" and I run below command on my Xen host : # ip neigh 172.30.9.1 dev br0 lladdr 1c:6f:65:3f:90:ea STALE 172.30.9.254 dev br0 lladdr 9c:4e:20:7a:7f:44 REACHABLE 172.30.9.21 dev br0 lladdr 00:16:17:a5:67:89 STALE 172.30.9.10 dev br0 lladdr 00:02:b6:44:f4:4d STALE and did same command on VM : # ip neigh 172.30.9.20 dev xenbr0 lladdr 50:e5:49:40:c4:8f STALE and "brctl showmacs br0" on Xen host show : # brctl showmacs br0 port no mac addr is local? ageing timer 1 00:02:b6:44:f4:4d no 34.00 1 00:0c:29:30:80:68 no 5.03 1 00:0c:29:c7:60:76 no 20.03 1 00:0c:29:e7:f7:8b no 5.07 1 00:0c:29:ec:56:d5 no 73.19 3 00:16:17:a5:67:89 no 290.23 1 00:1b:21:a6:4e:e0 no 2.04 1 00:50:56:9b:07:0c no 5.03 1 00:50:56:9b:0b:53 no 73.56 1 1c:6f:65:3f:90:ea no 6.91 1 50:e5:49:40:c4:8f yes 0.00 1 50:e5:49:40:c4:8f yes 0.00 1 90:2b:34:1f:29:5c no 46.58 1 9c:4e:20:7a:7f:44 no 0.00 1 e4:11:5b:11:af:a2 no 12.53 1 e4:11:5b:11:af:a4 no 39.60 1 e4:11:5b:11:af:a6 no 39.60 1 e8:39:35:e9:1d:b0 no 5.14 1 e8:ed:f3:fa:c5:12 no 0.59 2 fe:ff:ff:ff:ff:ff yes 0.00 2 fe:ff:ff:ff:ff:ff yes 0.00 and same command on VM : # brctl showmacs br0 Read of forward table failed : No such device I must tell you that, Xen host can ping VM IP and the VM can ping Xen IP but other computer in network can't see VM. On Wednesday, June 29, 2016 6:09 PM, Simon Hobson <linux@xxxxxxxxxxxxxxxx> wrote: Please don't top post, it's intensely annoying to some of us. Jason Long <hack3rcon@xxxxxxxxx> wrote: > vif=['mac=00:16:17:a5:6y:89,bridge=br0'] OK, you still have a "y" in the MAC address there. That may or may not affect things - I actually have no idea on that but Id suggest correcting it. > 4: enp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000 > 8: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default > inet 172.30.9.20/24 brd 172.30.9.255 scope global br0 > valid_lft forever preferred_lft forever OK, that looks OK. > 21: vif7.0-emu: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UNKNOWN group default qlen 500 TBH, I have no idea what this is or where it came from. > 22: vif7.0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master br0 state DOWN group default qlen 32 Ah, that doesn't look right. The state is UP on my systems. Correction, on one host all the interfaces show as UP, on another they all show as UNKNOWN. > bridge name bridge id STP enabled interfaces > br0 8000.50e54940c48f no enp7s0 > vif7.0 > vif7.0-emu That looks OK - apart from that vif7.0-emu I've not seen before. So I think the next step is to look at the guest. It should have one network interface, state up, with an IP address configured. "ip neigh" on both host and guest might give some clues, and "brctl showmacs br0" on the host should show if it's seeing anything from the guest. But I will have to admit, this is somewhat out of my skills zone now ... _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |