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!

A

andresmorago

Senior Member
Hello

I currently have this setup

ISP --- ONT --- Asus router

ONT is configured as a plain bridge and does no VLAN tagging
lan ip 192.168.100.1
no dhcp server

Asus router (AC68u @ 386.3_2)
lan 10.0.4.1
dhcp server
wan ip is acquired via pppoe and vlan 100

Im trying to access the ONT from the Asus router wifi but havent been able to achieve it. @john9527 posted a way to do it by adding some lines to the nat and wan start scripts. ive done so and i can see the new route being added.

1630858234667.png


But. When trying to ping 192.168.100.1, it responds but it wont load the web gui:

Code: 
ping 192.168.100.1

Pinging 192.168.100.1 with 32 bytes of data:
Reply from 192.168.100.1: bytes=32 time=2ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=2ms TTL=64
Reply from 192.168.100.1: bytes=32 time=33ms TTL=64

Ping statistics for 192.168.100.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 33ms, Average = 9ms

tracert 192.168.100.1

Tracing route to 192.168.100.1 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.100.1

Trace complete.

Another weird thing is that when performing an ip scan on that particular ip, a ASUS mac address (88D7F6) shows up
1630858425022.png
 
Last edited:
@ColinTaylor provided help to another person with the same issue. The conversation is here;

www.snbforums.com

Access to DSL modem

I have a DSL modem (Thompson ST516) in bridge mode, and router (Asus RT-N66U) does the PPPoE login. Would like to access modem webpage for line statistics, etc....however no connection. Found an instruction on DD-WRT how to access modem before the router...
www.snbforums.com www.snbforums.com

Hope this helps.
 
If the ONT is bridged, there is nothing to 'access'.
 
Yep, true enough. I missed that small, but important point.
 
Actually, looking at the link I posted, the fella Colin was helping had a bridged device. I would follow the instructions in the link and see what happens. Report back on what you find.
 
A DSL modem isn't an ONT. :)

But, I may be wrong about being able to access one (an ONT), too.
 
I can access mine which is in bridge mode.....but i think the isp did their bridge mode differently as they have 2 services running off the 2 in 1 tin can still.
i can access the tin can if i have VPN + DCHP acitvated in the WAN settings down the bottom.

Im with Movistar Espana
 
L&LD said:
If the ONT is bridged, there is nothing to 'access'.
Click to expand...
I would like to see power levels from the ONT web gui. If ONT is configured as bridge, would the web gui be entirely disabled? If i connect straight my pc to the ONT, im able to access the web gui if i have a static ip address assigned.

my past internet service had a cable modem also in bridge mode and i was able to access its ip and see power levels

Jeffrey Young said:
@ColinTaylor provided help to another person with the same issue. The conversation is here;

www.snbforums.com

Access to DSL modem

I have a DSL modem (Thompson ST516) in bridge mode, and router (Asus RT-N66U) does the PPPoE login. Would like to access modem webpage for line statistics, etc....however no connection. Found an instruction on DD-WRT how to access modem before the router...
www.snbforums.com www.snbforums.com

Hope this helps.
Click to expand...
thanks. will try tonight and report back
 
Last edited:
@andresmorago Can you post the complete output of ifconfig -a please?

I'm also confused why you seem to have a network of 10.0.0.0/8 that overlaps 3 other networks.
 
10.0.0.0/8 has always been there. even before i configured the vpn server and client

I have both VPN client and server running on my router.
Server runs on 10.0.10.1/255.255.255.0
Client has IP address of 10.0.1.2 and has a route configured so i can access external VPN server (which belongs to network 10.0.0.0/255.255.255.0 on its side)

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
10.0.4.0        0.0.0.0         255.255.255.0   U         0 0          0 br0
10.0.1.0        0.0.0.0         255.255.255.0   U         0 0          0 tun11
10.0.10.0       0.0.0.0         255.255.255.0   U         0 0          0 tun21
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


Code: 
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:32641 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29233 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10870446 (10.3 MiB)  TX bytes:17032858 (16.2 MiB)

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:48625 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44461 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:26662494 (25.4 MiB)  TX bytes:14381778 (13.7 MiB)
          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:2254 errors:0 dropped:0 overruns:0 frame:21407
          TX packets:2962 errors:4 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:899099 (878.0 KiB)  TX bytes:539805 (527.1 KiB)
          Interrupt:163

