RT-BE88U - Some options not showing in LAN\Switch Control

[VladDBA]

I've been using an RT-BE88U for the past 22 days without any issues, this week I've configured it to use GPON SFP stick so I won't have to use my ISP's ONT, everything is working as expected.
But looking through clips of how other people have set this up (one example being in another post here), I've noticed that they have a lot more options in the LAN\Switch Control menu, especially options that pertain to SFP.
I only have one.

Looking in Element Inspector (F12) shows that there are a bunch of option entries that are set to not display.

If I delete the

display:none

from the style option of each table row tag, then the rest of the options show up, although the "GPON module's IP address" option is still not there and I'm guessing Asus might have a valid reason for hiding the options.

In case it's relevant, the router is operating in single WAN mode.

Has anyone encountered this too, especially on RT-BE88U?

Later Edit: looking through the decoded config file, the only option from that section that I can find is Jumbo Frame.
At this point I'm suspecting that the reason why the rest of the options aren't displayed in the GUI is because they have yet to be implemented at the OS level.

 

[RMerlin]

The same page is used for every single router models. The page will adjust what to show at load time based on the specific model you have. If the options don't show, then it's because that router (or the currently running mode) don't support them, so they are hidden.

 

[VladDBA]

The same page is used for every single router models. The page will adjust what to show at load time based on the specific model you have. If the options don't show, then it's because that router (or the currently running mode) don't support them, so they are hidden.

Thank you for the input.

I get that, but I thought that actively using the SFP+ port would at least make the SFP+ and GPON related options avaliable.
I've tried switching to dual WAN mode, like the one in the example video, but it didn't change anything in the Switch Control menu.
I'll poke some more at it, maybe I'm missing something.

The reason why I'm looking into this is that I can no longer access the GPON's admin interface via its usual IP (192.168.1.10 which is in the same subnet that my whole LAN is using), and I thought it might have something to do with the Switch Control menu.

 

[ColinTaylor]

192.168.1.10 which is in the same subnet that my whole LAN is using

That won't be possible then. You would have to change your LAN subnet to be something other than 192.168.1.x.

 

[VladDBA]

That won't be possible then. You would have to change your LAN subnet to be something other than 192.168.1.x.

This might sound silly: why?
When I've set it up initially I accessed it via 192.168.1.10, it actually showed up in the router DHCP address reservation. Although I'm suspecting this might have been a fluke.
I'm not trying to contradict, I'm just trying to understand why.

 

[ColinTaylor]

I might be misunderstanding what you're describing. But it sounds like the GPON you're trying to access (at 192.168.1.10) is connected to your router's WAN port, which is the SFP+ port. So if your LAN is 192.168.1.x then it will assume 192.168.1.10 is a device connected to your LAN, not the WAN interface.

 

[VladDBA]

I might be misunderstanding what you're describing. But it sounds like the GPON you're trying to access (at 192.168.1.10) is connected to your router's WAN port, which is the SFP+ port. So if your LAN is 192.168.1.x then it will assume 192.168.1.10 is a device connected to your LAN, not the WAN interface.

No, you understood it correctly.
Before doing the initial setup of the GPON (setting its manufacturer ID, model, serial number and MAC to match the one from my ISPs ONT) I just connected the GPON to the router's SFP+ port and two things happened:
1. My AV popped up a warning about a potential ARP cache poisoning attack - this was the GPON broadcasting the 192.168.1.10 IP via ARP
2. The GPON's MAC and IP showed up in the router's DHCP address reservation menu, in that drop down list where you select connected clients to assign/set static IPs to them - I just used that to confirm the IP, not to set it as static
After 1 & 2 happened I just connected to the GPON via SSH and made the changes.
While making the config changes I have not touched the following two configuration options (because I had no reason to):
- ipaddr=192.168.1.10
- gatewayip=192.168.2.0

After I've made and committed the config changes I rebooted the GPON and was unable to connect to it since, but the internet connection works flawlessly.
At this point I'm suspecting that point 2 was a complete fluke and the reason I was able to connect to the GPON in the first place was because I somehow got lucky with ARP and just didn't go through the router somehow.

Later Edit:
I've tried setting the router to a different subnet (192.168.3.x to be specific), but I still haven't been able to connect to the GPON stick.
I'll most likely have to swap it out with my backup router so that I can mess with it more without impacting other clients in my LAN.

 

[VladDBA]

In case this might help someone facing the same issue:
I've tried again by changing the router's IP to something in a different subnet (192.168.3.1).
Then I've switched the LAN cable on my PC to my second NIC which I've set to use the 192.168.1.11 IP and 192.168.1.10 (the GPON's IP) as the gateway.
At this point I was still unable to connect to it via SSH.
What made the connection possible was changing the WAN source on the router to the 10GB WAN port instead of the SFP+ port (this was the same WAN setup I had when I was initially able to connect to the GPON). Once I've done that I was able to connect to the GPON SFP stick via SSH.
Once connected I've changed the GPON's management IP to something that doesn't clash with my router's original subnet, rebooted the GPON, changed back my router's IP and then tested the SSH connection again using the GPON's new IP - this worked again without any issues.
After I switched the WAN source back to the SFP+ port I could no longer connect to the GPON.

TL;DR: in order to connect via SSH to this model of GPON, the SFP+ port must not be the set as the WAN source.