lynx

[kamper]

So I'm ssh'ed into a machine in my home and from there I want to login to my router (linksys, a few years old) to change some port forwardings. The problem is that the router uses http authentication and the user name is blank while the password is not. When I enter no username, lynx assumes that I don't want to use a password so I can't get authenticated. Anybody know how I can get it to use the blank username properly?

 

[Yomicron]

My Linksys router just ignores the username field, allowing me to put anything there.

I was able to access it using Lynx by going to 192.168.1.1 and entering a bogus username and the password. Lynx then gave me a connection error, but going to 192.168.1.1 again brought me to the config page.

 

[kamper]

Oh, I had tried one space as the username and got the connection error but I gave up after that

Just tried again and it goes! I never thought I'd actually get help on such an arcane little thing Thanks a bunch

Now to see if I can change the ssh forwarding without ripping the carpet completely out from under my feet (or at least I can hopefully get back on said carpet afterwards!)

 

[wkinney]

just dont restart the sshd service from your shell thread

 

[kamper]

You're implying that I can do it without killing my ssh connection? I don't have any intention of killing the service but I'm just trying to reason through the tcp issues of changing an interface mid-connection. To be clear, what I'm trying to do is change the port forwarding from my dhcp-attained interface on 192.168.0.101 to a statically assigned interface on 192.168.0.99.

But I guess the ssh connection is a persistent tcp connection which shifted off port 26 (that's what I'm using) at initiation time. So the router has the open connection through some other port. I change the forwarding from .101 to .99 which affects any new connections, but any current connections remain on the .101 interface until it closes. I'm safe then right?