Menu
What's new
By:
Filters Better Search

Solved How to access my ONT from router

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

ColinTaylor said:
OK that's progress. Try adding this:
Code: 
iptables -t nat -I POSTROUTING -o eth0:0 -j MASQUERADE
Click to expand...
nothing so far
192.168.100.1 is still pingable from router but not from pc connected to router.

Code: 
C:\Users\andresmorago>tracert -w 100 -d 192.168.100.1

Tracing route to 192.168.100.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  10.0.4.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
 
 
C:\Users\andresmorago>ping 192.168.100.1

Pinging 192.168.100.1 with 32 bytes of data:
Request timed out.
Request timed out.

Ping statistics for 192.168.100.1:
    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
 
Disable the VPN client just in case that is effecting things.

EDIT: Also, try seeing if this has an effect:
Code: 
iptables -t nat -I POSTROUTING -o eth0 -j MASQUERADE
 
Last edited:
ColinTaylor said:
Disable the VPN client just in case that is effecting things.
Click to expand...
nothing :(
i have disabled both vpn server and client.

no access from lan clients.

router side looks ok

Code: 
andresmorago@bga01:/tmp/home/root# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
191.110.192.1   0.0.0.0         255.255.255.255 UH        0 0          0 ppp0
192.168.100.0   0.0.0.0         255.255.255.0   U         0 0          0 eth0
10.0.4.0        0.0.0.0         255.255.255.0   U         0 0          0 br0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 vlan100
10.0.0.0        0.0.0.0         255.0.0.0       U         0 0          0 br0
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 lo
0.0.0.0         191.110.192.1   0.0.0.0         UG        0 0          0 ppp0

andresmorago@bga01:/tmp/home/root# ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1): 56 data bytes
64 bytes from 192.168.100.1: seq=0 ttl=64 time=1.775 ms
64 bytes from 192.168.100.1: seq=1 ttl=64 time=1.461 ms
64 bytes from 192.168.100.1: seq=2 ttl=64 time=1.341 ms
^C
--- 192.168.100.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 1.341/1.525/1.775 ms

andresmorago@bga01:/tmp/home/root# ifconfig -a
br0       Link encap:Ethernet  HWaddr 88:D7:F6:88:53:58
          inet addr:10.0.4.1  Bcast:10.0.4.255  Mask:255.255.255.0
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:1743942 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3893611 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1214977107 (1.1 GiB)  TX bytes:4977065228 (4.6 GiB)

br0:pixelserv-t Link encap:Ethernet  HWaddr 88:D7:F6:88:53:58
          inet addr:10.0.4.2  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1

dpsta     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0      Link encap:Ethernet  HWaddr 88:D7:F6:88:53:58
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4488417 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2336082 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1296045148 (1.2 GiB)  TX bytes:1941617998 (1.8 GiB)
          Interrupt:179 Base address:0x4000

eth0:0    Link encap:Ethernet  HWaddr 88:D7:F6:88:53:58
          inet addr:192.168.100.2  Bcast:192.168.100.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:179 Base address:0x4000

eth1      Link encap:Ethernet  HWaddr 88:D7:F6:88:53:58
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:59072 errors:0 dropped:0 overruns:0 frame:1544954
          TX packets:80280 errors:16 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12170581 (11.6 MiB)  TX bytes:14749352 (14.0 MiB)
          Interrupt:163

eth2      Link encap:Ethernet  HWaddr 88:D7:F6:88:53:5C
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:1353077 errors:0 dropped:0 overruns:0 frame:931022
          TX packets:2131352 errors:702 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1126703476 (1.0 GiB)  TX bytes:464383677 (442.8 MiB)
          Interrupt:169

ifb0      Link encap:Ethernet  HWaddr 4A:4F:E1:0C:4A:93
          BROADCAST NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

ifb1      Link encap:Ethernet  HWaddr 92:13:C0:29:78:49
          BROADCAST NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING MULTICAST  MTU:16436  Metric:1
          RX packets:192427 errors:0 dropped:0 overruns:0 frame:0
          TX packets:192427 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:44803605 (42.7 MiB)  TX bytes:44803605 (42.7 MiB)

lo:0      Link encap:Local Loopback
          inet addr:127.0.1.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING MULTICAST  MTU:16436  Metric:1

ppp0      Link encap:Point-to-Point Protocol
          inet addr:167.0.62.103  P-t-P:191.110.192.1  Mask:255.255.255.255
          UP POINTOPOINT RUNNING MULTICAST  MTU:1480  Metric:1
          RX packets:3408119 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1602339 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:4225479337 (3.9 GiB)  TX bytes:1341809848 (1.2 GiB)

vlan1     Link encap:Ethernet  HWaddr 88:D7:F6:88:53:58
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:269827 errors:0 dropped:0 overruns:0 frame:0
          TX packets:411352 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:123881728 (118.1 MiB)  TX bytes:343265281 (327.3 MiB)

vlan100   Link encap:Ethernet  HWaddr 88:D7:F6:88:53:58
          inet addr:169.254.188.203  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4215476 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1924638 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5386065025 (5.0 GiB)  TX bytes:1598348282 (1.4 GiB)

andresmorago@bga01:/tmp/home/root#
 
@ColinTaylor
This last command you mentioned did it! :) Im now able to access ONT 192.168.100.1

so i guess we dont need eth0:0 but eth0
Code: 
iptables -t nat -I POSTROUTING -o eth0 -j MASQUERADE


VPN client and server are stable also
 
That's good news. I had also been thinking that you probably don't need to create an eth0:0 interface at all. But rather just reuse eth0 by assigning an IP address to it:

Code: 
ifconfig eth0 192.168.100.2 netmask 255.255.255.0

Whether one way or the other is "better" is probably a matter of opinion.
 
ColinTaylor said:
That's good news. I had also been thinking that you probably don't need to create an eth0:0 interface at all. But rather just reuse eth0 by assigning an IP address to it:

Code: 
ifconfig eth0 192.168.100.2 netmask 255.255.255.0

Whether one way or the other is "better" is probably a matter of opinion.
Click to expand...
great idea. will try that as well

so in conclusion:
Code: 
ifconfig eth0 192.168.100.2 netmask 255.255.255.0
iptables -t nat -I POSTROUTING -o eth0 -j MASQUERADE

thanks to all for the help!
 
Last edited:
Hi! What an intereseting thread!
I also have a ONT bridged to my 87U and its a real pit* to unplug/plug my pc from router to ONT every time I need access to it.
It would be awesome if I could access it directly from my LAN.
I've tried to understand what was written here to addapt it to my particular case but its beyond my humble understanding.

Please, could you point me to the correct lines in order to make it work for my setup?
I paste here the outputs that were asked to OP:
Code: 
ASUSWRT-Merlin RT-AC87U 384.13_10 Sun Jun 28 17:57:25 UTC 2020
@ASUS_RT-AC87U:/tmp/home/root# nvram get wan0_ifname
vlan2
Code: 
@ASUS_RT-AC87U:/tmp/home/root# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
181.117.205.1   0.0.0.0         255.255.255.255 UH        0 0          0 vlan2
169.254.39.0    0.0.0.0         255.255.255.0   U         0 0          0 br0
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0 br0
181.117.205.0   0.0.0.0         255.255.255.0   U         0 0          0 vlan2
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 lo
0.0.0.0         181.117.205.1   0.0.0.0         UG        0 0          0 vlan2
Code: 
@ASUS_RT-AC87U:/tmp/home/root# ifconfig -a
aux0      Link encap:Ethernet  HWaddr D0:17:C2:B3:39:C8
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:209520 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:16667465 (15.8 MiB)  TX bytes:0 (0.0 B)
          Interrupt:180 Base address:0x5000

br0       Link encap:Ethernet  HWaddr D0:17:C2:B3:39:C8
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:5204244 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16209066 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:13063775736 (12.1 GiB)  TX bytes:19306288783 (17.9 GiB)

br0:0     Link encap:Ethernet  HWaddr D0:17:C2:B3:39:C8
          inet addr:169.254.39.99  Bcast:169.254.39.255  Mask:255.255.255.0
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1

eth0      Link encap:Ethernet  HWaddr D0:17:C2:B3:39:C8
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:25778224 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21652117 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:162776873 (155.2 MiB)  TX bytes:24925956 (23.7 MiB)
          Interrupt:181 Base address:0x6000

eth1      Link encap:Ethernet  HWaddr D0:17:C2:B3:39:C8
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:159676 errors:0 dropped:0 overruns:0 frame:453684
          TX packets:2614365 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:22203576 (21.1 MiB)  TX bytes:722160409 (688.7 MiB)
          Interrupt:163

ifb0      Link encap:Ethernet  HWaddr BA:B7:84:8F:DB:03
          BROADCAST NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

ifb1      Link encap:Ethernet  HWaddr 66:BF:61:CE:39:33
          BROADCAST NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING MULTICAST  MTU:16436  Metric:1
          RX packets:370351 errors:0 dropped:0 overruns:0 frame:0
          TX packets:370351 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:49775759 (47.4 MiB)  TX bytes:49775759 (47.4 MiB)

lo:0      Link encap:Local Loopback
          inet addr:127.0.1.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING MULTICAST  MTU:16436  Metric:1

vlan1     Link encap:Ethernet  HWaddr D0:17:C2:B3:39:C8
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:14359652 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17606171 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:13594698756 (12.6 GiB)  TX bytes:20975511930 (19.5 GiB)

vlan2     Link encap:Ethernet  HWaddr D0:17:C2:B3:39:C8
          inet addr:181.117.205.20  Bcast:181.117.205.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11628088 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4211943 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11825618676 (11.0 GiB)  TX bytes:435273373 (415.1 MiB)

wl0.1     Link encap:Ethernet  HWaddr D0:17:C2:B3:39:C9
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:74810 errors:0 dropped:0 overruns:0 frame:453684
          TX packets:1895548 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:14608225 (13.9 MiB)  TX bytes:758479293 (723.3 MiB)

THANKS in advance for your help!!!
 
To start with, what is the address of your bride device.

I am not familiar with the 87U, but I would hazard from your posting that you will need to assign an address to eth0 that is in the same subnet as your bridge device. Reference post 27

Are you using ppoe or something similar for your connection?
 
FOA thanks for your reply Jeffrey!
What is the address of your bride device.
Click to expand...
Where can i get that info?
Are you using ppoe or something similar for your connection?
Click to expand...
I'm using "Automatic IP" under Wan Connection type (Enable Wan and Enable Nat both to yes)
 
When you connect to your ONT device, what address do you use? Or what name? Assuming you are using a web browser
 
The master beat me to it. Sorry for the double post.
 
Thanks @ColinTaylor and @Jeffrey Young , and excuse my fo*lness...

The address I use when I'm connected directly to ONT is 192.168.100.1

Thanks!
 
And to make sure of no subnet conflicts, what is your address of your 87U?
 
It's 192.168.0.1 (subnet 255.255.255.0)
 
Ok, using the "in conclusion" part of Colin's post in post 27 above, those two commands should also work for you as well.

SSH into your 87U and type each one in. Then see if can ping the ONT from the 87U and from a command prompt on your computer.
 
Jeffrey Young said:
Ok, using the "in conclusion" part of Colin's post in post 27 above, those two commands should also work for you as well.
Click to expand...
Using those commands may or may not work. But I wouldn't recommend using them because if he disabled hardware acceleration there would be conflicting IP addresses being assigned to the WAN interface.

As this is not a pppoe setup he should try using the "usual" solution to this problem. It has the advantage that you shouldn't need the iptables rule because that already exists. So it's just:
Code: 
ifconfig $(nvram get wan0_ifname):0 192.168.100.2 netmask 255.255.255.0
 
Thanks to both once again! top notch support and kindness!
Tonight when I get home I'll try Colin's approach to avoid any of the issues he stated (I'm using CTF + FA if it counts).

Just to win some time: if it works I do have to add it to wan-start script to make it permanent, don't I?
And to undone changes just delete that line from script and reboot, right?

Will report back with results!
THANKS!
 
I certainly bow to Colin's wisdom on this one. Colin, by far, goes out of his way to help anybody. I certainly respect his knowledge and willingness to help. I'd listen to him.

If the wan0_ifname value does not work, try the eth0.
 
You must log in or register to reply here.

Similar threads

R
Asus GT-AX11000 is bricked
Replies
12
Views
1K
dcsang
D
M
Solved No ping on WG - BUG?
2
Replies
20
Views
636
Mikii
M
Dathuil
dnsmasq hostname doesn't resolve on OSX/IPad but resolves on Windows/Android
Replies
10
Views
1K
torch
T
D
Solved Windows doesn't resolve Android device hostnames?
Replies
11
Views
1K
domic
D
V
ip6tables mangle does not do anything
Replies
3
Views
1K
dave14305
dave14305
Similar threads
Thread starter Title Forum Replies Date
A ASUSwrt-Merlin connection to modem as Access Point and/or Bridge Asuswrt-Merlin 6
R Disable Intranet access for a LAN port (not the WiFi Guest network)? Asuswrt-Merlin 13
K Solved "Block internet access" does nothing Asuswrt-Merlin 7
T GT BE98 Pro Guest Network Cannot Disable Intranet Access Asuswrt-Merlin 3
E Wireguard can't access devices behind asus router Asuswrt-Merlin 5
R Addition of Block Internet Access Asuswrt-Merlin 5
ali. Access point mode: unable to use AirPlay Asuswrt-Merlin 3
K How to block LAN access for a wired device on ASUS Merlin (Firmware 3004.388.8_2)? Asuswrt-Merlin 12
S OpenVPN LAN access + one external IP Asuswrt-Merlin 3
Preskitt.man Access Router Admin from Chrome Flex OS Asuswrt-Merlin 2

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 743 (members: 23, guests: 720)
Top