* Network script handling changes
@ 2005-10-31 16:52 Ewan Mellor
2005-10-31 17:05 ` Ewan Mellor
` (2 more replies)
0 siblings, 3 replies; 8+ messages in thread
From: Ewan Mellor @ 2005-10-31 16:52 UTC (permalink / raw)
To: Xen Developers
I have made some changes to the way the network scripts are handled, in order
to make it easier for those of you with non-standard configurations.
o All scripts now cope with parameters being passed on the command line, and
this command line may be specified in the xend-config.sxp.
o The vif-bridge script can autodetect the correct bridge name, if you are
using only one.
o The vif-bridge option in xend-config.sxp has gone. If you need this
functionality, specify it on the script command line, instead.
o If the default config worked for you before, then it should still work.
For example, if you are using this topology, the default bridged one:
dom0: fake eth0 -> vif0.0 -+
|
bridge (xenbr0) -> real eth0 -> the network
|
domU: fake eth0 -> vifN.0 -+
then
(network-script network-bridge)
(vif-script vif-bridge)
should suffice.
If, like Sean Dague, you are renaming the bridge, like this:
dom0: fake eth0 -> vif0.0 -+
|
bridge (br0) -> real eth0 -> the network
|
domU: fake eth0 -> vifN.0 -+
then you want
(network-script 'network-bridge bridge=br0')
(vif-script vif-bridge)
or if you have other bridges on your machine, but all the domUs use the same
bridge, then you want
(network-script 'network-bridge bridge=br0')
(vif-script 'vif-bridge bridge=br0')
If you need to use a different NIC than eth0, say eth1, like the "IBM blades":
dom0: fake eth0 -> vif0.0 -+
|
bridge -> real eth1 -> the network
|
domU: fake eth0 -> vifN.0 -+
then you want
(network-script 'network-bridge netdev=eth1')
(vif-script vif-bridge)
If, like Charles Duffy, you want two bridges:
dom0: fake eth0 -> vif0.0 ----------------------------+
dom0: fake eth1 -> vif0.1 ---+ |
| |
| bridge 0 -> real eth0
| |
bridge 1 -> real eth1 |
| |
| |
domU: fake eth0 -> vifN.0 ----------------------------+
domU: fake eth1 -> vifN.1 ---+
then you need to create a wrapper script:
(network-script my-network-script)
and in /etc/xen/scripts/my-network-script:
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" vifnum=0
"$dir/network-bridge" vifnum=1
If you want non-bridged topologies, then you have to use different scripts.
Michael Lessard, I believe, wants this:
dom0: ---------------------> real eth0 -> the network
dom1: fake eth0 -> vif1.0 -> real eth1 -> the network
In which case I think you want
(network-script network-route)
(vif-script vif-route)
though you might need some extra hacking to make this work, and I would be
interested in your success.
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.
If I claim your topology should work and it doesn't, then I would appreciate a
full set of info:
from dom0:
brctl show
ifconfig
route
iptables -L
cat /var/log/{debug,messages,syslog}
and from domU:
ifconfig
route
iptables -L
And if you want a topology that's not here, feel free to shout!
Happy networking,
Ewan.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Network script handling changes
2005-10-31 16:52 Network script handling changes Ewan Mellor
@ 2005-10-31 17:05 ` Ewan Mellor
2005-11-02 2:53 ` Greg Brackley
2005-11-02 16:50 ` Li Ge
2 siblings, 0 replies; 8+ messages in thread
From: Ewan Mellor @ 2005-10-31 17:05 UTC (permalink / raw)
To: Xen Developers
On Mon, Oct 31, 2005 at 04:52:54PM +0000, Ewan Mellor wrote:
> I have made some changes to the way the network scripts are handled, in order
> to make it easier for those of you with non-standard configurations.
And just a note about my rationale:
The intention is to move network-related stuff out of Xend and into the
scripts, where possible. It is still useful for some people (especially the
developers) for Xend to be able to alter the network configuration when it
starts, but in many cases it makes more sense for the init.d scripts to do it.
Given this, and for reasons of general cleanliness, I don't want Xend to need
to understand network-specific parameters like bridge names -- it is better
for Xend to just pass command line options through opaquely. Then, distros or
users are free to add whichever parameters they like without needing to patch
Xend.
Ewan.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Network script handling changes
2005-10-31 16:52 Network script handling changes Ewan Mellor
2005-10-31 17:05 ` Ewan Mellor
@ 2005-11-02 2:53 ` Greg Brackley
2005-11-03 4:39 ` Greg Brackley
2005-11-02 16:50 ` Li Ge
2 siblings, 1 reply; 8+ messages in thread
From: Greg Brackley @ 2005-11-02 2:53 UTC (permalink / raw)
To: Ewan Mellor, Xen Developers
----- Original Message -----
From: "Ewan Mellor" <ewan@xensource.com>
> 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 :-)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Network script handling changes
2005-10-31 16:52 Network script handling changes Ewan Mellor
2005-10-31 17:05 ` Ewan Mellor
2005-11-02 2:53 ` Greg Brackley
@ 2005-11-02 16:50 ` Li Ge
2005-11-02 17:19 ` Ewan Mellor
2 siblings, 1 reply; 8+ messages in thread
From: Li Ge @ 2005-11-02 16:50 UTC (permalink / raw)
To: Ewan Mellor; +Cc: Xen Developers, xen-devel-bounces
[-- Attachment #1.1.1: Type: text/plain, Size: 11777 bytes --]
Ewan,
I tried the two bridges topology you described below by following the
exact steps you suggested, but I could not get it work.
-----------------------------------------------------
dom0: fake eth0 -> vif0.0 ----------------------------+
dom0: fake eth1 -> vif0.1 ---+ |
| |
| bridge 0 -> real eth0
| |
bridge 1 -> real eth1 |
| |
| |
domU: fake eth0 -> vifN.0 ----------------------------+
domU: fake eth1 -> vifN.1 ---+
then you need to create a wrapper script:
(network-script my-network-script)
and in /etc/xen/scripts/my-network-script:
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" vifnum=0
"$dir/network-bridge" vifnum=1
------------------------------------------------------------------------------------------------------------------
Here are the lines uncommented in my xend-config.sxp
(xend-http-server yes)
(xend-relocation-server yes)
(xend-address localhost)
(xend-relocation-address localhost)
(network-script my-network-script)
(dom0-min-mem 0)
(dom0-cpus 0)
------------------------------------------------------------------------------------------------------------------
Here is the "ifconfig -a" output after I started xend:
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:09:6B:F5:F2:30
inet addr:9.3.192.171 Bcast:9.3.192.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:851 errors:0 dropped:0 overruns:0 frame:0
TX packets:206 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:90707 (88.5 Kb) TX bytes:28471 (27.8 Kb)
Interrupt:20
eth1 Link encap:Ethernet HWaddr 00:09:6B:F5:F2:31
inet addr:10.0.0.2 Bcast:10.0.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:21
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:36 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2594 (2.5 Kb) TX bytes:2594 (2.5 Kb)
veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
_____________________________________________________
I've also tried to start network-bridge manually. But still it does not
look right
#./network-bridge vifnum=0 start
eth0 device: Broadcom Corporation NetXtreme BCM5704 Gigabit
Ethernet (rev 03)
eth0 configuration: eth-id-00:09:6b:f5:f2:30
Nothing to flush.
eth0
eth0 configuration: eth-id-00:09:6b:f5:f2:30
# ./network-bridge vifnum=1 start
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:09:6B:F5:F2:30
inet addr:9.3.192.171 Bcast:9.3.192.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:90 errors:0 dropped:0 overruns:0 frame:0
TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7637 (7.4 Kb) TX bytes:3634 (3.5 Kb)
eth1 Link encap:Ethernet HWaddr 00:09:6B:F5:F2:31
inet addr:10.0.0.2 Bcast:10.0.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:21
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:46 errors:0 dropped:0 overruns:0 frame:0
TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3648 (3.5 Kb) TX bytes:3648 (3.5 Kb)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:89 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7969 (7.7 Kb) TX bytes:3558 (3.4 Kb)
Interrupt:20
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29 errors:0 dropped:0 overruns:0 frame:0
TX packets:90 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3634 (3.5 Kb) TX bytes:7637 (7.4 Kb)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:34 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2012 (1.9 Kb) TX bytes:0 (0.0 b)
xenbr1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Anything that I could have missed in the settings?
Thanks a lot,
Li
Ewan Mellor
<ewan@xensource.c
om> To
Sent by: Xen Developers
xen-devel-bounces <xen-devel@lists.xensource.com>
@lists.xensource. cc
com
Subject
[Xen-devel] Network script handling
10/31/2005 10:52 changes
AM
I have made some changes to the way the network scripts are handled, in
order
to make it easier for those of you with non-standard configurations.
o All scripts now cope with parameters being passed on the command line,
and
this command line may be specified in the xend-config.sxp.
o The vif-bridge script can autodetect the correct bridge name, if you
are
using only one.
o The vif-bridge option in xend-config.sxp has gone. If you need this
functionality, specify it on the script command line, instead.
o If the default config worked for you before, then it should still work.
For example, if you are using this topology, the default bridged one:
dom0: fake eth0 -> vif0.0 -+
|
bridge (xenbr0) -> real eth0 -> the network
|
domU: fake eth0 -> vifN.0 -+
then
(network-script network-bridge)
(vif-script vif-bridge)
should suffice.
If, like Sean Dague, you are renaming the bridge, like this:
dom0: fake eth0 -> vif0.0 -+
|
bridge (br0) -> real eth0 -> the network
|
domU: fake eth0 -> vifN.0 -+
then you want
(network-script 'network-bridge bridge=br0')
(vif-script vif-bridge)
or if you have other bridges on your machine, but all the domUs use the
same
bridge, then you want
(network-script 'network-bridge bridge=br0')
(vif-script 'vif-bridge bridge=br0')
If you need to use a different NIC than eth0, say eth1, like the "IBM
blades":
dom0: fake eth0 -> vif0.0 -+
|
bridge -> real eth1 -> the network
|
domU: fake eth0 -> vifN.0 -+
then you want
(network-script 'network-bridge netdev=eth1')
(vif-script vif-bridge)
If, like Charles Duffy, you want two bridges:
dom0: fake eth0 -> vif0.0 ----------------------------+
dom0: fake eth1 -> vif0.1 ---+ |
| |
| bridge 0 -> real eth0
| |
bridge 1 -> real eth1 |
| |
| |
domU: fake eth0 -> vifN.0 ----------------------------+
domU: fake eth1 -> vifN.1 ---+
then you need to create a wrapper script:
(network-script my-network-script)
and in /etc/xen/scripts/my-network-script:
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" vifnum=0
"$dir/network-bridge" vifnum=1
If you want non-bridged topologies, then you have to use different scripts.
Michael Lessard, I believe, wants this:
dom0: ---------------------> real eth0 -> the network
dom1: fake eth0 -> vif1.0 -> real eth1 -> the network
In which case I think you want
(network-script network-route)
(vif-script vif-route)
though you might need some extra hacking to make this work, and I would be
interested in your success.
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.
If I claim your topology should work and it doesn't, then I would
appreciate a
full set of info:
from dom0:
brctl show
ifconfig
route
iptables -L
cat /var/log/{debug,messages,syslog}
and from domU:
ifconfig
route
iptables -L
And if you want a topology that's not here, feel free to shout!
Happy networking,
Ewan.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.1.2: Type: text/html, Size: 19934 bytes --]
[-- Attachment #1.2: graycol.gif --]
[-- Type: image/gif, Size: 105 bytes --]
[-- Attachment #1.3: pic01052.gif --]
[-- Type: image/gif, Size: 1255 bytes --]
[-- Attachment #1.4: ecblank.gif --]
[-- Type: image/gif, Size: 45 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Network script handling changes
2005-11-02 16:50 ` Li Ge
@ 2005-11-02 17:19 ` Ewan Mellor
2005-11-02 17:33 ` Nivedita Singhvi
2005-11-02 19:28 ` Li Ge
0 siblings, 2 replies; 8+ messages in thread
From: Ewan Mellor @ 2005-11-02 17:19 UTC (permalink / raw)
To: Li Ge; +Cc: Xen Developers
On Wed, Nov 02, 2005 at 10:50:44AM -0600, Li Ge wrote:
> Ewan,
> I tried the two bridges topology you described below by following the
> exact steps you suggested, but I could not get it work.
>
> [Snip]
>
> Anything that I could have missed in the settings?
No, the settings look right. Of course, I presume that you have noticed that
my wrapper script is not quite right -- it does not pass the "start" command
through to network-bridge.
Even when you run network-bridge manually, it still hasn't worked though. Do
you get any error messages in /var/log/debug, /var/log/syslog, etc? One
obvious problem is that you have no vif0.1 interface, which is the one that
connects from your new eth1 to xenbr1. I presume that the script is bailing
out early for some reason -- it would be good if you could figure out where it
stops, and why.
Could you open a bug, and attach the output of
brctl show
ifconfig
route
iptables -L
before and after running
/etc/xen/scripts/network-bridge vifnum=0 start
/etc/xen/scripts/network-bridge vifnum=1 start
This should give us good clues to help with the debugging.
Thanks a lot,
Ewan.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Network script handling changes
2005-11-02 17:19 ` Ewan Mellor
@ 2005-11-02 17:33 ` Nivedita Singhvi
2005-11-02 19:28 ` Li Ge
1 sibling, 0 replies; 8+ messages in thread
From: Nivedita Singhvi @ 2005-11-02 17:33 UTC (permalink / raw)
To: Ewan Mellor; +Cc: Li Ge, Xen Developers
Ewan Mellor wrote:
> On Wed, Nov 02, 2005 at 10:50:44AM -0600, Li Ge wrote:
>
>
> No, the settings look right. Of course, I presume that you have noticed that
> my wrapper script is not quite right -- it does not pass the "start" command
> through to network-bridge.
Ewan, there seems to be an underlying problem that some people
are hitting more frequently than others - the virtual interface
just doesn't get created, and it seems to be non-deterministic
(occasionally passes). So we suspect yet another timing hole,
from what I can tell. Will have more for you today, although
there are a couple of other issues we're sidetracked on..
Getting trace output (set -x) from the scripts from everybody
would be good..
thanks,
Nivedita
> Even when you run network-bridge manually, it still hasn't worked though. Do
> you get any error messages in /var/log/debug, /var/log/syslog, etc? One
> obvious problem is that you have no vif0.1 interface, which is the one that
> connects from your new eth1 to xenbr1. I presume that the script is bailing
> out early for some reason -- it would be good if you could figure out where it
> stops, and why.
>
> Could you open a bug, and attach the output of
>
> brctl show
> ifconfig
> route
> iptables -L
>
> before and after running
>
> /etc/xen/scripts/network-bridge vifnum=0 start
> /etc/xen/scripts/network-bridge vifnum=1 start
>
> This should give us good clues to help with the debugging.
>
> Thanks a lot,
>
> Ewan.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Network script handling changes
2005-11-02 17:19 ` Ewan Mellor
2005-11-02 17:33 ` Nivedita Singhvi
@ 2005-11-02 19:28 ` Li Ge
1 sibling, 0 replies; 8+ messages in thread
From: Li Ge @ 2005-11-02 19:28 UTC (permalink / raw)
To: Ewan Mellor; +Cc: Xen Developers, xen-devel-bounces
[-- Attachment #1.1.1: Type: text/plain, Size: 2628 bytes --]
Please see bug #381.
Thanks,
Li
Ewan Mellor
<ewan@xensource.c
om> To
Sent by: Li Ge/Austin/IBM@IBMUS
xen-devel-bounces cc
@lists.xensource. Xen Developers
com <xen-devel@lists.xensource.com>
Subject
Re: [Xen-devel] Network script
11/02/2005 11:19 handling changes
AM
On Wed, Nov 02, 2005 at 10:50:44AM -0600, Li Ge wrote:
> Ewan,
> I tried the two bridges topology you described below by following the
> exact steps you suggested, but I could not get it work.
>
> [Snip]
>
> Anything that I could have missed in the settings?
No, the settings look right. Of course, I presume that you have noticed
that
my wrapper script is not quite right -- it does not pass the "start"
command
through to network-bridge.
Even when you run network-bridge manually, it still hasn't worked though.
Do
you get any error messages in /var/log/debug, /var/log/syslog, etc? One
obvious problem is that you have no vif0.1 interface, which is the one that
connects from your new eth1 to xenbr1. I presume that the script is
bailing
out early for some reason -- it would be good if you could figure out where
it
stops, and why.
Could you open a bug, and attach the output of
brctl show
ifconfig
route
iptables -L
before and after running
/etc/xen/scripts/network-bridge vifnum=0 start
/etc/xen/scripts/network-bridge vifnum=1 start
This should give us good clues to help with the debugging.
Thanks a lot,
Ewan.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.1.2: Type: text/html, Size: 4077 bytes --]
[-- Attachment #1.2: graycol.gif --]
[-- Type: image/gif, Size: 105 bytes --]
[-- Attachment #1.3: pic14253.gif --]
[-- Type: image/gif, Size: 1255 bytes --]
[-- Attachment #1.4: ecblank.gif --]
[-- Type: image/gif, Size: 45 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Network script handling changes
2005-11-02 2:53 ` Greg Brackley
@ 2005-11-03 4:39 ` Greg Brackley
0 siblings, 0 replies; 8+ messages in thread
From: Greg Brackley @ 2005-11-03 4:39 UTC (permalink / raw)
To: Xen Developers; +Cc: Ewan Mellor
----- Original Message -----
From: "Greg Brackley" <lists-xen-devel@lucidsolutions.co.nz>
>
>
> dom0: fake eth0 -> vif0.0 --- br0 --- bond0.1 (VLAN 1) --+
> |
> +------------------------------------------------------+
> |
> | + -> real eth0 -> the network
> +--- bond0 -+
> +--> real eth1 -> the network
I seem to be going backwards on the networking. I can't get the networking
operating for a dom0 only machine, using FC4 init scripts only.
The setup is two physical ethernets (sk-9e22), with bond, a single vlan, a
single bridge, and a single vif/veth0. I have added another ethernet card
so that I can SSH in (eth2/eth3), and put an IP address directly on eth2
(this works). The eth2 interface should be outside the problem.
I can reliably ping (ICMP) the veth0 interface from other networks. UDP and
TCP appear to be broken. e.g. DNS fails. SSH fails.
I have tried turning ARP off on all interfaces except veth0, but that alone
didn't help. I wonder if it is some checksum issue with the sk98lin driver?
I might try using the e1000 card as the eth0/eth1 interface. I have a tg3
based machine working ok with a single VLAN. Very weird (which means I
probably don't understand something). Lots of info below.
Greg :-)
# ifconfig
bond0 Link encap:Ethernet HWaddr 00:00:5A:72:A6:B6
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:848 errors:0 dropped:0 overruns:0 frame:0
TX packets:497 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:86163 (84.1 KiB) TX bytes:62876 (61.4 KiB)
bond0.133 Link encap:Ethernet HWaddr 00:00:5A:72:A6:B6
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:235 errors:0 dropped:0 overruns:0 frame:0
TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:14802 (14.4 KiB) TX bytes:3696 (3.6 KiB)
br0 Link encap:Ethernet HWaddr 00:00:5A:72:A6:B6
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:196 (196.0 b) TX bytes:0 (0.0 b)
eth0 Link encap:Ethernet HWaddr 00:00:5A:72:A6:B6
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:371 errors:0 dropped:0 overruns:0 frame:0
TX packets:257 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:38038 (37.1 KiB) TX bytes:32156 (31.4 KiB)
Interrupt:19 Memory:da000000-0
eth1 Link encap:Ethernet HWaddr 00:00:5A:72:A6:B6
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:477 errors:0 dropped:0 overruns:0 frame:0
TX packets:240 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:48125 (46.9 KiB) TX bytes:30720 (30.0 KiB)
eth2 Link encap:Ethernet HWaddr 00:04:23:AC:57:A4
inet addr:10.10.10.220 Bcast:10.10.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:292 errors:0 dropped:0 overruns:0 frame:0
TX packets:453 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:33617 (32.8 KiB) TX bytes:48430 (47.2 KiB)
Base address:0x3000 Memory:de280000-de2a0000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:23 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4204 (4.1 KiB) TX bytes:4204 (4.1 KiB)
veth0 Link encap:Ethernet HWaddr AA:DE:AD:01:33:01
inet addr:192.168.133.1 Bcast:192.168.133.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:235 errors:0 dropped:0 overruns:0 frame:0
TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:17152 (16.7 KiB) TX bytes:3822 (3.7 KiB)
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:52 errors:0 dropped:0 overruns:0 frame:0
TX packets:235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3696 (3.6 KiB) TX bytes:17152 (16.7 KiB)
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.133.0 0.0.0.0 255.255.255.0 U 0 0 0
veth0
10.10.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
0.0.0.0 192.168.133.254 0.0.0.0 UG 0 0 0
veth0
# ip addr show
1: lo: <LOOPBACK,UP> 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
2: vif0.0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
3: veth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
link/ether aa:de:ad:01:33:01 brd ff:ff:ff:ff:ff:ff
inet 192.168.133.1/24 brd 192.168.133.255 scope global veth0
4: bond0: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue
link/ether 00:00:5a:72:a6:b6 brd ff:ff:ff:ff:ff:ff
5: eth0: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast master
bond0 qlen 1000
link/ether 00:00:5a:72:a6:b6 brd ff:ff:ff:ff:ff:ff
6: eth1: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast master
bond0 qlen 1000
link/ether 00:00:5a:72:a6:b6 brd ff:ff:ff:ff:ff:ff
7: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:04:23:ac:57:a4 brd ff:ff:ff:ff:ff:ff
inet 10.10.10.220/24 brd 10.10.10.255 scope global eth2
8: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 00:04:23:ac:57:a5 brd ff:ff:ff:ff:ff:ff
9: br0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
link/ether 00:00:5a:72:a6:b6 brd ff:ff:ff:ff:ff:ff
10: bond0.133: <BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue
link/ether 00:00:5a:72:a6:b6 brd ff:ff:ff:ff:ff:ff
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00005a72a6b6 no bond0.133
# brctl showmacs br0
port no mac addr is local? ageing timer
1 00:00:5a:72:a6:b6 yes 0.00
1 00:12:3f:20:69:f0 no 0.80
2 aa:de:ad:01:33:01 no 38.59
2 fe:ff:ff:ff:ff:ff yes 0.00
# iptables -L
vif0.0
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
# grep . /proc/sys/net/bridge/*
/proc/sys/net/bridge/bridge-nf-call-arptables:1
/proc/sys/net/bridge/bridge-nf-call-ip6tables:1
/proc/sys/net/bridge/bridge-nf-call-iptables:1
/proc/sys/net/bridge/bridge-nf-filter-vlan-tagged:1
# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD
bond0.133 | 133 | bond0
# cat /proc/net/vlan/bond0.133
bond0.133 VID: 133 REORDER_HDR: 1 dev->priv_flags: 1
total frames received 2860
total bytes received 186932
Broadcast/Multicast Rcvd 4
total frames transmitted 458
total bytes transmitted 33915
total headroom inc 0
total encap on xmit 0
Device: bond0
INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
EGRESSS priority Mappings:
# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v2.6.1 (October 29, 2004)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
802.3ad info
LACP rate: fast
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 2
Actor Key: 17
Partner Key: 26
Partner Mac Address: 00:11:43:f7:8c:00
Slave Interface: eth0
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:00:5a:72:a6:b6
Aggregator ID: 1
Slave Interface: eth1
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:00:5a:72:a6:b7
Aggregator ID: 1
# /etc/modprobe.conf
alias eth0 sk98lin
alias eth1 sk98lin
alias eth2 e1000
alias eth3 e1000
alias bond0 bonding
options bond0 mode=802.3ad lacp_rate=fast miimon=100
# cat /proc/interrupts
CPU0
1: 8 Phys-irq i8042
8: 0 Phys-irq rtc
9: 0 Phys-irq acpi
12: 110 Phys-irq i8042
14: 1396 Phys-irq ide0
19: 4174 Phys-irq eth0
21: 0 Phys-irq ohci_hcd:usb1
22: 7690 Phys-irq libata
23: 0 Phys-irq libata
24: 168 Phys-irq mvSata
28: 168 Phys-irq mvSata
29: 3216 Phys-irq eth2
256: 42183 Dynamic-irq timer0
257: 67 Dynamic-irq xenbus
258: 0 Dynamic-irq console
259: 0 Dynamic-irq net-be-dbg
NMI: 0
LOC: 0
ERR: 0
# cat /proc/net/sk98lin/eth0
Detailed statistic for device eth0
=======================================
Board statistics
Card name SK-9E22 10/100/1000Base-T Dual Port Server
Adapter
Vendor/Device ID 1148/9e00
Card type (Bit) 64
Active Port A
Preferred Port A
Interrupt Moderation disabled
Bus type PCI-Express
Bus width (Lanes) 4
Driver version 8.24.1.3 (01)
Driver release date Aug-09-2005
Hardware revision v1.2
Temperature (C) 35.05
Temperature (F) 95.00
Voltage PCI (V) 0.000
Voltage PCI-IO (V) 0.000
Voltage VMAIN (V) 0.000
Voltage VAUX (V) 0.000
Voltage Core 1V2 (V) 0.000
Voltage PHY 1V5 (V) 0.000
Voltage PHY 2V5 (V) 0.000
Receive statistics
Received bytes 307552
Received packets 2887
Receive errors 0
Receive dropped 0
Received multicast 2874
Transmit statistics
Transmitted bytes 250406
Transmitted packets 1996
Transmit errors 0
Transmit dropped 0
Transmit collisions 0
Dump off ssh session started from 192.168.137.9, monitoring from
192.168.133.254 (router)
# tcpdump -n -i bond0.133 -vv
tcpdump: listening on bond0.133, link-type EN10MB (Ethernet), capture size
96 bytes
16:37:42.240082 IP (tos 0x10, ttl 63, id 37160, offset 0, flags [DF], proto
6, length: 60) 192.168.137.9.52089 > 192.168.133.1.ssh: S [tcp sum ok]
373073993:373073993(0) win 5840 <mss 1460,sackOK,timestamp 423049569
0,nop,wscale 0>
16:37:42.242073 arp who-has 192.168.133.254 tell 192.168.133.1
16:37:42.242086 arp reply 192.168.133.254 is-at 00:12:3f:20:69:f0
16:37:42.242230 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto 6,
length: 60) 192.168.133.1.ssh > 192.168.137.9.52089: S [tcp sum ok]
1404968999:1404968999(0) ack 373073994 win 5792 <mss 1460,sackOK,timestamp
229714 423049569,nop,wscale 2>
16:37:42.242455 IP (tos 0x10, ttl 63, id 37161, offset 0, flags [DF], proto
6, length: 52) 192.168.137.9.52089 > 192.168.133.1.ssh: . [tcp sum ok]
1:1(0) ack 1 win 5840 <nop,nop,timestamp 423049570 229714>
16:37:47.242073 arp who-has 192.168.133.1 tell 192.168.133.254
16:37:47.242273 arp reply 192.168.133.1 is-at aa:de:ad:01:33:01
# tcpdump -n -p -i bond0
03:18:20.200065 00:11:43:f7:8c:04 > 01:80:c2:00:00:02, ethertype Unknown
(0x8809), length 124:
0x0000: 0101 0114 0100 0011 43f7 8c00 1a00 0100 ........C.......
0x0010: 0c00 3f00 0000 0214 ffff 0000 5a72 a6b6 ..?.........Zr..
0x0020: 1100 ff00 0200 3f00 0000 0310 0000 0000 ......?.........
0x0030: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0040: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0050: 0000 ..
03:18:20.221549 802.1d unknown version
03:18:20.315315 IP (tos 0x0, ttl 64, id 13960, offset 0, flags [DF], proto
17, length: 65) 192.168.133.1.32796 > 192.168.134.6.domain: [bad udp cksum
8176!] 41708+ A? mygale.fifthweb.net. (37)
03:18:20.759854 00:11:43:f7:8c:03 > 01:80:c2:00:00:02, ethertype Unknown
(0x8809), length 124:
0x0000: 0101 0114 0100 0011 43f7 8c00 1a00 0100 ........C.......
0x0010: 0b00 3f00 0000 0214 ffff 0000 5a72 a6b6 ..?.........Zr..
0x0020: 1100 ff00 0100 3f00 0000 0310 0000 0000 ......?.........
0x0030: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0040: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0050: 0000
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2005-11-03 4:39 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-31 16:52 Network script handling changes Ewan Mellor
2005-10-31 17:05 ` Ewan Mellor
2005-11-02 2:53 ` Greg Brackley
2005-11-03 4:39 ` Greg Brackley
2005-11-02 16:50 ` Li Ge
2005-11-02 17:19 ` Ewan Mellor
2005-11-02 17:33 ` Nivedita Singhvi
2005-11-02 19:28 ` Li Ge
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.