Problem Obtaining IP Address via DHCP - Beryl AX

Technical Support for Routers VPN, DNS, Leaks
1

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".

Using that firmware (gl-mt3000-4.6.0-r2-2.1-13.20.tar), 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) 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!

2

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

I had no problems on the ship.

Don't keep settings, start from scratch!

1 Like
3

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!

4

Yes the op24 firmware fixed the issue.

1 Like
5

I never saw the "getting...."-Problem again after switching to op24 firmware.

6

btw: Is there a chance for op 4 4.7.x firmware?

7

I think so. But don't have a schedule.

8

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!

1 Like