Lastest Updates

[Kyawa]

There are several threads about the updates from 16.5.2. What is unclear is whether or not the ever growing list of issues apply to Untangle branded hardware. I have a 6-month old z4 Plus that I purchased from Untangle. I have temporarily disabled updates. Can someone from Arista clarify the problems with the updates and make a recommendation as to what users should do?

[bcarmichael]

We have not had any reports of this issue affecting the z4 appliance so I recommend for you to upgrade. The issue of interfaces changing their association is unfortunately something that has affected custom hardware installations for many years, and it's a difficult problem to solve. That said, we have made fixing this issue a top priority for the next release.

[Kyawa]

Thanks

[sky-knight]

We have not had any reports of this issue affecting the z4 appliance so I recommend for you to upgrade. The issue of interfaces changing their association is unfortunately something that has affected custom hardware installations for many years, and it's a difficult problem to solve. That said, we have made fixing this issue a top priority for the next release.

Beware, both Caswell and Lanner appliances in my fleet have reordered interfaces. So your stuff is not magic, and it's NOT immune. But it is limited to hardware configurations that have expansion bay interfaces installed. The order of the interfaces will remain unchanged, but the order the interface sets are stacked up next to each other can shift.

[oj88]

I admit that I am in no way, shape or form, a developer. But is it really so hard for Untangle to include lines of code somewhere to have the configuration file include the last-known interface assignments and/or mapping? Bind it, for instance, to the port's MAC address.

So regardless how the PHYs were initiated in-order or out-of-order during boot-up of the underlying OS, Untangle can just read said interface mapping from the config file as it loads up.

Now, if the PHYs were actually modified (ie. NICs were added, removed, or changed), I would understand the mapping going haywire.... and that's acceptable. But if nothing changed on the hardware, I think it's reasonable expectation that the mapping remain the same after every reboot or even software updates.

[sky-knight]

I admit that I am in no way, shape or form, a developer. But is it really so hard for Untangle to include lines of code somewhere to have the configuration file include the last-known interface assignments and/or mapping? Bind it, for instance, to the port's MAC address.

So regardless how the PHYs were initiated in-order or out-of-order during boot-up of the underlying OS, Untangle can just read said interface mapping from the config file as it loads up.

Now, if the PHYs were actually modified (ie. NICs were added, removed, or changed), I would understand the mapping going haywire.... and that's acceptable. But if nothing changed on the hardware, I think it's reasonable expectation that the mapping remain the same after every reboot or even software updates.

You mean these? https://wiki.debian.org/NetworkInter...NG_.LINK_FILES

Yes...