Linksys 4-port router/switch: I've forwarded port 80, now how do I connect to the config page for the router?

Sorry for the x-posting but this way I potentially get advice from more
people. (That's advise for you English fellers).

I have a Linksys BEFSR41 4 port router/switch. it is working fine. Nat is
fine. Internet connection is fine, etc. I can configure it just fine using
the LAN address (which I have changed to 192.168.0.1 rather than changing
all my computers to the Linksys' subnet.)

I've set up port forwardign for port 80 to an internal machine.

Now how do I connect to the Linksys itself from the internet? All port 80
requests are going to the internal machine!

Thanks!
--
Jeffrey D. Silverman | jeffrey AT jhu DOT edu
Johns Hopkins University | Baltimore, MD
Website | http://www.wse.jhu.edu/newtnotes/

"Jeffrey Silverman" <(E-Mail Removed)> wrote in
news(E-Mail Removed):

> Sorry for the x-posting but this way I potentially get advice from
> more people. (That's advise for you English fellers).
>
> I have a Linksys BEFSR41 4 port router/switch. it is working fine. Nat
> is fine. Internet connection is fine, etc. I can configure it just
> fine using the LAN address (which I have changed to 192.168.0.1 rather
> than changing all my computers to the Linksys' subnet.)
>
> I've set up port forwardign for port 80 to an internal machine.
>
> Now how do I connect to the Linksys itself from the internet? All port
> 80 requests are going to the internal machine!
>
> Thanks!

You have to enable "Remote Management" in the Advanced settings, then the
access to the Linksys moves to port 1080


Cheers,
Mark

On Thu, 11 Sep 2003 15:49:54 -0500, Mark Taylor wrote:

<snip!>
> You have to enable "Remote Management" in the Advanced settings, then the
> access to the Linksys moves to port 1080
>
>
> Cheers,
> Mark

Fantastic! Thanks.
--
Jeffrey D. Silverman | jeffrey AT jhu DOT edu
Johns Hopkins University | Baltimore, MD
Website | http://www.wse.jhu.edu/newtnotes/

Mark Taylor <(E-Mail Removed)> writes:

>You have to enable "Remote Management" in the Advanced settings, then the
>access to the Linksys moves to port 1080

Alternatively, you could should be able to simply telnet into the Linksys
instead of using a browser at all :-)


Michael
--
Michael Buchenrieder * (E-Mail Removed) * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.

On Fri, 12 Sep 2003 06:36:40 +0000, Michael Buchenrieder wrote:

> Mark Taylor <(E-Mail Removed)> writes:
>
>>You have to enable "Remote Management" in the Advanced settings, then the
>>access to the Linksys moves to port 1080
>
> Alternatively, you could should be able to simply telnet into the Linksys
> instead of using a browser at all :-)
>
>
> Michael

I tried that. It doesn't seem to work. what am I missing? Incidentally, I
could not find mention of this feature in the user doc taht came with this
(kick ass) router, so maybe you *can't* telnet in.
--
Jeffrey D. Silverman | jeffrey AT jhu DOT edu
Johns Hopkins University | Baltimore, MD
Website | http://www.wse.jhu.edu/newtnotes/

"Jeffrey Silverman" <(E-Mail Removed)> wrote in
news(E-Mail Removed):

> On Fri, 12 Sep 2003 06:36:40 +0000, Michael Buchenrieder wrote:
>
>> Mark Taylor <(E-Mail Removed)> writes:
>>
>>>You have to enable "Remote Management" in the Advanced settings, then
>>>the access to the Linksys moves to port 1080
>>
>> Alternatively, you could should be able to simply telnet into the
>> Linksys instead of using a browser at all :-)
>>
>>
>> Michael
>
> I tried that. It doesn't seem to work. what am I missing?
> Incidentally, I could not find mention of this feature in the user doc
> taht came with this (kick ass) router, so maybe you *can't* telnet in.

Sorry, it's http protocols. It's a gui screen.

"Jeffrey Silverman" <(E-Mail Removed)> writes:

[telnet]

>I tried that. It doesn't seem to work. what am I missing? Incidentally, I
>could not find mention of this feature in the user doc taht came with this
>(kick ass) router, so maybe you *can't* telnet in.

If a "telnet <router IP> doesn't yield a sucessful connection, although
you can ping the router's interface, then it's probably a feature that
the Linksys is lacking, sorry. I use Longshine routers only, and these
allow for classical telnet access (which is very handy if you have to
adjust the router's IP address to be matching the network's IP range
that the router is to be added onto - because in such a situation the
HTTP setup may be unreachable without tweaking at least one installed
system on that network).

Michael

--
Michael Buchenrieder * (E-Mail Removed) * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.

On Fri, 12 Sep 2003 16:21:16 -0500, Mark Taylor wrote:

> "Jeffrey Silverman" <(E-Mail Removed)> wrote in
> news(E-Mail Removed):
>
>> On Fri, 12 Sep 2003 06:36:40 +0000, Michael Buchenrieder wrote:
>>
>>> Mark Taylor <(E-Mail Removed)> writes:
>>>
>>>>You have to enable "Remote Management" in the Advanced settings, then
>>>>the access to the Linksys moves to port 1080
>>>
>>> Alternatively, you could should be able to simply telnet into the
>>> Linksys instead of using a browser at all :-)
>>>
>>>
>>> Michael
>>
>> I tried that. It doesn't seem to work. what am I missing?
>> Incidentally, I could not find mention of this feature in the user doc
>> taht came with this (kick ass) router, so maybe you *can't* telnet in.
>
> Sorry, it's http protocols. It's a gui screen.

