From: David F Barrera <dfbp@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
xen-devel@lists.xensource.com, "Zhai,
Edwin" <edwin.zhai@intel.com>
Subject: RE: RE: new /etc/xen/network script
Date: Tue, 16 Aug 2005 13:53:42 -0500 [thread overview]
Message-ID: <1124218423.4598.23.camel@localhost.localdomain> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282B7E@liverpoolst.ad.cl.cam.ac.uk>
On Tue, 2005-08-16 at 17:51 +0100, Ian Pratt wrote:
> > I, too, am having network related issues. I am now seeing
> > this problem on a FC3 box, which previously had worked just
> > fine. The networking is working fine before I enter 'xend
> > start'. No changes are made to the network-bridge script that
> > comes with the source, and the machine has only only nic, eth0.
>
> Grrr. Please can you do a 'netstat -rn' before and after.
I should point out that the new network-bridge script appears to have
cured the original problem on the SLES 9 boxes; at least xen-br0 is
coming up and Dom0 retains networking on those boxes.
On the FC3 box:
before:[root@dbarrera ~]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
9.53.94.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
eth0
0.0.0.0 9.53.94.1 0.0.0.0 UG 0 0 0
eth0
> What kind of network card is this?
Intel 82541EI Gigabit Ethernet Controller (Copper)
>
> The TX/RX counters for the new eth0 are non zero. Are they going up?
> In what whay does networking not work?
I cannot connect to or from the outside (ssh, ping, nfs mounts, etc).
> Can you use tcpdump on eth0 to determine whether packets from the outside world are arriving.
It seems that packets from the outside world are coming in.
I entered 'tcpdump -n -i eth0 host 9.53.94.235' then when I tried to ssh
from the other machine, it shows up on the tcpdump. But the ssh session
is never established. Ping shows up as well.
> If not, what about peth0?
Same.
> (Bare in mind that if you only have one-way connectivity the only packets you're see are arps, not icmp pings or anything else)
>
> Ian
>
> > ifconfig before 'xend start':
> >
> > [root@dbarrera ~]# ifconfig
> > eth0 Link encap:Ethernet HWaddr 00:0D:60:F0:C5:C8
> > inet addr:9.53.94.235 Bcast:9.53.94.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:99 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:88 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:12299 (12.0 KiB) TX bytes:11426 (11.1 KiB)
> > Base address:0x2000 Memory:e8100000-e8120000
> >
> > 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:26 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:2216 (2.1 KiB) TX bytes:2216 (2.1 KiB)
> >
> > [root@dbarrera ~]# brctl show
> > bridge name bridge id STP enabled interfaces
> > [root@dbarrera ~]#
> >
> > when 'xend start' is entered, these messages appear on console:
> > store_evtchn = 16
> > XENBUS xs_read_watch: 0
> >
> > ifconfig AFTER 'xend start'eth0 Link encap:Ethernet
> > HWaddr 00:0D:60:F0:C5:C8
> > inet addr:9.53.94.235 Bcast:9.53.94.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:380 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:28046 (27.3 KiB) TX bytes:426 (426.0 b)
> >
> > 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:26 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:2216 (2.1 KiB) TX bytes:2216 (2.1 KiB)
> >
> > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> > inet addr:9.53.94.235 Bcast:9.53.94.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
> > RX packets:501 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:111 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:44601 (43.5 KiB) TX bytes:12036 (11.7 KiB)
> > Base address:0x2000 Memory:e8100000-e8120000
> >
> > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:3 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:380 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:426 (426.0 b) TX bytes:28046 (27.3 KiB)
> >
> > xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:375 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:22208 (21.6 KiB) TX bytes:0 (0.0 b)
> >
> > [root@dbarrera ~]# brctl show
> > bridge name bridge id STP enabled interfaces
> > xen-br0 8000.feffffffffff no peth0
> > vif0.0
> >
> > xen-br0 is up, but networking is dead. This is different from
> > the previous issues where xen-br0 was not coming up, but when
> > started manually networking resumed.
> >
> > On 2 other machines, networking is up and working, Dom0 has
> > networking running correctly, but when I start a domU, it
> > does not have networking. I have 3 similar machines, only one
> > of which has a domU with working network; the other two
> > don't, even though they have very similar setups. This *may*
> > end up being a setup issue (although these same setups worked
> > before), but I can't figure out what that could
> > be--everything looks like it is supposed to be.
> >
> > > So, ifdown does succeed in taking the interface down. I
> > wander why the routes aren't getting removed?
> > >
> > > Could you do:
> > > ifconfig
> > > netstat -rn
> > > ifdown eth0
> > > netstat -rn
> > > ifconfig
> > >
> > > Thanks,
> > > Ian
> > >
> > >
> > > > -----Original Message-----
> > > > From: Zhai, Edwin [mailto:edwin.zhai@intel.com]
> > > > Sent: 16 August 2005 16:57
> > > > To: Ian Pratt
> > > > Cc: xen-devel@lists.xensource.com; ian.pratt@cl.cam.ac.uk
> > > > Subject: RE: new /etc/xen/network script
> > > >
> > > >
> > > > ***Before***
> > > > [root@vt-edwin ~]# ifconfig
> > > >
> > > > eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B
> > > >
> > > > inet addr:172.16.219.31 Bcast:172.16.219.255
> > > > Mask:255.255.255.0
> > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > > >
> > > > RX packets:127 errors:0 dropped:0 overruns:0
> > > > frame:0
> > > > TX packets:65 errors:0 dropped:0 overruns:0
> > > > carrier:0
> > > > collisions:0 txqueuelen:1000
> > > >
> > > > RX bytes:18387 (17.9 KiB) TX bytes:6072 (5.9 KiB)
> > > >
> > > >
> > > >
> > > > 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:16 errors:0 dropped:0 overruns:0 frame:0
> > > >
> > > > TX packets:16 errors:0 dropped:0 overruns:0
> > > > carrier:0
> > > > collisions:0 txqueuelen:0
> > > >
> > > > RX bytes:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB)
> > > >
> > > > ***After ifdown eth0 ***
> > > > [root@vt-edwin ~]# ifconfig
> > > >
> > > > 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:16 errors:0 dropped:0 overruns:0 frame:0
> > > >
> > > > TX packets:16 errors:0 dropped:0 overruns:0
> > > > carrier:0
> > > > collisions:0 txqueuelen:0
> > > >
> > > > RX bytes:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB)
> > > >
> > > >
> > > > but
> > > > [root@vt-edwin ~]# ifconfig -a
> > > > eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B
> > > > inet addr:172.16.219.31 Bcast:172.16.219.255
> > > > Mask:255.255.255.0
> > > > BROADCAST MULTICAST MTU:1500 Metric:1
> > > > RX packets:182 errors:0 dropped:0 overruns:0 frame:0
> > > > TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
> > > > collisions:0 txqueuelen:1000
> > > > RX bytes:25284 (24.6 KiB) TX bytes:6196 (6.0 KiB)
> > > >
> > > > 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:16 errors:0 dropped:0 overruns:0 frame:0
> > > > TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
> > > > collisions:0 txqueuelen:0
> > > > RX bytes:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB)
> > > >
> > > > 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)
> > > >
> > > > Ian Pratt <mailto:m+Ian.Pratt@cl.cam.ac.uk> scribbled on
> > > > 2005年8月16日 23:41:
> > > >
> > > > >> ian,
> > > > >> as the discussion in this thread, service os netwok will
> > > > break after
> > > > >> xend start.
> > > > >> this simple patch can work on my mahine.
> > > > >> but strange error still occur in xend.log and xend start
> > > > takes more
> > > > >> time with ifdown/ifup.
> > > > >
> > > > > I guess the patch can't do any harm, but why doesn't ifdown
> > > > remove the
> > > > > routes?
> > > > >
> > > > > Before starting xend, please can you post the output of the
> > > > following
> > > > > sequence:
> > > > >
> > > > > ifconfig
> > > > > ifdown eth0
> > > > > ifconfig
> > > > >
> > > > > Thanks,
> > > > > Ian
> > > > >
> > > > >
> > > > >> @@ -192,6 +192,7 @@
> > > > >> ifconfig p${netdev} -arp down
> > > > >> ifconfig p${netdev} hw ether fe:ff:ff:ff:ff:ff
> > > > >> ifconfig ${netdev} hw ether ${mac}
> > > > >> + del_addrs p${netdev}
> > > > >> add_to_bridge ${bridge} vif0.0
> > > > >> add_to_bridge ${bridge} p${netdev}
> > > > >> ip link set vif0.0 up
> > > > >>
> > > > >>
> > > > >> --------------xend.log------------------------
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + set -e
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + OP=start
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + shift
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + for arg in '"$@"'
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + export bridge=xen-br0
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + bridge=xen-br0
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + for arg in '"$@"'
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + export antispoof=no
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + antispoof=no
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + bridge=xen-br0
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + netdev=eth0
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + antispoof=no
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + echo '*network start bridge=xen-br0 netdev=eth0 antispoof=no'
> > > > >> [2005-08-16 23:14:19 xend] INFO (__init__:988)
> > [network-bridge]
> > > > >> network start bridge=xen-br0 netdev=eth0 antispoof=no
> > [2005-08-16
> > > > >> 23:14:19 xend] ERROR (__init__:988) [network-bridge] +
> > > > case ${OP} in
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + op_start
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + '[' xen-br0 == null ']' [2005-08-16 23:14:19 xend] ERROR
> > > > >> (__init__:988) [network-bridge] + create_bridge xen-br0
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + local bridge=xen-br0
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + brctl show
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + grep -q xen-br0
> > > > >> [2005-08-16 23:14:19 xend] INFO (__init__:988) EVENT>
> > xend.start
> > > > >> 0
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + brctl addbr xen-br0
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + brctl stp xen-br0 off
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + brctl setfd xen-br0 0
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + ifconfig xen-br0 up
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + ifconfig
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + grep -q veth0
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + ifconfig veth0
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + grep -q veth0
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > > > [network-bridge] ++
> > > > >> ifconfig eth0
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > > > [network-bridge] ++
> > > > >> grep HWadd
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > > > [network-bridge] ++
> > > > >> sed -e 's/.*\(..:..:..:..:..:..\).*/\1/'
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + mac=00:0C:F1:FE:4C:5B
> > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + ifdown eth0
> > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988)
> > > > [network-bridge] + ip
> > > > >> link set eth0 name peth0
> > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988)
> > > > [network-bridge] + ip
> > > > >> link set veth0 name eth0
> > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + ifconfig peth0 -arp down
> > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + ifconfig peth0 hw ether fe:ff:ff:ff:ff:ff
> > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + ifconfig eth0 hw ether 00:0C:F1:FE:4C:5B
> > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + del_addrs peth0
> > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + local src=peth0
> > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988)
> > > > [network-bridge] + ip
> > > > >> addr show dev peth0
> > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988)
> > [network-bridge]
> > > > >> + egrep '^ *inet '
> > > > >>
> > > > >> Best Rgds
> > > > >> Edwin
> > > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xensource.com
> > > http://lists.xensource.com/xen-devel
> > --
> > Regards,
> >
> > David F Barrera
> > Linux Technology Center
> > Systems and Technology Group, IBM
> >
> > "The wisest men follow their own direction. "
> > Euripides
> >
> >
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
next prev parent reply other threads:[~2005-08-16 18:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 16:51 RE: new /etc/xen/network script Ian Pratt
2005-08-16 18:53 ` David F Barrera [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-14 18:53 Stephan Böni
2005-10-14 23:23 ` Ewan Mellor
2005-10-14 18:29 Stephan Böni
2005-10-14 18:22 Stephan Böni
2005-10-14 17:16 Stephan Böni
2005-10-14 17:55 ` David F Barrera
2005-08-17 16:34 Ian Pratt
2005-08-17 18:17 ` David F Barrera
2005-08-17 13:30 Zhai, Edwin
2005-08-17 12:47 Zhai, Edwin
2005-08-17 12:34 Ian Pratt
2005-08-17 12:37 ` Nivedita Singhvi
2005-08-17 16:31 ` David F Barrera
2005-08-17 12:19 Zhai, Edwin
2005-08-17 12:34 ` Nivedita Singhvi
2005-08-17 11:44 Ian Pratt
2005-08-17 12:12 ` Nivedita Singhvi
2005-08-17 11:32 Ian Pratt
2005-08-17 11:43 ` Nivedita Singhvi
2005-08-16 16:27 Ian Pratt
2005-08-16 16:41 ` David F Barrera
2005-08-17 10:02 ` Nivedita Singhvi
2005-08-17 11:21 ` Nivedita Singhvi
2005-08-17 11:34 ` Nivedita Singhvi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1124218423.4598.23.camel@localhost.localdomain \
--to=dfbp@us.ibm.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=edwin.zhai@intel.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.