Initial thought is a routing issue particularly with multiple NICs.
What does 'ip r s' reveal?
That was it! ip r s showed that I had the local facing NIC (eth1) as the
gateway, which caused all outgoing packets to be routed to the local network
DUH!.
Yup been there before.
So
On 07/20/2011 01:24 AM, James Hogarth wrote:
Initial thought is a routing issue particularly with multiple NICs.
What does 'ip r s' reveal?
That was it! ip r s showed that I had the local facing NIC (eth1) as the
gateway, which caused all outgoing packets to be routed to the local network
I built a CentOS 6 machine to host several CentOS 6 guest servers. As all
guests will be Internet facing I set up the host with two bridged NICs and
assigned an Internet facing IP address to br0 and a local IP address to br1.
Each guest was installed using br0 and br1 with virtio drivers. On
On 19/07/2011 08:14, James Hogarth wrote:
I built a CentOS 6 machine to host several CentOS 6 guest servers.
As all guests will be Internet facing I set up the host with two
bridged NICs and assigned an Internet facing IP address to br0 and a
local IP address to br1.
Each guest was
On 07/19/2011 07:52 PM, Khusro Jaleel wrote:
A bit of a long shot but does turning on STP on the br* interfaces help?
I vaguely remember I had to do the following on one of my machines that
uses bonding + bridges:
# brctl stp br0 on
I have put this in the machines' /etc/rc.local so it's
On 07/19/2011 12:14 AM, James Hogarth wrote:
I built a CentOS 6 machine to host several CentOS 6 guest servers. As all
guests will be Internet facing I set up the host with two bridged NICs and
assigned an Internet facing IP address to br0 and a local IP address to br1.
Each guest
I built a CentOS 6 machine to host several CentOS 6 guest servers. As all
guests will be Internet facing I set up the host with two bridged NICs and
assigned an Internet facing IP address to br0 and a local IP address to br1.
Each guest was installed using br0 and br1 with virtio drivers. On
7 matches
Mail list logo
