(09-May-2019, 11:52 AM)bobzy Wrote: Done, full stack kernel installedit's br0. br as in bridge. bond is for teaming/LACP (trunking).![]()
how I do for the bridged interface, bond0 ?
(09-May-2019, 11:52 AM)bobzy Wrote: I put the same static IPv4 for both eth0 and eth1 ?Not quite. Refer here.
As an example, it'll be something like:
auto lo
iface lo inet loopback
# Bridge between eth0 and eth1
auto br0
iface br0 inet dhcp
address 192.168.1.10
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 192.168.1.1
bridge_ports eth0 eth1
bridge_stp off
bridge_fd 0
bridge_maxwait 0
If your home network is very "chatty", there will be a lot of traffic being "cut & pasted" between eth0 and eth1. This more or less will affect the latency of your PC so AQ will be YMMV. What this bridge can do however is it'll potentially isolate any electrical noise on the LAN side (e.g. if you switch/router is running a dirty SMPS).
So if you have a lousy switch, there is potential of an improvement.
However, once you get better switches down the road, there'll be a flip - this bridge is potentially going to be a bottle neck.
Almost worth writing a blog article on this. Just not too sure where/how to begin as there're so many topics to cover.