thr3ads.net - Xen users - Bridged, have IP, can''t ping anything, including the gateway [May 2013]

If this information is useful, please help other people find it:
Share via:

Matt Baer

2013-May-13 15:18 UTC

Bridged, have IP, can''t ping anything, including the gateway

First off, let me start by saying that I am new to Xen.  I do have
experience in Virtualization, but mainly VirtualBox and VMWare.

I''m attempting to test Xen in preparation for the physical server
arrival
this Friday.  The dom0 is currently running on a VirtualBox VM, which
I''m
wondering if that could be the issue that I''m having.

I''m almost 100% up and running. I worked through some issues I had with
bridging the network.  I''ve finally got it to a point where I am
getting a
DHCP address.  The dom0 machine is .190 and the domU is .213.  I cannot
ping the gateway nor anything else from the domU (Debian) nor can I ping
the domU from anything else on my network.  I haven''t seen anything in
IPTables that would indicate any issue there.  Does anyone have any other
suggestions?

-- 
Thanks,
Matt Baer
Network Manager
Leaf River Telephone Company
102 W Second Street
Leaf River, IL
 815.738.2211 - Main Office
866.738.2211 - Toll Free
mbaer@lrnet1.com


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Simon Jones

2013-May-13 15:36 UTC

head link

Re: Bridged, have IP, can''t ping anything, including the gateway

Your /etc/network/interfaces file should look something like this.. this works
for me but I am on a hardware platform for dom0 rather than a vm.

auto lo
    iface lo inet loopback

    iface eth1 inet manual
    auto xenbr0

    iface xenbr0 inet dhcp
        bridge_ports eth1

Simon Jones
SEMTEC Limited T/A SAQ
SERVICE AND QUALITY SINCE 1996
Sales: 01730 71 00 80
Technical Support: 08707 37 77 01
F: 08707 37 77 08
E: simon@saq.net<mailto:simon@saq.net>
W: www.saq.net<http://www.saq.net/>
Email: support@saq.net<mailto:support@saq.net>

*** Please note our terms of business have recently changed, visit
www.saq.net<http://www.saq.net> to review these changes, your continued
use of our products and services are deemed to be an acceptance of these terms
and conditions.***

HELP!! Need technical support?  SAQ Support Plus, expert help per incident or on
contract - call sales 01730 71 00 80 for a quotation
www.saq.net/support<http://www.saq.net/support>.
NEW!! Web site design, development and marketing services available - to
increase your hits please call sales on 01730 71 00 80 for details!
FAST!! - 40Mb Fibre Optic Broadband is here -Broadband from less than £16 per
month.

What our customer say:
"In a day and age when a mechanical voice offering a seemingly endless
range of options to choose from in pursuit of that great misnomer
''customer service'' is the norm, one company stands head and
shoulders above the rest for real customer service. Internet service provider,
SAQ delivers reassuring technical support, to even its smallest clients, from
the moment the phone is answered by a courteous, knowledgeable and helpful real
life person - that is customer service!"
SAQ is the trading name of SEMTEC Limited, a private limited company registered
in England and Wales under Co Reg No 06481952 and has its registered office at
18 Chapel Street, Petersfield, Hampshire, GU32 3DZ.
Disclaimer & Confidentiality: This e-mail and its attachments are intended
for the above named only and may be confidential. If they have come to you in
error you must take no action based on them, nor must you copy or show them to
anyone; please reply to this e-mail and highlight the error.
Security Warning: Please note that this e-mail has been created in the knowledge
that Internet e-mail is not a 100% secure communications medium. We advise that
you understand and observe this lack of security when e-mailing us.
P Please consider the environment before printing this e-mail.

From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org]
On Behalf Of Matt Baer
Sent: 13 May 2013 16:19
To: xen-users@lists.xen.org
Subject: [Xen-users] Bridged, have IP, can''t ping anything, including
the gateway

First off, let me start by saying that I am new to Xen.  I do have experience in
Virtualization, but mainly VirtualBox and VMWare.

I''m attempting to test Xen in preparation for the physical server
arrival this Friday.  The dom0 is currently running on a VirtualBox VM, which
I''m wondering if that could be the issue that I''m having.

I''m almost 100% up and running. I worked through some issues I had with
bridging the network.  I''ve finally got it to a point where I am
getting a DHCP address.  The dom0 machine is .190 and the domU is .213.  I
cannot ping the gateway nor anything else from the domU (Debian) nor can I ping
the domU from anything else on my network.  I haven''t seen anything in
IPTables that would indicate any issue there.  Does anyone have any other
suggestions?

--
Thanks,
Matt Baer
Network Manager
Leaf River Telephone Company
102 W Second Street
Leaf River, IL
815.738.2211 - Main Office
866.738.2211 - Toll Free
mbaer@lrnet1.com<mailto:mbaer@lrnet1.com>


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Matt Baer

2013-May-13 15:50 UTC

head link

Re: Bridged, have IP, can''t ping anything, including the gateway

