Dear Rafał,
Thanks for your reply and useful suggestions.
On Fri, 2008-03-21 at 12:53 +0100, Rafał Kupka wrote:
> Back to your problem -- run commands (while dom0 network has
> problems):
> # brctl show
> # brctl showmacs xen-br0
> # ip addr ls
# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif0.0
peth0
vif1.1
vif1.0
This is with one domU running; domU does have network access; dom0 does
not. It is possible to connect to the domU via ssh and then connect to
the dom0 from the domU via ssh.
# brctl showmacs xenbr0
port no mac addr is local? ageing timer
2 00:14:5e:ce:b5:c9 no 61.11
2 00:14:5e:ce:bb:8f no 89.24
2 00:14:5e:ce:bb:ba no 20.52
2 00:14:5e:ce:bb:bd no 81.96
2 00:14:5e:ce:bb:be no 39.58
2 00:14:5e:ce:bb:c4 no 85.97
2 00:19:56:e3:24:8c no 8.84
2 00:1a:64:8c:77:0e no 123.29
2 00:1a:64:8c:78:0a no 14.64
1 00:1a:64:8c:be:aa no 0.00
2 00:90:7f:3c:47:c3 no 0.00
4 02:00:00:00:00:01 no 0.00
1 fe:ff:ff:ff:ff:ff yes 0.00
00:1a:64:8c:be:aa is the MAC address of the physical eth0 interface
02:00:00:00:00:01 is the MAC address I have assigned to the domU
according to the rules in
http://wiki.xensource.com/xenwiki/XenNetworking:
"In summary, an address of the following form should be OK:
XY:XX:XX:XX:XX:XX
where X is any hexadecimal digit, and Y is one of 2, 6, A or E."
# ip addr ls
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: peth0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcff:ffff:feff:ffff/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 00:1a:64:8c:be:ac brd ff:ff:ff:ff:ff:ff
4: vif0.0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcff:ffff:feff:ffff/64 scope link
valid_lft forever preferred_lft forever
5: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:1a:64:8c:be:aa brd ff:ff:ff:ff:ff:ff
inet 192.168.0.1/24 brd 192.168.0.255 scope global eth0
inet6 fe80::21a:64ff:fe8c:beaa/64 scope link
valid_lft forever preferred_lft forever
6: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
7: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
8: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
9: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
10: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
11: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
12: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
13: xenbr0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet6 fe80::200:ff:fe00:0/64 scope link
valid_lft forever preferred_lft forever
14: vif1.0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcff:ffff:feff:ffff/64 scope link
valid_lft forever preferred_lft forever
15: vif1.1: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcff:ffff:feff:ffff/64 scope link
valid_lft forever preferred_lft forever
I will also try your suggestion of configuring the bridge via Debian's
interfaces file and using network-dummy as the Xen networking script.
Best regards,
George Karaolides
System Administrator
OTEnet Telecommunications Ltd.
Nicosia, Cyprus
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home