Re: [Xen-devel] Network script handling changes

[Greg Brackley <lists-xen-devel@xxxxxxxxxxxxxxxxxxxx>]

----- Original Message ----- 
From: "Ewan Mellor" <ewan@xxxxxxxxxxxxx>
> If you want to handle initial networking through the init.d scripts, as 
> Greg
> Brackley wanted, IIRC, then simply don't specify a network-script (this 
> has
> worked for a week or so now) and specify an appropriate vif-script 
> instead.
> Greg, if you've got anywhere with your VLAN/domU setup, I'd be interested.
I'm still having problems. I don't understand where I am having problems. I 
must be missing something really obvious!
I can get ICMP working just fine, but tcp/udp seem to be having problems. I 
don't have iptables or any filtering that I am aware of. I think I have 
everything running with an MTU of 1500 (but would prefer 9000). The strange 
thing is sometimes when I put tcpdump on the VLAN interfaces, things start 
to work (e.g. starting a ssh session). tcpdump without promiscuous mode 
seems to overcome the problem.
I'll try and get some information off the machine with sneaker-net.

I have an ugly ascii art diagram below showing what I am trying to get 
going. The only interfaces with IP addresses are the fake eth0's.
dom0: fake eth0 -> vif0.0 --- br0 --- bond0.1 (VLAN 1) --+
                                                        |
domU: fake eth0 -> vif1.0 --- br1 --- bond0.2 (VLAN 2) --+
                                                        |
domU: fake eth0 -> vif2.0 --- br2 --- bond0.3 (VLAN 3) --+
                                                        |
domU: fake eth0 -> vif3.0 --- br3 --- bond0.4 (VLAN 4) --+
                                                        |
domU: fake eth0 -> vif4.0 --- br4 --- bond0.5 (VLAN 5) --+
                                                        |
 +------------------------------------------------------+
 |
 |           + -> real eth0 -> the network
 +--- bond0 -+
             +--> real eth1 -> the network

Greg :-) 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel