All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bulpin <james@xensource.com>
To: Kir <kir@npptema.ru>
Cc: xen-devel@lists.xensource.com
Subject: Re: bridge problem on FC3. Please help!
Date: Thu, 30 Jun 2005 23:47:25 +0100	[thread overview]
Message-ID: <42C4767D.40205@xensource.com> (raw)
In-Reply-To: <732405245.20050630141137@npptema.ru>

Does your iptables FORWARD chain in dom0 prevent the forwarding of
packets across the bridge?

James

Kir wrote:
> Hello all,
> 
> I've got some strange problem with bridge. Ping from DomU doesn't
> work, but I can see correct icmp packets on the bridge.
> On domU I run:
> ping 213.33.197.1
> 
> On Dom0 I see:
> tcpdump -i xen-br0
> 12:41:41.697372 IP 213.33.197.2 > 213.33.197.1: icmp 64: echo request seq 1
> 12:41:41.697709 IP 213.33.197.1 > 213.33.197.2: icmp 64: echo reply seq 1
> 
> I've spent 4 days playing with bridge, but no result! Please help me!
> Fedora 3 and xen 2.0.6 are installed on my box.
> 
> Bridge config for dom0 is:
> bridge name     bridge id               STP enabled     interfaces
> xen-br0         8000.0004762663d3       no              eth0
>                                                         vif2.0
> Router config of Dom0 is:
> 213.33.197.0    *               255.255.255.192 U     0      0        0 xen-br0
> default         213.33.197.1    0.0.0.0         UG    0      0        0 xen-br0
> 
> ip addr show (Dom0) is:
> 1: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
>     link/ether 00:04:76:26:63:d3 brd ff:ff:ff:ff:ff:ff
>     inet 213.33.197.3/26 brd 213.33.197.63 scope global eth0
> 3: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
> 4: xen-br0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
>     link/ether 00:04:76:26:63:d3 brd ff:ff:ff:ff:ff:ff
>     inet 213.33.197.3/32 brd 213.33.197.63 scope global xen-br0
> 6: vif2.0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
>     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> 
> DomU has vif:
> (vif
>      (idx 0)
>      (vif 0)
>      (mac aa:10:00:00:00:11)
>      (vifname vif2.0)
>      (bridge xen-br0)
>      (evtchn 12 4)
>      (index 0)
>  )
> 
> 

  reply	other threads:[~2005-06-30 22:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 10:11 bridge problem on FC3. Please help! Kir
2005-06-30 22:47 ` James Bulpin [this message]
2005-07-04  8:01   ` Re[2]: " Kir
  -- strict thread matches above, loose matches on Subject: below --
2005-06-30  8:49 Kir

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42C4767D.40205@xensource.com \
    --to=james@xensource.com \
    --cc=kir@npptema.ru \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.