# Problem Obtaining IP Address via DHCP - Beryl AX **URL:** \ **Category:** VPN, DNS, Leaks\ **Created:** [November 20, 2024, 2:43pm UTC](https://forum.gl-inet.com/t/problem-obtaining-ip-address-via-dhcp-beryl-ax/50743 "2024-11-20T14:43:40Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Drinyth](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/d/ed655f/32.png) [@Drinyth](https://forum.gl-inet.com/u/Drinyth)\ **Post date:** [November 20, 2024, 2:43pm UTC](https://forum.gl-inet.com/t/problem-obtaining-ip-address-via-dhcp-beryl-ax/50743/1 "2024-11-20T14:43:40Z")
I have purchased a Beryl AX travel router and am having problems trying to have the router successfully obtain an IP address while in repeater mode with a fixed MAC Address. I will be going on a cruise soon and understand that I will be required to use the same MAC address with my service there (we are limited to the number of devices we can use - hence the purchase of this travel router) and as a result am trying to test out that configuration at home. When using a fixed MAC address, the Beryl AX does not actually ever seem to apply the IP that the DHCP server sends it: \<134\>1 2024-11-18T16:00:43-06:00 opnsense kea-dhcp4 19415 - [meta sequenceId="123"] INFO [kea-dhcp4.leases.0x249f7e216d00] DHCP4\_LEASE\_OFFER [hwtype=1 56:05:4f:03:93:29], cid=[no info], tid=0x7ec9ee1b: lease 192.168.30.100 will be offered \<134\>1 2024-11-18T16:00:46-06:00 opnsense kea-dhcp4 19415 - [meta sequenceId="127"] INFO [kea-dhcp4.leases.0x249f7e216d00] DHCP4\_LEASE\_OFFER [hwtype=1 56:05:4f:03:93:29], cid=[no info], tid=0x7ec9ee1b: lease 192.168.30.100 will be offered \<134\>1 2024-11-18T16:00:49-06:00 opnsense kea-dhcp4 19415 - [meta sequenceId="131"] INFO [kea-dhcp4.leases.0x249f7e216d00] DHCP4\_LEASE\_OFFER [hwtype=1 56:05:4f:03:93:29], cid=[no info], tid=0x7ec9ee1b: lease 192.168.30.100 will be offered \<134\>1 2024-11-18T16:00:52-06:00 opnsense kea-dhcp4 19415 - [meta sequenceId="135"] INFO [kea-dhcp4.leases.0x249f7e216d00] DHCP4\_LEASE\_OFFER [hwtype=1 56:05:4f:03:93:29], cid=[no info], tid=0x7ec9ee1b: lease 192.168.30.100 will be offered \<134\>1 2024-11-18T16:00:55-06:00 opnsense kea-dhcp4 19415 - [meta sequenceId="139"] INFO [kea-dhcp4.leases.0x249f7e216d00] DHCP4\_LEASE\_OFFER [hwtype=1 56:05:4f:03:93:29], cid=[no info], tid=0x7ec9ee1b: lease 192.168.30.100 will be offered After researching this on the internet, I came across a post of others having this issue which led me to a the following post from someone on the GL.iNet staff that posted "a firmware which use open source WiFi driver". > [@Beryl AX at hotel / repeater mode not working](https://forum.gl-inet.com/t/beryl-ax-at-hotel-repeater-mode-not-working/37999/10): > > I have a firmware which use open source WiFi driver. If you want to have a try pls download and install using this link. Using that firmware ([gl-mt3000-4.6.0-r2-2.1-13.20.tar](https://www.dropbox.com/scl/fi/s8yg9zve96tc8hhixkh11/gl-mt3000-4.6.0-r2-2.1-13.20.tar?rlkey=3flvdvwa1hpaqp7gwt3tdmzia&dl=0)), my Beryl AX functions perfectly and ALWAYS gets an IP address from the DHCP server! I have tried every single stable 4.6.x version firmware from the GL.iNet website ([GL.iNet download center](https://dl.gl-inet.com/router/mt3000/stable)) and all of them exhibit the same behavior where the router never obtains an IP address from the DHCP server. I have also tried the beta 4.7 firmware and that does not work either. Looking at the DHCP server logs, it just scrolls constantly trying to send the Beryl AX an IP address. The firmware with the open source WiFi driver that was posted above is the ONLY firmware that I have found that will reliably work. In all cases, I flash the firmware and do not keep any settings and just reconfigure the router from scratch. Not sure where else to go from this point. The router does work with that firmware with the open source wifi drivers, but I also don't want to be stuck not being able to upgrade the firmware from the latest offering from GL.iNet. I emailed the above to support a couple of days ago, but haven't heard anything back yet. Hence, I'm posting here for advice. Thanks! ---
**Author:** ![buntspext](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/b/3ec8ea/32.png) [@buntspext](https://forum.gl-inet.com/u/buntspext)\ **Post date:** [November 20, 2024, 7:19pm UTC](https://forum.gl-inet.com/t/problem-obtaining-ip-address-via-dhcp-beryl-ax/50743/2 "2024-11-20T19:19:00Z")
I've been on a ship last week with my Beryl with this firmware: [https://dl.gl-inet.com/release/router/rc/mt3000-open/4.6.6-op24](https://dl.gl-inet.com/release/router/rc/mt3000-open/4.6.6-op24) I had no problems on the ship. _ **Don't keep settings, start from scratch!** _ ---
**Author:** ![Drinyth](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/d/ed655f/32.png) [@Drinyth](https://forum.gl-inet.com/u/Drinyth)\ **Post date:** [November 20, 2024, 7:47pm UTC](https://forum.gl-inet.com/t/problem-obtaining-ip-address-via-dhcp-beryl-ax/50743/3 "2024-11-20T19:47:08Z")
Interesting. I did try that version as well, but had a problem where the wireless radio said it was doing some kind of scan and to wait (I should have taken better notes as to exactly what the message was). I waited 5-10 minutes and it never cleared, so I gave up and flashed back to the "stable" versions. Since you reported success, I just flashed it again and it appears to be working. I see in its release notes it mentions: - Fixed the issue where the device could not obtain an IP address after being set up as a repeater. So hopefully the DHCP issue isn't present in this version? I will continue to test this version and if it appears good over the next few days, I'll roll with this on my trip. Thanks for the reply and feedback! ---
**Author:** ![alzhao](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@alzhao](https://forum.gl-inet.com/u/alzhao)\ **Post date:** [November 21, 2024, 8:29am UTC](https://forum.gl-inet.com/t/problem-obtaining-ip-address-via-dhcp-beryl-ax/50743/4 "2024-11-21T08:29:39Z")
Yes the op24 firmware fixed the issue. ---
**Author:** ![buntspext](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/b/3ec8ea/32.png) [@buntspext](https://forum.gl-inet.com/u/buntspext)\ **Post date:** [November 21, 2024, 8:33am UTC](https://forum.gl-inet.com/t/problem-obtaining-ip-address-via-dhcp-beryl-ax/50743/5 "2024-11-21T08:33:26Z")
> [@Drinyth](#): > > So hopefully the DHCP issue isn't present in this version? I will continue to test this version and if it appears good over the next few days, I'll roll with this on my trip. Thanks for the reply and feedback! I never saw the "getting...."-Problem again after switching to op24 firmware. ---
**Author:** ![buntspext](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/b/3ec8ea/32.png) [@buntspext](https://forum.gl-inet.com/u/buntspext)\ **Post date:** [November 21, 2024, 8:34am UTC](https://forum.gl-inet.com/t/problem-obtaining-ip-address-via-dhcp-beryl-ax/50743/6 "2024-11-21T08:34:11Z")
> [@alzhao](#): > > Yes the op24 firmware fixed the issue. btw: Is there a chance for op 4 4.7.x firmware? ---
**Author:** ![alzhao](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@alzhao](https://forum.gl-inet.com/u/alzhao)\ **Post date:** [November 21, 2024, 8:39am UTC](https://forum.gl-inet.com/t/problem-obtaining-ip-address-via-dhcp-beryl-ax/50743/7 "2024-11-21T08:39:18Z")
I think so. But don't have a schedule. ---
**Author:** ![Drinyth](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/d/ed655f/32.png) [@Drinyth](https://forum.gl-inet.com/u/Drinyth)\ **Post date:** [November 21, 2024, 2:08pm UTC](https://forum.gl-inet.com/t/problem-obtaining-ip-address-via-dhcp-beryl-ax/50743/8 "2024-11-21T14:08:08Z")
The op24 firmware does appear to be working. When I tried it the first time, I couldn't get the router to connect to my wifi network for whatever reason. It popped up with a message that it was doing a DFS scan and to wait until it was finished, but it never got past that (or perhaps I got impatient). In any case, all appears to be working as expected now. Hopefully this DHCP fix makes it into the next version(s) of the stable and beta branches. Thanks to everyone that responded! ---
**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\ **Post date:** [July 3, 2025, 7:17am UTC](https://forum.gl-inet.com/t/problem-obtaining-ip-address-via-dhcp-beryl-ax/50743/9 "2025-07-03T07:17:18Z")