TOPEX Bytton (HSPA+ / LTE)
ByttonLTE(full)_genericUsermanual_sw306FAS_revN.1.docx
Page: 72 / 290
collisions:0 txqueuelen:0
RX bytes:22825 (22.2 KiB) TX bytes:11603 (11.3 KiB)
lan Link encap:Ethernet HWaddr 00:50:C2:F5:23:2A
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:204 errors:0 dropped:0 overruns:0 frame:0
TX packets:63 errors:1 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:39576 (38.6 KiB) TX bytes:11741 (11.4 KiB)
Base address:0x2200
lan0 Link encap:Ethernet HWaddr 00:50:C2:F5:23:27
inet addr:192.168.148.148 Bcast:192.168.148.151 Mask:255.255.255.252
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:46 (46.0 B)
Base address:0x2000
The second WAN IP that you have defined shows up and also in the Routing Table:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.148.148 0.0.0.0 255.255.255.252 U 0 0 0 lan0
172.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wan
0.0.0.0 192.168.1.8 0.0.0.0 UG 0 0 0 wan
Access on WAN side over alternate IP – example;
Suppose you set up “
192.168.148.148
” as alternate IP address over the WAN interface:
Following a
Commit
command and restart, the Bytton LTE equipment will be now accessible on the WAN
side, through its port labeled “WAN0/LAN”, at the address for second WAN that was set previously: