Hi,
Actually, I checked this script indeed, and also did by hand what I
thought should happen, the takeover of the MAC and IP of eth0 and transfer
it to de veth0. What I did was setting the MAC address to a plain
FE:FF:FF:FF:FF:FF MAC address, and deleted the IP address, after these
were taken over by veth0.
But, as Keir correctly stated, the routes should also be redefined, hence
eth0 is disabled.
Also, when I boot, and I do not use 'xend start' but do the
/etc/xen/scripts/network start instead, the IP take-over process is done
correctly. So I'll check why this isn't working via xend start later.
The thing is, after I've got the following configuration it is still -NOT-
working:
megalosaurus:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:86 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1956 (1.9 KiB) TX bytes:12490 (12.1 KiB)
Interrupt:11 Base address:0xec00
<..snip..>
veth0 Link encap:Ethernet HWaddr 00:40:63:D7:A3:82
inet addr:10.0.0.4 Bcast:10.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:882 (882.0 b)
megalosaurus:~#
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
veth0
0.0.0.0 10.0.0.254 0.0.0.0 UG 0 0 0
veth0
megalosaurus:~# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy DROP)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
So, this looks good IMHO, but it does not work.
Some checking with tcpdump on the Xen host (10.0.0.4) gave me the
following remarkable info:
04:41:30.508617 arp who-has 10.0.0.3 tell newmeg
04:41:30.508763 arp reply 10.0.0.3 is-at 00:01:02:0a:25:0d
And, I saw on this 10.0.0.3 (oldserver) host:
20:44:00.289199 arp who-has oldserver tell 10.0.0.4
They are getting each others arp replies!
So, these two servers actually *see* each other, but they won't come much
further than arp, ip (as in the protocol) is not working...
PS
When stopping the xen network and thus the bridge, and restart my default
debian network configuration, everything works again..
I am really scratching my head now.
Jurgen
Although very unlikely, it seems Keir Fraser stated on Jun 5 that :
>
> On 5 Jun 2005, at 17:40, Keir Fraser wrote:
>
> >> The /etc/xen/scripts/network script should be creating the bridge and
> >> veth0, and transferring the IP address from eth0 to veth0.
> >>
> >> It appears in your report as though both eth0 and veth0 have the same
> >> address. I expect this is a conflict between the network script and
> >> your
> >> existing setup.
> >
> > The script does not bother to delete the address from the old
> > interface, but the routes should be changed to be via veth0 rather
> > than eth0.
>
> Hmm.. actually the script *is* supposed to delete the address from
> eth0. So I'm not sure how things ended up in the state Jurgen posted.
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home