My /etc/network/interfaces looks exactly like that, but my physical
interface is eth0.  I am getting a DHCP address, so something is getting
passed through.  Give the circumstances, the only things I can think of is
that there''s a firewall issue or the fact that it''s run
through a VM.
Also, I forgot to mention on my original post that the VM has a bridged
interface as well, I don''t think that should matter, but just throwing
it
out there.


On Mon, May 13, 2013 at 10:36 AM, Simon Jones <Simon@saq.net> wrote:
>  Your /etc/network/interfaces file should look something like this.. this
> works for me but I am on a hardware platform for dom0 rather than a vm.***
> *
>
> ** **
>
> auto lo****
>
>     iface lo inet loopback****
>
> ** **
>
>     iface eth1 inet manual****
>
>     auto xenbr0****
>
> ** **
>
>     iface xenbr0 inet dhcp****
>
>         bridge_ports eth1****
>
> ** **
>
> Simon Jones
> SEMTEC Limited T/A SAQ****
>
> *SERVICE AND QUALITY SINCE 1996*
> Sales: 01730 71 00 80
> Technical Support: 08707 37 77 01
> F: 08707 37 77 08
> E: simon@saq.net
> W: www.saq.net
> Email: support@saq.net****
>
> * *
>
> **** Please note our terms of business have recently changed, visit
> www.saq.net to review these changes, your continued use of our products
> and services are deemed to be an acceptance of these terms and
> conditions.****
>
> *
> HELP!! Need technical support?  SAQ Support Plus, expert help per
> incident or on contract – call sales 01730 71 00 80 for a quotation
> www.saq.net/support.*
>
> *NEW!! Web site design, development and marketing services available – to
> increase your hits please call sales on 01730 71 00 80 for details!*
>
> *FAST!! - 40Mb Fibre Optic Broadband is here –Broadband from less than
> £16 per month.*
>
> * *
>
> *What our customer say:*
>
> *“**In a day and age when a mechanical voice offering a seemingly endless
> range of options to choose from in pursuit of that great misnomer ‘customer
> service’ is the norm, one company stands head and shoulders above the rest
> for real customer service. Internet service provider, SAQ delivers
> reassuring technical support, to even its smallest clients, from the moment
> the phone is answered by a courteous, knowledgeable and helpful real life
> person – that is customer service!”***
>
> *SAQ is the trading name of SEMTEC Limited, a private limited company
> registered in England and Wales under Co Reg No **06481952** **and has
> its registered office at 18 Chapel Street, Petersfield, Hampshire, GU32
3DZ.
> ***
>
> *Disclaimer & Confidentiality: This e-mail and its attachments are
> intended for the above named only and may be confidential. If they have
> come to you in error you must take no action based on them, nor must you
> copy or show them to anyone; please reply to this e-mail and highlight the
> error.*
>
> *Security Warning: Please note that this e-mail has been created in the
> knowledge that Internet e-mail is not a 100% secure communications medium.
> We advise that you understand and observe this lack of security when
> e-mailing us.*****
>
> *P** **Please consider the environment before printing this e-mail.*****
>
> ** **
>
> *From:* xen-users-bounces@lists.xen.org [mailto:
> xen-users-bounces@lists.xen.org] *On Behalf Of *Matt Baer
> *Sent:* 13 May 2013 16:19
> *To:* xen-users@lists.xen.org
> *Subject:* [Xen-users] Bridged, have IP, can''t ping anything,
including
> the gateway****
>
> ** **
>
> First off, let me start by saying that I am new to Xen.  I do have
> experience in Virtualization, but mainly VirtualBox and VMWare.
> ****
>
> ** **
>
> I''m attempting to test Xen in preparation for the physical server
arrival
> this Friday.  The dom0 is currently running on a VirtualBox VM, which
I''m
> wondering if that could be the issue that I''m having.
>
> I''m almost 100% up and running. I worked through some issues I had
with
> bridging the network.  I''ve finally got it to a point where I am
getting a
> DHCP address.  The dom0 machine is .190 and the domU is .213.  I cannot
> ping the gateway nor anything else from the domU (Debian) nor can I ping
> the domU from anything else on my network.  I haven''t seen
anything in
> IPTables that would indicate any issue there.  Does anyone have any other
> suggestions?****
>
>
> --
> Thanks,
> Matt Baer
> Network Manager
> Leaf River Telephone Company
> 102 W Second Street
> Leaf River, IL
> 815.738.2211 - Main Office
> 866.738.2211 - Toll Free
> mbaer@lrnet1.com ****
>


-- 
Thanks,
Matt Baer
Network Manager
Leaf River Telephone Company
102 W Second Street
Leaf River, IL
 815.738.2211 - Main Office
866.738.2211 - Toll Free
mbaer@lrnet1.com


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Ian Campbell

2013-May-13 15:54 UTC

head link

Re: Bridged, have IP, can''t ping anything, including the gateway

On Mon, 2013-05-13 at 16:18 +0100, Matt Baer wrote:
> I''m almost 100% up and running. I worked through some issues I had
> with bridging the network.  I''ve finally got it to a point where I
am
> getting a DHCP address.  The dom0 machine is .190 and the domU
> is .213.  I cannot ping the gateway nor anything else from the domU
> (Debian) nor can I ping the domU from anything else on my network.  I
> haven''t seen anything in IPTables that would indicate any issue
there.
> Does anyone have any other suggestions?
Please provide details of your actual network configuration.

