Solved Upgrade to V18 - MAC Address changed

[wpanagotopulos]

Hi All:

I completed our upgrade from V16 to V18. (The Debian Linux ISO version)

When the upgrade completed, I could not access the Management Page at the original IP address. I had the MAC address loaded into the router DHCP reservation to stream line things

The IT team found that the MAC address reported from the machine changed to a much longer MAC - See the screenshot below.

The original MAC was "b8:ca:3a:86:39:d6" and as you can see, is still embedded in the "new" MAC.

Whilst we got it working by loading the new MAC into the DHCP reservation, can someone tell me what went wrong or is this standard operation going from V16 to V18?

BR,
Bill.

 

[ChrisC_3CX]

This is actually a change in behavior from Debian 9 to Debian 10. It does not change the MAC address per se, rather, changes what is advertised on the network level. There is enough info online about this should you wish to restore the previous behavior however I'm afraid it's not something that can be rectified via 3CX.

 

[wpanagotopulos]

This is actually a change in behavior from Debian 9 to Debian 10. It does not change the MAC address per se, rather, changes what is advertised on the network level. There is enough info online about this should you wish to restore the previous behavior however I'm afraid it's not something that can be rectified via 3CX.

Thanks, Chris.

I strongly suspected a Debian change and I searched here but not exhaustively. I did a cursory web search but obviously came up short.

I will dig in again and work it out on my own.

BR, Bill.

 

[ChrisC_3CX]

I did find this in our forums which you might find useful: https://www.3cx.com/community/threads/linux-upgrade-aborted-troubleshooting-tips.84511/post-396357

However I do have to mention that this is purely OS configuration not directly related to 3CX so we cannot really provide any information or even confirm it will work. I suggest thoroughly researching these settings and making sure that you fully understand what you are changing and what the behavior will be before you apply any modifications.

 

[wpanagotopulos]

Thanks, Chris.

I understand - I got up to speed on the whole "Client ID" issue - which is really not an "issue", but part of the DHCP operation. Was a bit eye-opening.

Decided to simply go along with the new client id; the windows DHCP server accepted the long client ID and everything is working well.

Additionally, I think your advice is spot-on; I had momentarily pondered editing the "dhclient.conf" file but quickly dismissed it because I didn't want to mess with the base OS config.

 

[ChrisC_3CX]

Glad to see you managed to sort everything out!

Do let us know if anything else comes up!