eth2      Link encap:Ethernet  HWaddr 88:D7:F6:88:53:5C
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:8732 errors:0 dropped:0 overruns:0 frame:28283
          TX packets:10266 errors:2 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2174839 (2.0 MiB)  TX bytes:14764371 (14.0 MiB)
          Interrupt:169

ifb0      Link encap:Ethernet  HWaddr C6:7B:84:97:E4:CB
          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 26:4F:45:B2:C8:54
          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:6450 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6450 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1528569 (1.4 MiB)  TX bytes:1528569 (1.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

ppp0      Link encap:Point-to-Point Protocol
          inet addr:190.96.184.17  P-t-P:191.110.192.1  Mask:255.255.255.255
          UP POINTOPOINT RUNNING MULTICAST  MTU:1480  Metric:1
          RX packets:30393 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26891 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:17395156 (16.5 MiB)  TX bytes:9771832 (9.3 MiB)

tun11     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:10.0.1.2  P-t-P:10.0.1.2  Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:370 errors:0 dropped:0 overruns:0 frame:0
          TX packets:364 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:132164 (129.0 KiB)  TX bytes:68734 (67.1 KiB)

tun21     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:10.0.10.1  P-t-P:10.0.10.1  Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP 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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vlan1     Link encap:Ethernet  HWaddr 88:D7:F6:88:53:58
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:18126 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17547 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8019045 (7.6 MiB)  TX bytes:3910126 (3.7 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:30416 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26914 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:17761051 (16.9 MiB)  TX bytes:10471652 (9.9 MiB)


as a side note, i have the other router (LAN 10.0.0.1/24) on a different site and it also has that 10.0.0.0/8 network. interestingly, one thing that both routers share is pixelsrv. would that be?
1631136248325.png
 

Attachments

  • 1631136224985.png
    1631136224985.png
    11.7 KB · Views: 211
Last edited:
In post #1 you created another interface to access 192.168.100.0/24. That isn't there anymore. Please post the commands you used to create that.
 
ColinTaylor said:
In post #1 you created another interface to access 192.168.100.0/24. That isn't there anymore. Please post the commands you used to create that.
Click to expand...
Code: 
ifconfig `nvram get wan0_ifname`:0 192.168.100.1 netmask 255.255.255.0
i believe that was wrong and canceled it because 192.168.100.1 is already used by the ONT (lan side)
 
Yes that is wrong. Try entering this command and see if you can now access the ONT:

Code: 
ifconfig $(nvram get wan0_ifname):0 192.168.100.2 netmask 255.255.255.0

EDIT: Unrelated to your problem, but IIRC you can set "Enable VPN + DHCP Connection" to No under "WAN > Internet Connection > Special Requirement from ISP" to get rid of that superfluous vlan100 interface.
 
Last edited:
ColinTaylor said:
Yes that is wrong. Try entering this command and see if you can now access the ONT:

Code: 
ifconfig $(nvram get wan0_ifname):0 192.168.100.2 netmask 255.255.255.0

EDIT: Unrelated to your problem, but IIRC you can set "Enable VPN + DHCP Connection" to No under "WAN > Internet Connection > Special Requirement from ISP" to get rid of that superfluous vlan100 interface.
Click to expand...
hello @ColinTaylor, no luck so far. I have entered that command and the vlan interface indeed gets an ip address (192.168.100.2), but yet still, im not able to ping the ONT (192.168.100.1) from the router.

Code: 
andresmorago@bga01:/tmp/home/root# ifconfig $(nvram get wan0_ifname):0 192.168.100.2 netmask 255.255.255.0
andresmorago@bga01:/tmp/home/root#
andresmorago@bga01:/tmp/home/root# ping 192.168.100.2
PING 192.168.100.2 (192.168.100.2): 56 data bytes
64 bytes from 192.168.100.2: seq=0 ttl=64 time=0.453 ms
64 bytes from 192.168.100.2: seq=1 ttl=64 time=0.278 ms
--- 192.168.100.2 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.278/0.365/0.453 ms

andresmorago@bga01:/tmp/home/root# ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1): 56 data bytes
--- 192.168.100.1 ping statistics ---
10 packets transmitted, 0 packets received, 100% packet loss

Code: 
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:62573 errors:0 dropped:0 overruns:0 frame:0
          TX packets:256192 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9262004 (8.8 MiB)  TX bytes:357719395 (341.1 MiB)

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:265474 errors:0 dropped:0 overruns:0 frame:0
          TX packets:71940 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:365417396 (348.4 MiB)  TX bytes:23662270 (22.5 MiB)
          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:3844 errors:0 dropped:0 overruns:0 frame:32094
          TX packets:6063 errors:10 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2661362 (2.5 MiB)  TX bytes:1122997 (1.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:56100 errors:0 dropped:0 overruns:0 frame:57355
          TX packets:150353 errors:3 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8138141 (7.7 MiB)  TX bytes:353371706 (337.0 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:12441 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12441 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1762008 (1.6 MiB)  TX bytes:1762008 (1.6 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:190.66.51.105  P-t-P:191.110.192.1  Mask:255.255.255.255
          UP POINTOPOINT RUNNING MULTICAST  MTU:1480  Metric:1
          RX packets:251272 errors:0 dropped:0 overruns:0 frame:0
          TX packets:52435 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:351221050 (334.9 MiB)  TX bytes:7938996 (7.5 MiB)

tun11     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:10.0.1.2  P-t-P:10.0.1.2  Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:3325 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2314 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3639627 (3.4 MiB)  TX bytes:208680 (203.7 KiB)

tun21     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:10.0.10.1  P-t-P:10.0.10.1  Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP 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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vlan1     Link encap:Ethernet  HWaddr 88:D7:F6:88:53:58
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:14102 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19460 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6395239 (6.0 MiB)  TX bytes:14358047 (13.6 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:251288 errors:0 dropped:0 overruns:0 frame:0
          TX packets:52480 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:354237157 (337.8 MiB)  TX bytes:9304223 (8.8 MiB)

vlan100: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

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 vlan100
10.0.4.0        0.0.0.0         255.255.255.0   U         0 0          0 br0
10.0.1.0        0.0.0.0         255.255.255.0   U         0 0          0 tun11
10.0.10.0       0.0.0.0         255.255.255.0   U         0 0          0 tun21
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#

I have disconnected the router wan from the ont and connected my pc instead. with a fixed ip on my pc, im able to access the ont:

1631151915192.png

1631151895344.png
 
OK that didn't work correctly. It's created the interface on vlan100 instead of ppp0. I'm not that familiar with pppoe connections so I'm obviously using the wrong nvram variable.

So rather than be clever let's just hard code it for now.

So get rid of the incorrect interface:
Code: 
ifconfig vlan100:0 down
and create the correct interface:
Code: 
ifconfig ppp0:0 192.168.100.2 netmask 255.255.255.0
 
Last edited:
ColinTaylor said:
OK that didn't work correctly. It's created the interface on vlan100 instead of ppp0. I'm not that familiar with pppoe connections so I'm obviously using the wrong nvram variable.

So rather than be clever let's just hard code it for now.

So get rid of the incorrect interface:
Code: 
ifconfig vlan100:0 down
and create the correct interface:
Code: 
ifconfig ppp0:0 192.168.100.2 netmask 255.255.255.0
Click to expand...
still no go :(
could it be related to the fact the router is doing a vlan tagging for the pppoe to work (VLAN 100)?
from my computer, ONT web GUI is not accessible if i set vlan 100 on ethernet adapter (pppoe will work though)


Code: 
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:339193 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1849616 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:39925921 (38.0 MiB)  TX bytes:2640056686 (2.4 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:2161773 errors:0 dropped:0 overruns:0 frame:0
          TX packets:761565 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2970351698 (2.7 GiB)  TX bytes:528499584 (504.0 MiB)
          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:10283 errors:0 dropped:0 overruns:0 frame:201323
          TX packets:18690 errors:11 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4731365 (4.5 MiB)  TX bytes:3318165 (3.1 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:269146 errors:0 dropped:0 overruns:0 frame:220436
          TX packets:963106 errors:4 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:31305395 (29.8 MiB)  TX bytes:2438084396 (2.2 GiB)
          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:29936 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29936 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5939958 (5.6 MiB)  TX bytes:5939958 (5.6 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:1216703 errors:0 dropped:0 overruns:0 frame:0
          TX packets:186478 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:1735875626 (1.6 GiB)  TX bytes:17964437 (17.1 MiB)

ppp0:0    Link encap:Point-to-Point Protocol
          inet addr:192.168.100.2  P-t-P:192.168.100.2  Mask:255.255.255.0
          UP POINTOPOINT RUNNING MULTICAST  MTU:1480  Metric:1

tun11     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:10.0.1.3  P-t-P:10.0.1.3  Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:7648 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4685 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7910962 (7.5 MiB)  TX bytes:428894 (418.8 KiB)

tun21     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:10.0.10.1  P-t-P:10.0.10.1  Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP 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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vlan1     Link encap:Ethernet  HWaddr 88:D7:F6:88:53:58
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:137966 errors:0 dropped:0 overruns:0 frame:0
          TX packets:253405 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:61273595 (58.4 MiB)  TX bytes:290833807 (277.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:2023464 errors:0 dropped:0 overruns:0 frame:0
          TX packets:508164 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2870136770 (2.6 GiB)  TX bytes:237669219 (226.6 MiB)



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 ppp0
10.0.4.0        0.0.0.0         255.255.255.0   U         0 0          0 br0
10.0.1.0        0.0.0.0         255.255.255.0   U         0 0          0 tun11
10.0.10.0       0.0.0.0         255.255.255.0   U         0 0          0 tun21
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
^C
--- 192.168.100.1 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

andresmorago@bga01:/tmp/home/root#
 
Last edited:
What IP does the directly connected PC get without a fixed IP set on the PC? Is it a public IP, or a private IP address?

This doesn't look like a truly 'bridged' ONT to me?
 
andresmorago said:
could it be related to the fact the router is doing a vlan tagging for the pppoe to work (VLAN 100)?
from my computer, ONT web GUI is not accessible if i set vlan 100 on ethernet adapter (pppoe will work though)
Click to expand...
I think you are correct. When you did your test in post #14 you were just creating a normal Ethernet connection to the ONT, without using pppoe. So in hindsight trying to use the router's pppoe interface was the wrong way to go.

As I said, I'm not that familiar with pppoe and have no way of testing various configurations here. My first guess would be to trying using eth0:0 instead of ppp0:0
 
Last edited:
ColinTaylor said:
I think you are correct. When you did your test in post #14 you were just creating a normal Ethernet connection to the ONT, without using pppoe. So in hindsight trying to use the router's pppoe interface was the wrong way to go.

As I said, I'm not that familiar with pppoe and have no way of testing various configurations here. My first guess would be to trying using eth0:0 instead of ppp0:0
Click to expand...
that worked! :) but partially. ONT is now pingable from router (10.0.4.1) but not from router's lan (10.0.4.0/24)
next part, how do i make it accessible from LAN computers? Should i create a static route?

L&LD said:
What IP does the directly connected PC get without a fixed IP set on the PC? Is it a public IP, or a private IP address?

This doesn't look like a truly 'bridged' ONT to me?
Click to expand...
as a side note and to add up to @L&LD:
1- ONT when configured in bridge mode wont assign IP's to whatever you connect to the lan port as DHCP is disabled
2- if i connect my pc to the ONT, i need to first assign to the ethernet adapter a VLAN 100 in order to be able to succesfully execute the PPPoE connection. in this case, ONT web gui isnt accesible
3- if i connect my pc to the ONT assign an IP address (lets say 192.168.100.2) and no VLAN, i will be able to access the web gui at 192.168.100.1
 
Last edited:
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
453
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
931
domic
D
V
ip6tables mangle does not do anything
Replies
3
Views
978
dave14305
dave14305
Similar threads
Thread starter Title Forum Replies Date
K Solved "Block internet access" does nothing Asuswrt-Merlin 6
T GT BE98 Pro Guest Network Cannot Disable Intranet Access Asuswrt-Merlin 0
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
E RT AX88U problem with update 3004 388-8-1 and 2: loss of internet access Asuswrt-Merlin 8
R Lost console access Asuswrt-Merlin 4

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!

Staff online

Members online

Total: 675 (members: 30, guests: 645)
Top