On Tue, Jul 26, 2016 at 7:43 PM, Volker Kuhlmann <[email protected]> wrote: > On Tue 26 Jul 2016 09:41:37 NZST +1200, Karl Fife wrote: > >> Interesting how it failed: The fried port 'simply' broke >> connectivity for the interface's LAN segment. Everything else >> continued to work. I kinda didn't believe the report that Internet >> was out for the one LAN, since the other was not. > > I don't think this is that unusual or surprising. You get the same > effect if you plug in a real POTS line into an Ethernet port... > >> After some >> testing, I found the system would not come up after reboot because >> it had gone into port reassignment mode since the config made >> reference to a non-existent interface. > > I find this really really annoying of pfsense! Especially for headless > systems. Hey, why run with only one interface and some functionality > missing when one can run with functionality of zero point zero instead? >
Because any fall back there is potentially unsafe. Say you have igb0-igb5, and igb2 dies. Now your igb3 is igb2, igb4 is igb3, etc. Any assumptions you make about what's correct are potentially dangerous, and likely to be wrong. We've had discussions around that in greater depth multiple times over the years. Any way you do it has edge case bugs, is dangerous and/or wouldn't be right anyway. _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
