June 20, 20197 yr I moved most of my server functions off my server and onto bare metal for the 24/7 operated things, so I could tinker about without ruining something vital for the network. I did a clean install and reconfigured the network according to screenshots I took beforehand (it's identical to what it used to be, I've quadruple checked). Everything worked exactly as it should before the reset configured exactly the same. I have a 10Gb/s PCIe network card and that's the connection I've set up and used. The only cable between the switch and the server is CAT6 in the PCIe RJ45 jack. My problem now when trying to f.ex ping 8.8.8.8 the command window tries to ping through the eth1 (motherboard) 192.x.x.69 instead of eth0 (PCIe) 192.x.x.60 like it used to. Why? Isn't eth0 the first priority? System info Command line
June 21, 20197 yr Author # route outputs Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default X.X.X.1 X.X.X.0 UG 0 0 0 br1 So the br1 interface is default (bonded to eth1). My goal would be to set br0 as default. Alternatively add eth0 to br1 (but that feels alot like using duct tape) So, does anyone know how to change default interface?
June 21, 20197 yr Author Turned off bonding and bridging on eth1 and adding eth1 to br0 made br0 the default interface :shrug: Is there a way to mark this solved or something?
June 23, 20197 yr You can edit the first post and change the topic to tag it as solved. That said. you didn't really provide any info, but was both your interfaces configured with a gateway? this is one of the causes for this behavior.
Archived
This topic is now archived and is closed to further replies.