Static Route for WAN2 for 192.168.11.0

Routers
2

I’ve gone ahead and sent this to you directly via your support ticket, but for visibility I’ll also share it here.

I have an EN–XGSFPP–0MAC–V2 XGS-PON module (WAS-110) which is accessible at 192.168.11.1. We need to modify the configuration via shell (or ultimately a post-cfg.sh script), but there’s no need to use a static route. Instead, we can assign the router interface an IP in that management subnet and add it to the lan zone. This effectively connects the ONT’s network directly to the LAN, allowing any LAN device to access it.

Important: Do not create a VLAN that resides in the same address space, to avoid conflicts.

Below is what you would need to add in the /cfg/post-cfg.sh script file assuming that your XGS-PON module is connected to W2 (eth4):

#!/bin/sh

# post-cfg.sh 
# Allows access to ONT management

# 1) Tear down any old mgmt subif
uci delete network.ont_mgmt

# 2) Create a plain-eth4 alias for ONT mgmt
uci set network.ont_mgmt='interface'
uci set network.ont_mgmt.ifname='eth4'
uci set network.ont_mgmt.proto='static'
uci set network.ont_mgmt.ipaddr='192.168.11.2'
uci set network.ont_mgmt.netmask='255.255.255.0'

# 3) Add it into the LAN firewall zone
uci add_list firewall.@zone[0].network='ont_mgmt'

# 4) Commit your changes
uci commit network
uci commit firewall

# 5) Bring the interface up and reload firewall
ifup ont_mgmt
/etc/init.d/firewall reload

I wrote another guide HERE which touches on pasting the content for post-cfg.sh, but you can also direclty transfer the file via scp. If doing the latter, it still needs permissions updated after, etc. Also, if helpful, we have a help centre article HERE on adding SSH keys, which would be needed if going the scp transfer route.

2 Likes