Re: Network Bridge - Do not pass back to router

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Hello,

Sorry for the late reply, I was busy over the weekend.

The output of ip ro is:

default via 192.168.2.1 dev br0 proto dhcp src 192.168.2.2 metric 425
192.168.2.0/24 dev br0 proto kernel scope link src 192.168.2.2 metric 425

Nothing seems wrong here, unless there is a priority system? As the default is to pass back to the router, and then it is to the bridge to handle it, so maybe it is a priority related issue within the routing table?

The truth is that it is a very strange behavior. Especially considering that the 192.168.2.0/24 network is directly connected and therefore would not have to go to the router at all.
Out of curiosity, what happens when you physically disconnect the server from the router, does it communicate with the LXC containers?

If I unplugged the Ethernet cable, yes the lxc containers would lose network access, their only route is via a single cable.

Thanks for the help,
--
Polarian
GPG signature: 0770E5312238C760
Website: https://polarian.dev
JID/XMPP: polarian@xxxxxxxxxxxx

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux