Just started using Lynx again, or I'm trying to, :( but these days I'm
running my main PC behind a router box. Everything else seems ok with
going through a masquerading firewall/LAN connection, but Lynx just sits
there trying to connect to the router address.

I've fried my brain trying to set up the Lynx variables, and am now
taking a short break from feeding the (clearly) wrong questions into
search engines.

Anybody got one of those "Simple mate! Just....." tips, or pointers to
resources that are focussed on this probably simple problem?

Ta

--
*===( http://www.jonestheweb.myby.co.uk/
*===( http://principiadiscordia.com/
*===( http://www.badphorm.co.uk/

On Fri, 06 Jun 2008 17:47:59 +0000, Mike wrote:

> Just started using Lynx again, or I'm trying to, :( but these days I'm
> running my main PC behind a router box. Everything else seems ok with
> going through a masquerading firewall/LAN connection, but Lynx just sits
> there trying to connect to the router address.
>
> I've fried my brain trying to set up the Lynx variables, and am now
> taking a short break from feeding the (clearly) wrong questions into
> search engines.
>
> Anybody got one of those "Simple mate! Just....." tips, or pointers to
> resources that are focussed on this probably simple problem?

Lynx seems to prefer using IPv6 by default. Does it *ever* connect, if
you wait long enough (2 or 3 minutes)? What happens if you do

lynx `nslookup desired_site_address` ?

Hello,

Mike a écrit :
> Just started using Lynx again, or I'm trying to, :( but these days I'm
> running my main PC behind a router box. Everything else seems ok with
> going through a masquerading firewall/LAN connection, but Lynx just sits
> there trying to connect to the router address.

Can you please elaborate "everything else" ?
How does lynx try to connect to the router address (protocol, port) ? It
is not supposed to do so, except for DNS resolution if the router is
declared as a nameserver in /etc/resolv.conf.

> I've fried my brain trying to set up the Lynx variables, and am now
> taking a short break from feeding the (clearly) wrong questions into
> search engines.

What variables have you set ? You haven't set WWW_access_GATEWAY,
http_proxy and so on with the router address, have you ? A NAT router is
usually not a proxy nor a "gateway server".

Responding to Mark Madsen:

> On Fri, 06 Jun 2008 17:47:59 +0000, Mike wrote:
>
>> Just started using Lynx again, or I'm trying to, :( but these days I'm
>> running my main PC behind a router box. Everything else seems ok with
>> going through a masquerading firewall/LAN connection, but Lynx just
>> sits there trying to connect to the router address.
>>
>> I've fried my brain trying to set up the Lynx variables, and am now
>> taking a short break from feeding the (clearly) wrong questions into
>> search engines.
>>
>> Anybody got one of those "Simple mate! Just....." tips, or pointers to
>> resources that are focussed on this probably simple problem?
>
> Lynx seems to prefer using IPv6 by default. Does it *ever* connect, if
> you wait long enough (2 or 3 minutes)? What happens if you do
>
> lynx `nslookup desired_site_address` ?

Hmmm.Interesting...

nslookup nslookup http://en.wikipedia.org

gets me

Server: 208.67.222.222
Address: 208.67.222.222#53

Non-authoritative answer:
Name: http://en.wikipedia.org
Address: 67.215.66.132

and

lynx 67.215.66.132
lynx http://67.215.66.132

gets me a page full of Lynx switches advice.

Most curious.

--
*===( http://www.jonestheweb.myby.co.uk/
*===( http://principiadiscordia.com/
*===( http://www.badphorm.co.uk/

Mike a écrit :
>
> nslookup nslookup http://en.wikipedia.org

Wrong query, try "nslookup en.wikipedia.org" instead.

> gets me
>
> Server: 208.67.222.222
> Address: 208.67.222.222#53

This is the address of resolver1.opendns.com. Looks like your box uses
OpenDNS nameservers. They mangle replies and thus cannot be trust when
doing DNS tests.

> Non-authoritative answer:
> Name: http://en.wikipedia.org
> Address: 67.215.66.132

This is the address of hit-servfail.opendns.com, not en.wikipedia.org.
Instead of replying with the DNS error your query deserved, OpenDNS
replied with the address of their web server handling failed queries.

Responding to Pascal Hambourg:

> Mike a écrit :
>>
>> nslookup nslookup http://en.wikipedia.org
>
> Wrong query, try "nslookup en.wikipedia.org" instead.
>
>> gets me
>>
>> Server: 208.67.222.222
>> Address: 208.67.222.222#53
>
> This is the address of resolver1.opendns.com. Looks like your box uses
> OpenDNS nameservers. They mangle replies and thus cannot be trust when
> doing DNS tests.

Ah. Thats a bad thing.

>> Non-authoritative answer:
>> Name: http://en.wikipedia.org
>> Address: 67.215.66.132
>
> This is the address of hit-servfail.opendns.com, not en.wikipedia.org.
> Instead of replying with the DNS error your query deserved, OpenDNS
> replied with the address of their web server handling failed queries.

And another bad thing. Must dig out the VirginMedia nameserver addresses.
Might as well get one problem off the list before we go any further. :(

--
*===( http://www.jonestheweb.myby.co.uk/
*===( http://principiadiscordia.com/
*===( http://www.badphorm.co.uk/

>
> >> Server: * * * * 208.67.222.222
> >> Address: * * * *208.67.222.222#53
>
> > This is the address of resolver1.opendns.com. Looks like your box uses
> >OpenDNSnameservers. They mangle replies and thus cannot be trust when
> > doing DNS tests.
>
> Ah. Thats a bad thing.
>

If you're looking for a reliable alternative to OpenDNS, I use
iFireFly for free DNS resolution:
http://www.ifirefly.com

Responding to snoopy2:


>> >> Server: Â* Â* Â* Â* 208.67.222.222
>> >> Address: Â* Â* Â* Â*208.67.222.222#53
>>
>> > This is the address of resolver1.opendns.com. Looks like your box
>> > uses
>> >OpenDNSnameservers. They mangle replies and thus cannot be trust when
>> > doing DNS tests.
>>
>> Ah. Thats a bad thing.
>>
>>
> If you're looking for a reliable alternative to OpenDNS, I use iFireFly
> for free DNS resolution:
> http://www.ifirefly.com

I'll take a look. Cheers.

--