Well, the thing was only $US50, so I can't expect *every* feature now, can
I.

This thing makes a great replacement for my Linux firewall I had set up on
an old pc. No fan! (i.e. quiet)
--
Jeffrey D. Silverman | jeffrey AT jhu DOT edu
Johns Hopkins University | Baltimore, MD
Website | http://www.wse.jhu.edu/newtnotes/

Jeffrey Silverman wrote:

>> Sorry, it's http protocols. It's a gui screen.
>
> Well, the thing was only $US50, so I can't expect every feature now, can
> I.
>
> This thing makes a great replacement for my Linux firewall I had set up on
> an old pc. No fan! (i.e. quiet)
>

I recently bought an SMC 7004VWBR wireless router for $90 (CDN) with a $60
rebate from SMC. Currently, I have it between my LInux firewall and cable
modem. This means that anyone wanting to access my home network, has to
use a VPN, to get past my Linux firewall.

Incidentally, I'm currently sitting on my balcony, with my notebook
computer. I'm running Knode on my main desktop system, and using X over
the wireless, to display the program. Since I used ssh, to connect to the
desktop and redirect X, my newsgroup messages are protected by both ssh and
vpn encryption! ;-)

--

Fundamentalism is fundamentally wrong.

To reply to this message, replace everything to the left of "@" with
james.knott.

Michael Buchenrieder wrote:

> If a "telnet <router IP> doesn't yield a sucessful connection, although
> you can ping the router's interface, then it's probably a feature that
> the Linksys is lacking, sorry. I use Longshine routers only, and these
> allow for classical telnet access (which is very handy if you have to
> adjust the router's IP address to be matching the network's IP range
> that the router is to be added onto - because in such a situation the
> HTTP setup may be unreachable without tweaking at least one installed
> system on that network).
>

My SMC wireless router also doesn't appear to have any control method, other
than browser. What would be nice, would be SSH, instead of telnet. SSH
supports sending commands, without actually logging in. It also encrypts
everything, so a snooper can't read your password.

--

Fundamentalism is fundamentally wrong.

To reply to this message, replace everything to the left of "@" with
james.knott.