Skip to main content
Question

Troubleshooting with G54 Bridge Mode

J
The Many
Forum|alt.badge.img

Hello, I need some help with my G54 modem.

Network: My G54 will act as my bridge, my UDM Pro will handle assigning IP addresses to devices. I will be setting up VLANs on a switch and I’ll be using mesh nodes for AP (replacing repeaters.)

Issue: When I enable Bridge Mode on my G54 and restart it, my connected Router does not recieve a WAN IP, only a LAN IP.  When Bridge Mode is disabled, I have both on my UDM Pro router. I have been factory restting my G54 to recieve internet access/connection when this fails.

When I connect my laptop to G54 (in bridge mode) my laptop is assigned a 169. IP but when I connect to the Router (while G54 is in bridge mode I get a 192. IP, but I do not gain internet access.)

Troubleshooting attempts: 

  1. I tried cloning the MAC address assigned to my laptop, it recieved from the modem, to my UDM Pro’s WAN1. (in the app.) It was unsuccessful. 
  2. I tried to manually push a working IP address. Awful attempt. Unsuccessful.
  3. I called my ISP and asked them to enable Bridge mode. 7 different attempts, each rep told me they had enabled it. It was not enabled. I then asked if the ISP locks the MAC address of the first device connected to the network, thier response was, “no.”
  4. I tried enabling bridge mode, and giving a one hour grace period to the ‘restarting’  of each device. No difference. Unsuccessful

So, I am asking for help. I need my G54 to have bridge mode enabled, but to have the ability to provide my router with a WAN IP.

Note: Ethernet cords being used are Cat6a. I am connecting the 10G port from the G54 to the WAN port (9) on the UDM. 

In advance: I truly appreciate the help, Thank you kindly. 

 

2 replies

S
Wi-Fi Warriors
Forum|alt.badge.img+42

Please try the following steps:

  1. Unplug the coaxial cable from the G54, and then connect only one Ethernet port from the gateway to your computer. It doesn't matter which port you use, but please ensure only one Ethernet connection is active.

  2. After removing the coaxial cable, restart the modem. The LED lights will start blinking, and they will continue blinking until the coaxial cable is reconnected.

  3. Once that’s done, please log in to the web interface (GUI) and enable bridge mode.

  4. After enabling bridge mode, wait for at least 5 minutes. Then, turn off the G54, and while it is off, remove the Ethernet cable from your computer and plug it into the WAN port of your UDM Pro.

  5. Turn on the G54 and reconnect the coaxial cable. Wait for the G54 LED to turn solid blue.

  6. Now, turn on the UDM Pro and allow it to fully boot up. Once it’s ready, check if the UDM Pro receives a WAN IP address.

SURFboard Community Moderator Team
J
1 person likes this
  • J
    JesSvl
J
The Many
Forum|alt.badge.img
  • JesSvlThe Many
  • Author
  • The Many
  • 1 reply
  • March 17, 2025

Update: Issue Solved.

It looked like a DHCP issue, because my UDM was being issued a LAN IP, but not a WAN IP. I did follow your advice. Here’s what I did differently afterwards. 

I enabled bridge mode from the Surfboard app. Then I unplugged, waited 20 minutes, plugged back in, waited to stabilize. As that was happening, I went into the UDM pro app, DHCP settings, and found my issue. 

The issue: My UDM Pro comes with factory settings. One of those settings is, ‘Rogue DHCP server detection,’ being enabled. I disabled it, restarted my UDM, and BAM!!! Problem solved.

My G54 had bridge mode enabled, and my ISP issued my UDM Pro a WAN IP and LAN IP. I could connect to the internet when I connected via ethernet to my router, not my modem. 

I then set up my AP, (which also had to be in brdige mode,) and now I have excellent internet connection throughout the area without having to connect via Ethernet. 

Thank you for the help and support! 

I truly appreciate it. 

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings