Jack Smith
2008-Jan-08 03:39 UTC
[Fedora-xen] Routing doesn''t work when I boot with the Xen kernel
I have a choice of kernels to boot with in Grub, 2.6.21-2952.fc8xen 2.6.23.9-85.fc8 2.6.23.1-42.fc8 As far as I can see, I have networking set up the same on all three. (Besides, wouldn''t they use the same configuration files at boot time?) My problem is, when I boot with the xen kernel, I can''t get out through my router. I can ping everything on my eth0 or eth1 networks, just not go through my eth0 Linksys router. The only difference I''ve been able to see is that something called "peth0" uses the same card as the NIC my router is on. Is this getting in the way somehow? eth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8 inet addr:192.168.1.151 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:47 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:494 (494.0 b) TX bytes:6566 (6.4 KiB) eth1 Link encap:Ethernet HWaddr 00:17:31:01:D0:20 inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::217:31ff:fe01:d020/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29 errors:0 dropped:0 overruns:0 frame:0 TX packets:63 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2412 (2.3 KiB) TX bytes:8491 (8.2 KiB) Interrupt:23 Base address:0xe000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8504 errors:0 dropped:0 overruns:0 frame:0 TX packets:8504 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:10008668 (9.5 MiB) TX bytes:10008668 (9.5 MiB) peth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8 inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:53 errors:0 dropped:0 overruns:0 frame:0 TX packets:121 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5414 (5.2 KiB) TX bytes:14547 (14.2 KiB) Interrupt:18 virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:32 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:5156 (5.0 KiB) Thanks, -- Jack Smith English doesn''t borrow from other languages -- English follows other languages down dark alleys and takes what it wants.
John Summerfield
2008-Jan-08 06:56 UTC
Re: [Fedora-xen] Routing doesn''t work when I boot with the Xen kernel
Jack Smith wrote:> I have a choice of kernels to boot with in Grub, > 2.6.21-2952.fc8xen > 2.6.23.9-85.fc8 > 2.6.23.1-42.fc8 > > As far as I can see, I have networking set up the same on all three. > (Besides, wouldn''t they use the same configuration files at boot time?) My > problem is, when I boot with the xen kernel, I can''t get out through my > router. I can ping everything on my eth0 or eth1 networks, just not go > through my eth0 Linksys router. The only difference I''ve been able to see > is that something called "peth0" uses the same card as the NIC my router is > on. Is this getting in the way somehow? > > eth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8 >Check that the NICs are both connected to the same wire with the different kernels. if I read it correctly, they''re both the same brand. Maybe the kernels detect them differently. Unplug one, test with ethtool: sudo ethtool eth0 Find and inspect the configuration files: [summer@potoroo ~]$ locate ifcfg-eth /etc/sysconfig/network-scripts/ifcfg-eth0 [summer@potoroo ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 # Intel Corporation 82566DM Gigabit Network Connection DEVICE=eth0 BOOTPROTO=dhcp HWADDR=00:18:71:84:A5:9E ONBOOT=yes [summer@potoroo ~]$ The HWADDR line ties the MAC address to the interface configuration, but I''ve never had the need to explore how it works, and I can imagine some different ways. -- Cheers John -- spambait 1aaaaaaa@coco.merseine.nu Z1aaaaaaa@coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-)
Dustin Henning
2008-Jan-08 13:21 UTC
RE: [Fedora-xen] Routing doesn''t work when I boot with the Xen kernel
When the xend service starts, it creates bridges and virtual
interfaces attached to those bridges. I am not so familiar with it to tell
you how to correct your problem on a permanent basis, but I can tell you
that perhaps the network script isnt preserving your routes. Check your
routes and see if a default route to the Linksys still exists. It also
seems to me like F8 may use a different default xen network script, so
depending on what you want to do, you many need to change the network script
in xens config file. This advice may be legacy, as I know Fedoras
implementation gets more and more custom with each release, and I generally
fall back on old xen configuration techniques in spite of that, so this may
not be the route you want to take.
Dustin
From: fedora-xen-bounces@redhat.com [mailto:fedora-xen-bounces@redhat.com]
On Behalf Of Jack Smith
Sent: Monday, January 07, 2008 22:40
To: fedora-xen@redhat.com
Subject: [Fedora-xen] Routing doesn''t work when I boot with the Xen
kernel
I have a choice of kernels to boot with in Grub,
2.6.21-2952.fc8xen
2.6.23.9-85.fc8
2.6.23.1-42.fc8
As far as I can see, I have networking set up the same on all three.
(Besides, wouldn''t they use the same configuration files at boot
time?) My
problem is, when I boot with the xen kernel, I can''t get out through my
router. I can ping everything on my eth0 or eth1 networks, just not go
through my eth0 Linksys router. The only difference I''ve been able to
see
is that something called "peth0" uses the same card as the NIC my
router is
on. Is this getting in the way somehow?
eth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8
inet addr:192.168.1.151 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:494 (494.0 b) TX bytes:6566 (6.4 KiB)
eth1 Link encap:Ethernet HWaddr 00:17:31:01:D0:20
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::217:31ff:fe01:d020/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29 errors:0 dropped:0 overruns:0 frame:0
TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2412 (2.3 KiB) TX bytes:8491 (8.2 KiB)
Interrupt:23 Base address:0xe000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8504 errors:0 dropped:0 overruns:0 frame:0
TX packets:8504 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10008668 (9.5 MiB) TX bytes:10008668 (9.5 MiB)
peth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8
inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:53 errors:0 dropped:0 overruns:0 frame:0
TX packets:121 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5414 (5.2 KiB) TX bytes:14547 (14.2 KiB)
Interrupt:18
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:5156 (5.0 KiB)
Thanks,
--
Jack Smith
English doesn''t borrow from other languages -- English follows other
languages down dark alleys and takes what it wants.
Jack Smith
2008-Jan-08 14:27 UTC
Re: [Fedora-xen] Routing doesn''t work when I boot with the Xen kernel
I have no idea why, but the problem corrected itself overnight. Something, either in Fedora, the router, Comcast or somewhere must have run and fixed the problem. I have no idea how. On Jan 8, 2008 8:21 AM, Dustin Henning <Dustin.Henning@prd-inc.com> wrote:> When the xend service starts, it creates bridges and virtual > interfaces attached to those bridges. I am not so familiar with it to > tell > you how to correct your problem on a permanent basis, but I can tell you > that perhaps the network script isn''t preserving your routes. Check your > routes and see if a default route to the Linksys still exists. It also > seems to me like F8 may use a different default xen network script, so > depending on what you want to do, you many need to change the network > script > in xen''s config file. This advice may be legacy, as I know Fedora''s > implementation gets more and more custom with each release, and I > generally > fall back on old xen configuration techniques in spite of that, so this > may > not be the route you want to take. > Dustin > > From: fedora-xen-bounces@redhat.com [mailto:fedora-xen-bounces@redhat.com] > On Behalf Of Jack Smith > Sent: Monday, January 07, 2008 22:40 > To: fedora-xen@redhat.com > Subject: [Fedora-xen] Routing doesn''t work when I boot with the Xen kernel > > I have a choice of kernels to boot with in Grub, > 2.6.21-2952.fc8xen > 2.6.23.9-85.fc8 > 2.6.23.1-42.fc8 > > As far as I can see, I have networking set up the same on all three. > (Besides, wouldn''t they use the same configuration files at boot time?) My > problem is, when I boot with the xen kernel, I can''t get out through my > router. I can ping everything on my eth0 or eth1 networks, just not go > through my eth0 Linksys router. The only difference I''ve been able to see > is that something called "peth0" uses the same card as the NIC my router > is > on. Is this getting in the way somehow? > eth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8 > inet addr:192.168.1.151 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:10 errors:0 dropped:0 overruns:0 frame:0 > TX packets:47 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:494 (494.0 b) TX bytes:6566 (6.4 KiB) > > eth1 Link encap:Ethernet HWaddr 00:17:31:01:D0:20 > inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0 > inet6 addr: fe80::217:31ff:fe01:d020/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:29 errors:0 dropped:0 overruns:0 frame:0 > TX packets:63 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:2412 (2.3 KiB) TX bytes:8491 (8.2 KiB) > Interrupt:23 Base address:0xe000 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:8504 errors:0 dropped:0 overruns:0 frame:0 > TX packets:8504 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:10008668 (9.5 MiB) TX bytes:10008668 (9.5 MiB) > > peth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8 > inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:53 errors:0 dropped:0 overruns:0 frame:0 > TX packets:121 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:5414 (5.2 KiB) TX bytes:14547 (14.2 KiB) > Interrupt:18 > > virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:32 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:5156 (5.0 KiB) > > Thanks, > > -- > Jack Smith > > English doesn''t borrow from other languages -- English follows other > languages down dark alleys and takes what it wants. > > >-- Jack Smith English doesn''t borrow from other languages -- English follows other languages down dark alleys and takes what it wants.