Unless the issue is with the appliances available from Untangle, hardware issues with third party hardware are not fixed.Quote:
Originally Posted by Rumboogy
Printable View
Unless the issue is with the appliances available from Untangle, hardware issues with third party hardware are not fixed.Quote:
Originally Posted by Rumboogy
Even for something as glaring as this? I mean, doesn't Untangle remember the mappings and/or isn't it saved in a config file somewhere? If so, all it needs to do is look up this setting during start-up and it should never go wrong. Like maybe map the MAC address to an interface role.Quote:
Originally Posted by jcoffin
Or am I being overly simplistic?
It's not based on MAC address. It's based on the NIC dev name. eth0, eth1, etc. Debian assigns them based on up order. It appears your system brings the NICs up in random order.
Yes, which is normal behavior from the Debian kernel, it can be controlled... but it shouldn't be happening. If you've got hardware bringing NICs up in a random order, that's a massive issue with the mainboard, not Debian.
If you've got such a mainboard, as a person that rolled your own hardware it is UP TO YOU to solve the problem. You took on that risk when you decided to use your own hardware.
The instructions for fixing this are on Debian's wiki: https://wiki.debian.org/NetworkInter...NG_.LINK_FILES
Thank you. That makes sense.Quote:
Originally Posted by jcoffin
Though, it could also be said that Debian isn't detecting the NICs in the order it originally saw them. IDK.. this is probably way too deep for me. I was just speaking from a end user's perspective. The simpleton in me thinks that Untangle shouldn't rely on the dev names, given how they can be unreliable in certain situations (ie. adding/removing/changing NICs).
But at least now I understand what Untangle's position is.
The problem is those device names are how you configure any given bit of hardware. Eth0 is actually not a default name anymore... that's a legacy flag setting Untangle is using on boot to emulate the old behavior.
The new process uses names based on positions on the PCI bus, which isn't supposed to change... but still can. This started with Debian 9, but was enforced with Debian 10. It all boils down to how the PCI bus enumerates the devices when you turn your computer on.
The really ugly part is, with Debian 8 and 9 once IPTables saw a given interface on a given name it would generate a rules file for you that would lock a mac address to a device name. This prevented all this tomfoolery, but the process was deprecated. And here we are...
The really sad thing is the whole point of Debian's slower release cadence (and Untangle's reliance on Debian as a base) is Debian has a reputation of doing more testing and being very careful before pushing things to stable... precisely to avoid this kind of break.
When does 16.0 come out?Quote:
Originally Posted by jcoffin
Hopefully when it is ready. There is a beta that has been out for a while now.Quote:
Originally Posted by Rumboogy
Does anyone know the planned release date?Quote:
Originally Posted by donhwyo