still can''t get packets to route correctly if xen sets up xen-br0.
Here are interfaces after xend start
eth0 Link encap:Ethernet HWaddr 00:D0:59:CD:55:9B
inet addr:10.128.207.119 Bcast:10.128.255.255 Mask:255.255.0.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)
xen-br0 Link encap:Ethernet HWaddr 00:D0:59:CD:55:9B
inet addr:10.128.207.119 Bcast:10.128.255.255
Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19 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:10414 (10.1 Kb) TX bytes:0 (0.0 b)
brctl show gives this:
bridge name bridge id STP enabled interfaces
xen-br0 8000.00d059cd559b no eth0
Start the domain, get this:
vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
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:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
bridge name bridge id STP enabled interfaces
xen-br0 8000.00d059cd559b no eth0
vif3.0
no iptables in the default xen build for dom0, so I assume these are not
an issue. (I just now put them in but they''re empty anyway).
After running a dhcp client on plan 9, I can see packets:
vif3.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:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1240 (1.2 Kb) TX bytes:0 (0.0 b)
I can tcpdump packets:
11:23:16.172028 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x5dfa8f8a
secs:8 file ""[|bootp]
11:23:20.177092 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x73978e0d
file ""[|bootp]
11:23:24.171624 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x73978e0d
secs:4 file ""[|bootp]
but they''re not making it through to anywhere else.
So bridging does not seem to be happening.
If I do a showmacs I can even see the dom1 mac in there.
Now, if I do this:
ifconfig eth0 172.16.233.1
ifconfig xen-br0 172.16.233.1
everything is fine -- no shock, the plan 9 domain has ip 172.16.233.201.
So, if xen-br0 is actually bridging, I can''t see it happening.
What am I missing?
ron
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel
On Fri, Dec 31, 2004 at 10:17:34AM -0700, Ronald G. Minnich wrote:> Start the domain, get this: > vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > What am I missing?I bet the FE:FF:FF:FF:FF:FF hardware address is special in some way or another and the bridge code doesn''t like it. The default ones are much saner ;-) christian ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> On Fri, Dec 31, 2004 at 10:17:34AM -0700, Ronald G. Minnich wrote: > > Start the domain, get this: > > vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > > > What am I missing? > > I bet the FE:FF:FF:FF:FF:FF hardware address is special in some way or > another and the bridge code doesn''t like it. The default ones are much > saner ;-) > > christianI made that the new default, and noone else has complained about it not working. :-) -- Keir ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Fri, 31 Dec 2004, Christian Limpach wrote:> On Fri, Dec 31, 2004 at 10:17:34AM -0700, Ronald G. Minnich wrote: > > Start the domain, get this: > > vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > > > What am I missing? > > I bet the FE:FF:FF:FF:FF:FF hardware address is special in some way or > another and the bridge code doesn''t like it. The default ones are much > saner ;-)I''m not sure that would explain why it all starts working when I set the IP address on eth0 and xen-br0. I don''t think that''s it. Also, ... I can do this ifconfig xen-br0 down brctl del xen-br0 ifconfig vif3.0 172.16.233.200 and it all starts working. It''s something going on with the bridge. ron ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Ronald G. Minnich wrote:>still can''t get packets to route correctly if xen sets up xen-br0. > >Here are interfaces after xend start > >eth0 Link encap:Ethernet HWaddr 00:D0:59:CD:55:9B > inet addr:10.128.207.119 Bcast:10.128.255.255 Mask:255.255.0.0 > >[snip]>xen-br0 Link encap:Ethernet HWaddr 00:D0:59:CD:55:9B > inet addr:10.128.207.119 Bcast:10.128.255.255 > >[snip]>but they''re not making it through to anywhere else. > >So bridging does not seem to be happening. > >If I do a showmacs I can even see the dom1 mac in there. > >Now, if I do this: >ifconfig eth0 172.16.233.1 >ifconfig xen-br0 172.16.233.1 > >everything is fine -- no shock, the plan 9 domain has ip 172.16.233.201. > >So, if xen-br0 is actually bridging, I can''t see it happening. > > >What IS your network address for eth0 and xen-br0 anyway? 172.16.233.0 or 10.128.207.0? Generally speaking, devices in a bridge should be on the same network. Regards, Fajar ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Sun, 2 Jan 2005, Fajar A. Nugraha wrote:> What IS your network address for eth0 and xen-br0 anyway? > 172.16.233.0 or 10.128.207.0? > Generally speaking, devices in a bridge should be on the same network.yes, I realized yesterday it is a bridge. Foolish of me. I knew there was some cog in my brain that was stuck. That said, if I bridge vifX.0 and eth1, and do a simple dhcp from the plan 9 side, the NAT box on my network never responds, even though I see the dhcp on eth1. But at least the cog in my brain has been jolted loose. ron ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel