Ok this should be super simple and it worked before bookworm. Now not so much.
Simple rundown is as follows:
pi 4B
Wifi is DHCP and is the network with a valid intenet gateway. Ip of 192.168.254.X gateway of .254
Wired is a standalone network no internet connection. 192.168.1.X no gateway
Used to be able to talk to the .1.X network via the Pi but now I cant.
The wifi works so I can get to the Pi, and its set as auto connect with priority 10.
The wired connection is set to auto connect with priority 1 and has the static IP set.
When I run ifconfig I get this.
pi@pi:~ $ ifconfig eth0
eth0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether dc:a6:32:d0:a5:73 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
no ip shows.
This is where I'm confused, its like its not even making it an available interface to be used but if I show the setup through nmcli the ip is there.
Simple rundown is as follows:
pi 4B
Wifi is DHCP and is the network with a valid intenet gateway. Ip of 192.168.254.X gateway of .254
Wired is a standalone network no internet connection. 192.168.1.X no gateway
Used to be able to talk to the .1.X network via the Pi but now I cant.
The wifi works so I can get to the Pi, and its set as auto connect with priority 10.
The wired connection is set to auto connect with priority 1 and has the static IP set.
When I run ifconfig I get this.
pi@pi:~ $ ifconfig eth0
eth0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether dc:a6:32:d0:a5:73 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
no ip shows.
This is where I'm confused, its like its not even making it an available interface to be used but if I show the setup through nmcli the ip is there.
Statistics: Posted by libram11 — Fri Nov 01, 2024 4:43 am — Replies 0 — Views 12