[CentOS-virt] proper bridging technoque
aurfalien at gmail.com
Sat Nov 23 00:19:03 UTC 2013
So let me first give an analogy.
So I have a flat tire.
No, its inflated and looks fine.
No, I'm tellin ya its flat.
I just checked tire pressure, all is well.
Holy sh$#, the road it jacked up giving e the illusion of a flat!
So I am able to ping my br6 int from another host so I assumed it was up. But upon examining ip route, I see my def route is my primary interface br0 so it answered back even though I ping br6.
I walk over to the KVM host and eth6 is physically unplugged!
Its in now and all is well.
Dude, so sorry.
Now, to fix it so a ping will result in accuracy.
On Nov 22, 2013, at 3:51 PM, Digimer wrote:
> On 22/11/13 18:11, aurfalien wrote:
>> Cancel my last email as I peeked at a server I set up last year w/o issue having multiple interfaces. Its working no issue.
>> I don't recall but can you gentlemen tell me if there are any routes that need to be set?
>> My guest VMs being on a 2nd or 3rd NIC interface can't get a IP via DHCP and when set statically cannot send/recv packets.
>> I vaguely recall setting routes on the working box from last year but forgot :)
>> - aurf
> We're not all gentlemen. ;)
> So you have multiple separate networks? If so, then I assume you have a
> bridge per network? If so, then the server you configure will see the
> outside network that the given bridge connects to.
> Remember, a bridge is just a "software network switch". If the "switch"
> is not connected to the server with a DHCP server, it will not get an
> answer to DHCP requests.
> Papers and Projects: https://alteeve.ca/w/
> What if the cure for cancer is trapped in the mind of a person without
> access to education?
> CentOS-virt mailing list
> CentOS-virt at centos.org
More information about the CentOS-virt