| View previous topic :: View next topic |
| Author |
Message |
juanatix
n00b
Joined: 13 Jun 2024
Posts: 6
Location: USA
|
 Posted: Thu Jun 13, 2024 5:45 pm Post subject: Bridge Member Acquiring IP Address Despite config_eth1=null |
 |
|
Hello Gentoo Forums,
Long time Debian/Devuan user - recently took the Gentoo plunge and up until my recently my only question was, "why didn't I do this sooner?" I've exhausted my own research capabilities and hope someone here can shine a light on a situation for me.
I've setup a bridge using /etc/conf.d/net, which was pretty straight forward. The bridge is working, br0 has an IP address and I have network connectivity, routes, etc. The problem is, a member of the bridge (eth1) is still receiving an IP address via DHCP despite setting config_eth1="null" in /etc/conf.d/net.
Here's my /etc/conf.d/net:
| Code: |
config_eth0="null"
config_eth1="null"
bridge_br0="eth1"
config_br0="10.50.20.113 netmask 255.255.255.0"
routes_br0="default via 10.50.20.1"
bridge_forward_delay_br0=0
bridge_hello_time_br0=1000
|
Here's the output of ifconfig:
| Code: |
sysop@localhost /etc $ ifconfig br0
br0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
inet 10.50.20.113 netmask 255.255.255.0 broadcast 10.50.20.255
ether 52:33:a4:fc:99:7f txqueuelen 1000 (Ethernet)
RX packets 83387 bytes 94215419 (89.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 56602 bytes 7720216 (7.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
sysop@localhost /etc $ ifconfig eth1
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.50.20.128 netmask 255.255.255.0 broadcast 10.50.20.255
ether 71:51:3c:b7:2a:d9 txqueuelen 1000 (Ethernet)
RX packets 100855 bytes 84403294 (80.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 53673 bytes 8092566 (7.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
sysop@localhost /etc $
|
As you can see, eth1 has an IP address and I'm not sure what else to look at. /etc/dhcpcd.conf doesn't have anything for eth1. I tried deleting /etc/init.d/net.eth1 but that didn't help, so I added it back. I think it's causing issues because there are also routes in place for eth1 and web apps keep saying "lost connection" or "check your internet connection" intermittently. 10.50.20.128 (eth1) is not allowed out by the upstream firewall, so perhaps Gentoo is trying to send packets out eth1, causing connection interruptions. Maybe a different issue.
Either way, how can I ensure eth1 doesn't pull an IP address via DHCP? |
|
| Back to top |
|
 |
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1921
|
| Posted: Thu Jun 13, 2024 5:49 pm Post subject: |
|
|
| Please show the output of rc-update show and rc-status |
|
| Back to top |
|
|
juanatix
n00b
Joined: 13 Jun 2024
Posts: 6
Location: USA
|
| Posted: Thu Jun 13, 2024 5:51 pm Post subject: |
|
|
| grknight wrote: | | Please show the output of rc-update show and rc-status |
| Code: |
sysop@localhost /etc $ rc-update show
binfmt | boot
bootmisc | boot
cgroups | sysinit
devfs | sysinit
dhcpcd | default
dmesg | sysinit
elogind | boot
fsck | boot
hostname | boot
hwclock | boot
keymaps | boot
killprocs | shutdown
kmod-static-nodes | sysinit
libvirtd | default
local | default nonetwork
localmount | boot
loopback | boot
modules | boot
mount-ro | shutdown
mtab | boot
net.br0 | default
netmount | default
procfs | boot
root | boot
save-keymaps | boot
save-termencoding | boot
savecache | shutdown
seedrng | boot
sshd | default
swap | boot
sysctl | boot
sysfs | sysinit
sysklogd | default
systemd-tmpfiles-setup | boot
systemd-tmpfiles-setup-dev | sysinit
termencoding | boot
udev | sysinit
udev-trigger | sysinit
sysop@localhost /etc $ rc-status
Runlevel: default
net.br0 [ started ]
sysklogd [ started ]
dhcpcd [ started ]
libvirtd [ started ]
netmount [ stopped ]
sshd [ started ]
local [ started ]
Dynamic Runlevel: hotplugged
Dynamic Runlevel: needed/wanted
dbus [ started ]
virtlogd [ started ]
Dynamic Runlevel: manual
opensnitch [ started ]
sysop@localhost /etc $
|
|
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1921
|
| Posted: Thu Jun 13, 2024 5:54 pm Post subject: |
|
|
This is your problem. Do not start dhcpcd in manager mode if you are doing it all via netifrc. It will assume control of all interfaces by default.
tl;dr answer: rc-service dhcpcd stop; rc-update del dhcpcd default
If you need "eth0" to use dhcp, then change the config_eth0="dhcp" and dhcpcd will be called the correct way per interface when net.eth0 is started. |
|
| Back to top |
|
|
juanatix
n00b
Joined: 13 Jun 2024
Posts: 6
Location: USA
|
| Posted: Thu Jun 13, 2024 6:05 pm Post subject: |
|
|
| grknight wrote: |
This is your problem. Do not start dhcpcd in manager mode if you are doing it all via netifrc. It will assume control of all interfaces by default.
tl;dr answer: rc-service dhcpcd stop; rc-update del dhcpcd default |
Well that was simple enough, wow. Thank you! I'll review the handbook and my installation notes to see where I went wrong. Admittedly this is a little different than how Devuan handles it with /etc/network/interfaces so today I learned. Thanks again for the quick response. |
|
| Back to top |
|
|
nicop
Tux's lil' helper
Joined: 10 Apr 2014
Posts: 95
|
|
| Back to top |
|
|
|
Networking & Security
