I have been trying for a couple days to try to get this to work, and
I''m stumped. I''ve seen wiki''s on how people do it,
but I must
completely be missing something.
My provider gives me two network connections:
eth0: private
eth1: public
My eth1 interface has a /29, and I am also getting an additional /29
routed to me (so they are routing it to the IP address that is set on
my eth1 interface). So I have two /29''s, one which is currently bound
to eth1 (subnet A), and one which is just routed to me and not bound
(subnet B). I only want to use one of these /29''s for
domU''s.. the
one that is being routed to me (subnet B)
I want to bridge subnet B with my Xen domU''s. I took one IP from
subnet B and assigned it to "dummy0", and I can ping it from the
outside world, bind to it and make connections outbound, and all is
well.
However, I cannot get DomU''s to communicate with anything (not even
the dom0) if they use an IP address from subnet B.
"brctl status" shows that xenbr1 is connected to vif0.1 and pdummy,
and that vif1.0 is also bound to it.
bridge name bridge id STP enabled interfaces
virbr0 8000.000000000000 yes
xenbr1 8000.feffffffffff no vif1.0
pdummy0
vif0.1
Now, given that I am trying to do a network install of CentOS on the
guest, I can''t actually get into the shell and do an
"ifconfig" or a
"tcpdump" as I don''t have any domU''s that are
created that I can
attach to a console, so my troubleshooting is limited to the dom0 side.
I''ve check iptables, and nothing is set to be dropped/rejected.
xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:60 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:10140 (9.9 KiB) TX bytes:0 (0.0 b)
vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:412 (412.0 b) TX bytes:1008 (1008.0 b)
pdummy0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:0 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:0 (0.0 b) TX bytes:9276 (9.0 KiB)
dummy0 Link encap:Ethernet HWaddr B6:CE:E7:E8:3E:9C
inet addr:208.x.x.x Bcast:208.x.x.x Mask:255.255.255.248
inet6 addr: fe80::b4ce:e7ff:fee8:3e9c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 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:0 (0.0 b) TX bytes:9462 (9.2 KiB)
tcpdump''s are not showing any traffic on xenbr1, vif1.0, pdummy0, or
dummy0. I''m not even sure if tcpdump will show anything on interfaces
like that. I am also showing nothing on eth1 for anything coming from
this domU I am trying to install.
I''m at a loss?
Kristofer
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Well I feel completely stupid. After a few days of messing with this.... I shouldn''t even admit how dumb this was. I have a /29.. I was using .240 on the dummy0 interface on dom0.. Uhh, yeah.. I can''t do math and realize that .240 was the network address. :-\ Oops. Setting dummy0 to .241, which is the correct first address of the subnet, and things are now routing. *sigh* On Jul 28, 2008, at 8:23 PM, Kristofer wrote:> I have been trying for a couple days to try to get this to work, and > I''m stumped. I''ve seen wiki''s on how people do it, but I must > completely be missing something. > > My provider gives me two network connections: > > eth0: private > eth1: public > > My eth1 interface has a /29, and I am also getting an additional /29 > routed to me (so they are routing it to the IP address that is set > on my eth1 interface). So I have two /29''s, one which is currently > bound to eth1 (subnet A), and one which is just routed to me and not > bound (subnet B). I only want to use one of these /29''s for > domU''s.. the one that is being routed to me (subnet B) > > I want to bridge subnet B with my Xen domU''s. I took one IP from > subnet B and assigned it to "dummy0", and I can ping it from the > outside world, bind to it and make connections outbound, and all is > well. > > However, I cannot get DomU''s to communicate with anything (not even > the dom0) if they use an IP address from subnet B. > > "brctl status" shows that xenbr1 is connected to vif0.1 and pdummy, > and that vif1.0 is also bound to it. > > bridge name bridge id STP enabled interfaces > virbr0 8000.000000000000 yes > xenbr1 8000.feffffffffff no vif1.0 > pdummy0 > vif0.1 > > Now, given that I am trying to do a network install of CentOS on the > guest, I can''t actually get into the shell and do an "ifconfig" or a > "tcpdump" as I don''t have any domU''s that are created that I can > attach to a console, so my troubleshooting is limited to the dom0 > side. > > I''ve check iptables, and nothing is set to be dropped/rejected. > > xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:60 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:10140 (9.9 KiB) TX bytes:0 (0.0 b) > > vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:7 errors:0 dropped:0 overruns:0 frame:0 > TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:32 > RX bytes:412 (412.0 b) TX bytes:1008 (1008.0 b) > > pdummy0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 b) TX bytes:9276 (9.0 KiB) > > dummy0 Link encap:Ethernet HWaddr B6:CE:E7:E8:3E:9C > inet addr:208.x.x.x Bcast:208.x.x.x Mask:255.255.255.248 > inet6 addr: fe80::b4ce:e7ff:fee8:3e9c/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 b) TX bytes:9462 (9.2 KiB) > > tcpdump''s are not showing any traffic on xenbr1, vif1.0, pdummy0, or > dummy0. I''m not even sure if tcpdump will show anything on > interfaces like that. I am also showing nothing on eth1 for > anything coming from this domU I am trying to install. > > I''m at a loss? > > > Kristofer > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Well I feel completely stupid. After a few days of messing with > this.... I shouldn''t even admit how dumb this was. > > I have a /29.. I was using .240 on the dummy0 interface on dom0.. Uhh, > yeah.. I can''t do math and realize that .240 was the network > address. :-\ > > Oops. Setting dummy0 to .241, which is the correct first address of > the subnet, and things are now routing. > > *sigh*Don''t feel too bad. I''m made mistakes at least twice as dumb as that before :) James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Don''t feel too bad. I''m made mistakes at least twice as dumb as that > before :)On the upside, I learned more about Xen networking than I ever cared to know. :-) Kristofer _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users