http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen has some examples of
the sorts of things, "brctl show", "ifconfig -a", config
files, that
sort of thing.

Ian.

Matt Baer

2013-May-13 16:06 UTC

head link

Re: Bridged, have IP, can''t ping anything, including the gateway

From dom0

*root@debian-xen:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 08:00:27:30:b9:53
          inet6 addr: fe80::a00:27ff:fe30:b953/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2449702 errors:0 dropped:0 overruns:0 frame:0
          TX packets:138140 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:281121959 (268.0 MiB)  TX bytes:12538172 (11.9 MiB)

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:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:728 (728.0 B)  TX bytes:728 (728.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 PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:29951 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2324864 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:3215716 (3.0 MiB)  TX bytes:269574095 (257.0 MiB)

xenbr0    Link encap:Ethernet  HWaddr 08:00:27:30:b9:53
          inet addr:192.168.168.190  Bcast:192.168.168.255
Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe30:b953/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2460954 errors:0 dropped:0 overruns:0 frame:0
          TX packets:108212 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:245381651 (234.0 MiB)  TX bytes:8905548 (8.4 MiB)*

*

root@debian-xen:~# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.08002730b953       no              eth0
                                                        vif1.0*

*Network Portion of xend-config.sxp* *on dom0*

*##
# NOTE:
# Please read /usr/share/doc/xen-utils-common/README.Debian for Debian
specific
# informations about the network setup.

##
# To bridge network traffic, like this:
#
# dom0: ----------------- bridge -> real eth0 -> the network
#                            |
# domU: fake eth0 -> vifN.0 -+
#
# use
#
#(network-script network-bridge)

#
# Your default ethernet device is used as the outgoing interface, by
default.
# To use a different one (e.g. eth1) use
#
# (network-script ''network-bridge netdev=eth0'')
#
# The bridge is named xenbr0, by default.  To rename the bridge, use
#
# (network-script ''network-bridge bridge=<name>'')
#
# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges, and
# two fake interfaces per guest domain.  To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as
appropriate.
#

# The script used to control virtual interfaces.  This can be overridden on
a
# per-vif basis when creating a domain or a configuring a new vif.  The
# vif-bridge script is designed for use with the network-bridge script, or
# similar configurations.
#
# If you have overridden the bridge name using
# (network-script ''network-bridge bridge=<name>'') then
you may wish to do
the
# same here.  The bridge name can also be set when creating a domain or
# configuring a new vif, but a value specified here would act as a default.
#
# If you are using only one bridge, the vif-bridge script will discover
that,
# so there is no need to specify it explicitly.
#
# (vif-script vif-bridge)


## Use the following if network traffic is routed, as an alternative to the
# settings for bridged networking given above.
#(network-script network-route)
#(vif-script     vif-route)
*
*
## Use the following if network traffic is routed with NAT, as an
alternative
# to the settings for bridged networking given above.
#(network-script network-nat)
#(vif-script     vif-nat)*


*FROM domU

**root@test-deb-2:/etc# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:3e:ac:f1:11
          inet addr:192.168.168.213  Bcast:192.168.168.255
Mask:255.255.255.0
          inet6 addr: fe80::216:3eff:feac:f111/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2327701 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29977 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:237398493 (226.4 MiB)  TX bytes:3643922 (3.4 MiB)
          Interrupt:17

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:2990 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2990 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1050903 (1.0 MiB)  TX bytes:1050903 (1.0 MiB)**



*


On Mon, May 13, 2013 at 10:54 AM, Ian Campbell
<Ian.Campbell@citrix.com>wrote:
> On Mon, 2013-05-13 at 16:18 +0100, Matt Baer wrote:
>
> > I''m almost 100% up and running. I worked through some issues
I had
> > with bridging the network.  I''ve finally got it to a point
where I am
> > getting a DHCP address.  The dom0 machine is .190 and the domU
> > is .213.  I cannot ping the gateway nor anything else from the domU
> > (Debian) nor can I ping the domU from anything else on my network.  I
> > haven''t seen anything in IPTables that would indicate any
issue there.
> > Does anyone have any other suggestions?
>
> Please provide details of your actual network configuration.
>
> http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen has some examples of
> the sorts of things, "brctl show", "ifconfig -a",
config files, that
> sort of thing.
>
> Ian.
>
>
>

-- 
Thanks,
Matt Baer
Network Manager
Leaf River Telephone Company
102 W Second Street
Leaf River, IL
 815.738.2211 - Main Office
866.738.2211 - Toll Free
mbaer@lrnet1.com


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Xen users - May 2013 - Bridged, have IP, can't ping anything, including the gateway

Bridged, have IP, can''t ping anything, including the gateway

Re: Bridged, have IP, can''t ping anything, including the gateway

Re: Bridged, have IP, can''t ping anything, including the gateway

Re: Bridged, have IP, can''t ping anything, including the gateway

Re: Bridged, have IP, can''t ping anything, including the gateway