Hi List!
I have a bridging setup in my Dom0. Everything worked as expected in the
DomUs from the beginning. I also attached a serial console to Dom0 for
debugging the boot-process which worked perfectly as well.
The Router DomU fetches an internet-ip from the inode-device, connects
through pppoe and masquerades all traffic from lan through. It also has
a dchp-server running. The Devices are called lan and inode via udev.
_______________________________
|Dom0------ _______|
| \ | |
----|--lan---lanbr----DomU: |router |
| / |_______|
| / ________|
| / | |
----|--inode--iodebr--DomU:|pubserv |
|______________________|________|
What I want to do now is simply attach the Dom0 as a client to the lan
because serial console sucks to work on...
I do get an ip if i start dhclient on lanbr (device lan doesn''t work),
but I can''t reach any machines, also Dom0 isn''t reachable from
the
router DomU which is a bit funny because i get an ip.
There are no iptables-rules on Dom0 AND DomU (except masquerading and
pppoe-MTU-clamping-stuff).
in xend.conf
i start my-network-bridge:
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 bridge=inodebr
brctl addif inodebr inode
"$dir/network-bridge" "$@" vifnum=1 bridge=lanbr
brctl addif lanbr lan
"$dir/network-bridge" "$@" vifnum=2 bridge=xenintbr
and my-vif-script:
#!/bin/sh
dir=$(dirname "$0")
"$dir/vif-bridge" "$@" vif=inode bridge=inodebr
"$dir/vif-bridge" "$@" vif=lan bridge=lanbr
brctl show looks like this:
bridge name bridge id STP enabled interfaces
inodebr 8000.0000210716b2 no inode
vif1.0
vif2.0
lanbr 8000.0000cb021337 no lan
vif1.1
Can anyone give me a hint where to continue debugging my setup?
regards, gregor
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users