re: Lynx, auth, dump and kernel 2.4.x
I'm going to answer my own question on this one.
I was able to get lynx to work under 2.4.9 by using a url of
http://linky/Status.htm (instead of the IP, and "linky" is defined in my
/etc/hosts)
I don't know why this works, and wish I had tried it sooner!! Either
way, it'd be nice to have some insight as to what's going on..
I also noted a huge increase in bandwidth once I went to 2.4.9. The
2.2.19 was getting about 1.0Mbps (this is on the Linksys router/switch,
the card is at 100mbps FD). Once I went to 2.4.9 I was over 50Mbps.
Doug
> -----Original Message-----
> From: Doug Baker [mailto:dbaker@wesleyan.edu]
> Sent: Thursday, August 30, 2001 8:58 AM
> To: 'debian-user@lists.debian.org'
> Subject: Lynx, auth, dump and kernel 2.4.x
>
>
> Hi all. I recently upgraded my debian-woody to kernel 2.4.9.
> The kernel compilation went fine and upon reboot all was
> well, with one glitch.
>
> To update my dynamic DNS, I use lynx to grab the external IP
> from a Linksys BEFSR41 router. This function broke once I
> upgraded to 2.4.9 (and was working fine under 2.2.19). I also
> tried 2.4.8 with the same results.
>
> The specific problem : my lynx (2.8.4rel.1) command is like
> this : Lynx -dump -auth=admin:pswd http://10.10.10.1/Status.htm
>
> This should print the web page to the screen, then I grep for the IP.
>
> But under 2.4.9, (actually, 2.4.8 right now) I get this :
> ---
> lynx -dump -auth=admin:pswd http://10.10.10.1/Status.htm
> Looking up 10.10.10.1 10.10.10.1 Making HTTP connection to
> 10.10.10.1 Sending HTTP request. HTTP request sent; waiting
> for response.
> Alert!: Access without authorization denied -- retrying
> Retrying with access authorization information. Looking up
> 10.10.10.1 10.10.10.1 Making HTTP connection to 10.10.10.1
> Alert!: Unable to connect to remote host.
>
> lynx: Can't access startfile http://10.10.10.1/Status.htm
> --
>
> Now the funny thing is that only the "-dump" is what's
> causing the problem. When I eliminate that and open the web
> page interactively (still passing the auth at the command
> line) it's fine!
>
> Note that I don't seem to be having any other troubles with
> networking or otherwise.
>
> Any ideas? It's driving me nuts! Thanks!
>
> Doug Baker
>
>
Reply to: