All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jaggi, Manish" <Manish.Jaggi@caviumnetworks.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: PV Bridged DHCP (domU) Not working on Xen 4.5rc1 arm64
Date: Thu, 22 Jan 2015 13:12:24 +0000	[thread overview]
Message-ID: <1421932343533.53626@caviumnetworks.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 885 bytes --]

Hi All,


I am running ubuntu-trusty arm64 server image as dom0. I have enabled CONFIG_BRIDGE, CONFIG_IPV6, CONFIG_NETFILTER in linux 3.18. Xen version is 4.5 rc1.


in Dom0 post boot did the following


a) brctl addbr xenbr0;

b) brctl addif xenbr0 eth0

c) Updated /etc/sysctl.conf

net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0

d)

iptables -I FORWARD -m physdev --physdev-is-bridged -j ACCEPT


e) sysctl -p /etc/sysctl.conf
f) /etc/init.d/networking restart
g) dhclient xenbr0

xenbr0 gets an IP.

h)vif = [ 'bridge=xenbr0' ]. Started domU
g) domU got an ip.

Now the problem is domU is able to ping dom0 but not any other host. While dom0 is able to ping any host.


There could be something missing in my steps, can you please help

-Regards
manish

?






[-- Attachment #1.2: Type: text/html, Size: 2257 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

             reply	other threads:[~2015-01-22 13:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 13:12 Jaggi, Manish [this message]
2015-01-22 14:33 ` PV Bridged DHCP (domU) Not working on Xen 4.5rc1 arm64 Ian Campbell

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=1421932343533.53626@caviumnetworks.com \
    --to=manish.jaggi@caviumnetworks.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.