vanhh
join:2003-06-24
Sacramento, CA
| reply to vanhh
Re: [General] how to access motorola 2210-02-1002 stats behind a
ok here we go folks. There are few ways to do it.
1)This way will work, but you need a second network card and a switch in between your modem and router (modem ---- switch ---- router ---- PCs.) Modem is in Bridge mode and your router does PPPoE. Give a static ip to your second NID like 192.168.1.xx (something different range from your router), subnet mask 255.255.255.0 and default gateway 192.168.1.254 (your modem IP). Connect this NID to the switch. You don't have to change anything in the router. This is the part I hated it. To get the modem stats, you need to disable the NID connecting to your router and enable the NID connect to the switch. Then type 192.168.1.254 to get the stats. To get back to the internet, then you need to reverse the process disable and enable the NID. This is why I didn't like it.
2) Here is the easy way. You don't need to have extra NID and a switch. Your modem does PPPoE. I didn't test with the modem in Bridge mode, but I think we will be able to get stats with the modem in either modes in this setup. Maybe someone could try and give some feedbacks with modem in Bridge mode.
This is my router setup:
Connection Type DHCP
LAN
Router IP Address 192.168.X.1 In this case X=2
Subnet Mask 255.255.255.0
DHCP 192.168.X.100 - 149
NID (set it to 'Obtain an IP address automatically' also works)
IP Address 192.168.X.101
Subnet Mask 255.255.255.0
Default Gateway 192.168.X.1
Type 192.168.1.254 to get to the modem.
enjoys, |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| said by vanhh  :This way will work, but you need a second network card and a switch in between your modem and router (modem ---- switch ---- router ---- PCs.) This is the part I hated it. To get the modem stats, you need to disable the NID connecting to your router and enable the NID connect to the switch. Then type 192.168.1.254 to get the stats. To get back to the internet, then you need to reverse the process disable and enable the NID. This is why I didn't like it. I'd just build a route to the modem:
route add 192.168.1.254 255.255.255.255 192.168.1.x if 2 -p
(Where 192.168.1.x it the IP address on the second NIC.)
I think that should do it. The '-p' switch makes the addition persistent across system reboots. I am not sure about the gateway IP address, but I believe using the second NIC will cause packets for 192.168.1.254 to be routed in that direction. I didn't include a metric because I believe the default value should work.
Using 255.255.255.255 as the subnet mask for the destination of the added router means that only packets to 192.168.1.254 will be routed to the second NIC.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
vanhh
join:2003-06-24
Sacramento, CA
edit:
May 10th, @10:26PM
| This should work with second NID without having enable/disable one of the NID or using special commands. The modem will be in Bridge mode and router will handle PPPoE.
- Modem is in Bridge mode
- router setup to handle PPPoE:
IP address 192.168.X.1 (X=any number less than 255 and not 1)
Subnet mask 255.255.255.0
Original NID set to 'Obtain IP address automatically' or you can assign static IP to it.
- Second NID connect to the switch:
IP address 192.168.1.X (X=any number less than 255 and not 254)
Subnet mask 255.255.255.0
Default gateway 192.168.1.254
You should be able to get the modem stats now by typing 192.168.1.254. Both NIDs can run concurrently now without having 'IP conflicted' error.
|
|
sideband
join:2000-07-02
Redwood City, CA
| reply to NormanS
Now that my router is back in my circuit and the DSL adpater behind it, I thought I would try to access the adapter Web server. Connection 2 below is PC/switch/DLink DIR-655/hub/DSL adapter. Connection 1 is PC/hub/DSL adapter. I then tried to build the route as suggested with adjustment for my situation. No luck. The adapter is in bridge mode.
C:\Users>route add 192.168.1.254 mask 255.255.255.255 169.254.71.47 if 1 -p
OK!
C:\Users>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::c157:975d:3a11:3d34%9
IPv4 Address. . . . . . . . . . . : 10.0.0.197
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.99
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::715f:c1a7:3b80:472f%7
Autoconfiguration IPv4 Address. . : 169.254.71.47
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
I then tried giving the NIC a static IP address of 192.168.1.0 and subnet mask of 255.255.255.255 and set the route accordingly. No luck. I then tried a static IP address of 192.168.1.64 and subnet mask of 255.255.255.0. No luck.
This is how it's set now:
C:\Users>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::c157:975d:3a11:3d34%9
IPv4 Address. . . . . . . . . . . : 10.0.0.197
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.99
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::715f:c1a7:3b80:472f%7
IPv4 Address. . . . . . . . . . . : 192.168.1.64
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
C:\Users>route print
===========================================================================
Interface List
9 ...00 1b fc 58 88 f3 ...... Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Con
troller
7 ...00 1b fc 58 93 fc ...... Marvell Yukon 88E8052 PCI-E ASF Gigabit Ethernet
Controller
1 ........................... Software Loopback Interface 1
12 ...00 00 00 00 00 00 00 e0 isatap.{E3FDC6AA-CCDC-43E9-9AC9-9F43D228DF93}
8 ...00 00 00 00 00 00 00 e0 isatap.{7A57BDC7-5E77-4184-AD68-370013C36DB0}
11 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.99 10.0.0.197 20
10.0.0.0 255.255.255.0 On-link 10.0.0.197 276
10.0.0.197 255.255.255.255 On-link 10.0.0.197 276
10.0.0.255 255.255.255.255 On-link 10.0.0.197 276
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
169.254.0.0 255.255.0.0 On-link 10.0.0.197 30
169.254.255.255 255.255.255.255 On-link 10.0.0.197 276
192.168.1.0 255.255.255.0 On-link 192.168.1.64 276
192.168.1.64 255.255.255.255 On-link 192.168.1.64 276
192.168.1.254 255.255.255.255 192.168.1.64 127.0.0.1 51
192.168.1.255 255.255.255.255 On-link 192.168.1.64 276
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 10.0.0.197 276
224.0.0.0 240.0.0.0 On-link 192.168.1.64 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 10.0.0.197 276
255.255.255.255 255.255.255.255 On-link 192.168.1.64 276
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.1.254 255.255.255.255 192.168.1.64 1
===========================================================================
Any thoughts on what to try next? |
|
d_l
Barsoom
Premium,MVM
join:2002-12-08
Reno, NV
| You could try Method 4: »SBC DSL FAQ »How do I access the modem GUI thru a router - advanced methods? with the PC-router-switch-modem if all devices behind the router are on static IPs (no using DHCP). Be certain that you have any software firewalls set to trust all IPs that you want to access.
Try Method 3 if you have a second router available. |
|
wayjac
Premium
join:2001-12-22
Indy | reply to sideband
Give this a try:
2210 Modem GUI access with a router |
|
sideband
join:2000-07-02
Redwood City, CA
| reply to d_l
Fixed it. I stuck with method two and used the route command described in the link you gave me, which routed to 192.168.0.1. I was using 192.168.1.254 With a syslog running and access to my adapter, I can now obsess over every detail of my connection  . There goes more UDP packets to ports 1026, 1027, and 1028 
Thanks,
Curt |
|
d_l
Barsoom
Premium,MVM
join:2002-12-08
Reno, NV | Ah, so you had a slight problem with the route command you had been using. |
|
