| [DSL] Problem logging into Speedtouch (bridged) Hi,
I've been using my speedtouch ST516 in routed mode for 3 years. This worked, even though I have a Belkin router sitting behind it. I have just switched to bridged mode on the Speedtouch after some account issues forced me to reset everything. (And I read some comments that this was better, and the tech support person wanted it that way... Okay!)
The problem is that while our Internet access is working, I am unable to access the Speedtouch from my internal network. I try access 192.168.1.254 and it just times out. I've tried that in a telnet window and in the browser, no difference.
- The Speedtouch is in bridged mode, DHCP turned off, All the settings verified (I think!)
- I have a Belkin router/switch
- the Belkin is now handling the login
- the belkin is on 192.168.1.1, Mask 255.255.255.0, DNS from the modem,
- My internal machines are all Mac, if that matters.
- If I plug my mac directly into the speedtouch, THEN I can access the modem. But with the Belkin router in there, I can't.
- I've looked through the Belkin settings, and I don't see anything that would be filtering internal traffic.
I found this old forum thread on this topic: »Problems logging into Speedtouch in Bridge Mode
But that didn't seem to solve anything either.
Any pointers would be greatly appreciated.
...art
ps: I speak Linux, Mac, Windows, Solaris...  |
|
| I suspect that since the modem IP (192.168.1.254) is in the same subnet and IP range as the Belkin, the router thinks that when you're trying to access 192.168.1.254 that it should be within your internal network, and doesn't know to look to the WAN side. If you change your Belkin to another range, maybe 192.168.2.1 it might work. |
|
|
|
 Mike2009
join:2009-01-13
Ottawa, ON
kudos:3 | reply to twobikes
This will work for you: »Re: Any ideas how to Do MLPP ? with xp? |
|
| reply to Scycotic
Thanks, but nope, that doesn't work.
Looks like I may have to just switch the modem off of bridged mode to get it to behave the way I want. Oh well, it did work the other way, I'm not entirely sure why the documentation insists that I configure it in bridged mode when I have an intranet switch. |
|
Reviews:
 ·voip.ms
·link2voip
| The diagram in Mike2009's link will work for you.
The other option is to get a router that can do IP aliases on the WAN, or just use Tomato, which has a setting which makes it easy to access your modem while in bridge mode.
Not that you have to run bridge mode, but modems typically make poor routers, and the double NAT can complicate troubleshooting.
--
db |
|
TypeS
join:2012-12-17
London, ON
kudos:1 Reviews:
 ·TekSavvy Cable
| reply to twobikes
I had the same issue with my TP-Link TD-8816, I would never be able to access the GUI when in bridged mode and behind a router. I'd have to disconnect the router and plug directly into the modem, leaving it still in bridged mode. But my connection with DSL from TSI was so stable, I rarely ever had to login into the modem. So I never investigated the odd behavior.
It's not a bridged vs routed mode issue though, if you leave it bridged and direct connect into with with a computer, it will work (it did for me at least). So the above poster is probably on the right track, its a route confliction. If theyre on the same subnet, your router will take your http request to that IP and try to switch it instead of route because it believes the address is on the same subnet (assuming both devices are using 192.168.1.0/24). |
|
 PlatooN
join:2007-02-13
Kitchener, ON | reply to twobikes
when in bridge mode, communications between the modem and router are at layer 2 (mac) not at layer 3 (ip).
some router firmware's (tomato comes to mind) will let you enter an iptables mask command to allow communication to 10.0.0.138 (the OTHER ip on a speedtouch).
Why do you want to login to the modem though? if it's bridged (as it should be) there is literally nothing to see or change. |
|
| said by PlatooN:when in bridge mode, communications between the modem and router are at layer 2 (mac) not at layer 3 (ip).
...
Why do you want to login to the modem though? if it's bridged (as it should be) there is literally nothing to see or change.
I did not know that (about the layer 2 ...).
Why? Mostly just because. It's mine, and I want to be able to SEE the menus and settings. Also because when (not if) something inevitably breaks, I would like to be able to look at things without having to dismantle my network and wrestle with the cable tangle. And partly because it just seems... dumb. Dumb that it's right there hooked together but "can't get there from here".
Who would intentionally design it like that! When this started I was sure that something was actually broken or misconfigured that I could not see the modem. Now I'm beginning to accept that that is just the way it is. Still seems like a stupid design. |
|
| If I'm correct and it's like the modems I use then it depends on your router capabilities or if you check the diagram linked above.
First rule is you don't want conflicts with the IP subnets, change one or the other.
I've done it with Tomato, it has an easy function that does the iptables configs to give you access.
On the Mikrotik or any decent linux type router you setup a virtual WAN IP and rules to gain access.
Then you have easy access like you're looking for. |
|
| reply to twobikes
You also have to keep in mind that you're dialing PPPoE from the router, essentially bypassing the modem...it's like making it a standalone modem where IIRC there's no menu to see or configure.
In a way it's like having a router within a network as a VPN client...the computer behind that router wouldn't be able to see anything of the rest of the network as the VPN tunnel would block it. In your case you wouldn't be able to access anything of your modem because you have a "tunnel" connecting you to Bell. |
|
MZB
join:2010-11-25
Dunrobin, ON | If it helps anyone, the ST516 also responds to 10.0.0.138
It's possible to add routing rules using Tomato firmware (or use one of the TomatoUSB variants which support this from the GUI) which route from the LAN to the correct interface.
No idea how to add a route to for your router with unspecified (presumably stock) firmware, however. |
|
| reply to Scycotic
said by Scycotic:You also have to keep in mind that you're dialing PPPoE from the router, essentially bypassing the modem...it's like making it a standalone modem where IIRC there's no menu to see or configure.
In a way it's like having a router within a network as a VPN client...the computer behind that router wouldn't be able to see anything of the rest of the network as the VPN tunnel would block it. In your case you wouldn't be able to access anything of your modem because you have a "tunnel" connecting you to Bell.
Sounds right but for sure I can see the modem from behind a router doing the PPoE. The modem still has an IP you can connect to for stats and what not, the normal web UI of the modem. Like I said I added a virtual IP to the physical WAN port that also does PPPoE. |
|
