[Xen-users] Re: Troubleshooting Bridging

[Adam Carheden <adam.carheden@xxxxxxxxx>]

It turned out to by my (well, my org's) dhcp server (the `redmond`
brand). My domu was a physical machine that I migrated to Xen.
Apparently the dhcp server didn't like the fact that a machine with
the same hostname was using a different mac address (which seems
strange, given that we change NIC's all the time.)

To solve the problem I... (on DomU)
a) deleted /var/lib/dhpc/* (this did nothing)
b) Changed the machine's hostname (this fixed it)

Before I make an ars of myself and proliferate the MS-bashing linux
user stereotype, can anyone take a guess as to weather the MS DHCP
server or my dhcpcd-2.0.0 (gentoo 2005.1) failed to follow protocol?

Thanks Nivedita for your replies!
--
Adam

On 12/6/05, Nivedita Singhvi <niv@xxxxxxxxxx> wrote:
> Adam Carheden wrote:
>
> > No, both the netmask and broadcast are correct and were assigned to
> > Dom0 by DHCP.
>
> Any chance you could upgrade to 3.0?
> Your config doesn't look ok by current mainline
> xen (not sure if SuSE changed anything) - for instance
> you don't have a vif0.x, and it's hard to remember
> what the earlier scripts did..You can put a set -x
> in your network script and step through the logs
> to see exactly what it's doing..
>
> thanks,
> Nivedita
>
> > Address:   192.168.109.26
> > Netmask:   255.255.254.0 = 23
> > Network:   192.168.108.0/23
> > Broadcast: 192.168.109.255
> > HostMin:   192.168.108.1
> > HostMax:   192.168.109.254
> > Hosts/Net: 510
> >
> >
> > On 12/5/05, Nivedita Singhvi <niv@xxxxxxxxxx> wrote:
> >
> >>Adam Carheden wrote:
> >>
> >>
> >>>dom0:/etc/xen # iptables --list
> >>>Chain INPUT (policy ACCEPT)
> >>>target     prot opt source               destination
> >>>
> >>>Chain FORWARD (policy ACCEPT)
> >>>target     prot opt source               destination
> >>>ACCEPT     all  --  anywhere             anywhere            PHYSDEV
> match
> >>>--physdev-in eth0
> >>>
> >>>Chain OUTPUT (policy ACCEPT)
> >>>target     prot opt source               destination
> >>>dom0:/etc/xen # brctl show
> >>>bridge name     bridge id               STP enabled     interfaces
> >>>xen-br0         8000.00105aac4561       no              eth0
> >>>                                                        vif7.0
> >>>                                                        vif8.0
> >>>dom0:/etc/xen # ifconfig -a
> >>>eth0      Link encap:Ethernet  HWaddr 00:10:5A:AC:45:61
> >>>          inet addr:192.168.109.26  Bcast:192.168.109.255  Mask:
> >>>255.255.254.0
> >>
> >>Mismatch between your mask and broadcast. Is that 254 a typo?
> >>
> >>thanks,
> >>Nivedita
> >>
> >>
> >>
> >>
> >>>          inet6 addr: fe80::210:5aff:feac:4561/64 Scope:Link
> >>>          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
> >>>          RX packets:53322 errors:0 dropped:0 overruns:0 frame:0
> >>>          TX packets:34477 errors:0 dropped:0 overruns:0 carrier:0
> >>>          collisions:0 txqueuelen:1000
> >>>          RX bytes:53151039 (50.6 Mb)  TX bytes:4320684 (4.1 Mb)
> >>>          Interrupt:9 Base address:0x1000
> >>>
> >>>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:13705 errors:0 dropped:0 overruns:0 frame:0
> >>>          TX packets:13705 errors:0 dropped:0 overruns:0 carrier:0
> >>>          collisions:0 txqueuelen:0
> >>>          RX bytes:1004429 (980.8 Kb)  TX bytes:1004429 (980.8 Kb)
> >>>
> >>>sit0      Link encap:IPv6-in-IPv4
> >>>          NOARP  MTU:1480  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)
> >>>
> >>>vif7.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> >>>          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> >>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >>>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >>>          TX packets:0 errors:0 dropped:420 overruns:0 carrier:0
> >>>          collisions:0 txqueuelen:0
> >>>          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> >>>
> >>>vif8.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> >>>          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> >>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >>>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >>>          TX packets:0 errors:0 dropped:411 overruns:0 carrier:0
> >>>          collisions:0 txqueuelen:0
> >>>          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> >>>
> >>>xen-br0   Link encap:Ethernet  HWaddr 00:10:5A:AC:45:61
> >>>          inet addr:192.168.109.26  Bcast:192.168.109.255  Mask:
> >>>255.255.255.255
> >>>          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
> >>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >>>          RX packets:52126 errors:0 dropped:0 overruns:0 frame:0
> >>>          TX packets:33778 errors:0 dropped:0 overruns:0 carrier:0
> >>>          collisions:0 txqueuelen:0
> >>>          RX bytes:52281788 (49.8 Mb)  TX bytes:4217308 (4.0 Mb)
> >>>
> >>>Any hints?
> >>>
> >>>--
> >>>Adam Carheden
> >>>
> >>>
> >>>
> >>>------------------------------------------------------------------------
> >>>
> >>>_______________________________________________
> >>>Xen-users mailing list
> >>>Xen-users@xxxxxxxxxxxxxxxxxxx
> >>>http://lists.xensource.com/xen-users
> >>
> >>
> >>
> >
> >
> >
> > --
> > Adam Carheden
> >
>
>
>


--
Adam Carheden

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