Re: broken DNS proxying at public wireless hotspots

2007-02-04 Thread Chris Adams
Once upon a time, Chris Adams <[EMAIL PROTECTED]> said: > Once upon a time, Trent Lloyd <[EMAIL PROTECTED]> said: > > The flaw here is that DNS operates over 53(UDP), last time I checked SSH > > doesn't do UDP port forwarding? > > It doesn't forward UDP ports, but you can set up a full IP tunnel

Re: broken DNS proxying at public wireless hotspots

2007-02-04 Thread Chris Adams
Once upon a time, Trent Lloyd <[EMAIL PROTECTED]> said: > The flaw here is that DNS operates over 53(UDP), last time I checked SSH > doesn't do UDP port forwarding? It doesn't forward UDP ports, but you can set up a full IP tunnel with it now. -- Chris Adams <[EMAIL PROTECTED]> Systems and Netwo

Re: broken DNS proxying at public wireless hotspots

2007-02-04 Thread Suresh Ramasubramanian
On 2/3/07, Gadi Evron <[EMAIL PROTECTED]> wrote: On Sat, 3 Feb 2007, Suresh Ramasubramanian wrote: > What do nanogers usually do when caught in a situation like this? Important question: if memory serves, and you are in the "Paris Charles de Gaulle International Airport", wireless costs money.

Re: broken DNS proxying at public wireless hotspots

2007-02-03 Thread Mark Foster
On Sun, 4 Feb 2007, Peter J. Cherny wrote: At 04:58 PM 4/2/07, Trent Lloyd <[EMAIL PROTECTED]> wrote: * Set up the profile, to your house/work/etc, of your favorite SSH client to forward port 53 local to port 53 on your remote machine. The flaw here is that DNS operates over 53(UDP), last t

Re: broken DNS proxying at public wireless hotspots

2007-02-03 Thread Trent Lloyd
Hi Joe, On Sun, Feb 04, 2007 at 01:30:58AM -0500, Joe Abley wrote: > > On 4-Feb-2007, at 00:58, Trent Lloyd wrote: > > >The flaw here is that DNS operates over 53(UDP), last time I > >checked SSH > >doesn't do UDP port forwarding? > > In the interests of dispelling a common myth, DNS operate

Re: broken DNS proxying at public wireless hotspots

2007-02-03 Thread Peter J. Cherny
At 04:58 PM 4/2/07, Trent Lloyd <[EMAIL PROTECTED]> wrote: >> * Set up the profile, to your house/work/etc, of your favorite SSH >> client to forward port 53 local to port 53 on your remote machine. >The flaw here is that DNS operates over 53(UDP), last time I checked >SSH doesn't do UDP port fo

Re: broken DNS proxying at public wireless hotspots

2007-02-03 Thread Roy
Trent Lloyd wrote: On Sat, Feb 03, 2007 at 09:22:30PM -0800, Lasher, Donn wrote: If so, how do you configure your client operating system of choice to use the novel, un-proxied ports instead of using port 53? * Set up the profile, to your house/work/etc, of your favorit

Re: broken DNS proxying at public wireless hotspots

2007-02-03 Thread Joe Abley
On 4-Feb-2007, at 00:58, Trent Lloyd wrote: The flaw here is that DNS operates over 53(UDP), last time I checked SSH doesn't do UDP port forwarding? In the interests of dispelling a common myth, DNS operates over both 53/udp and 53/tcp. However, given that a substantial portion of most

Re: broken DNS proxying at public wireless hotspots

2007-02-03 Thread Trent Lloyd
On Sat, Feb 03, 2007 at 09:22:30PM -0800, Lasher, Donn wrote: > >If so, how do you configure your client operating system of choice to > use the novel, un-proxied ports instead of using > > port 53? > > * Set up the profile, to your house/work/etc, of your favorite SSH > client to forward port 53

RE: broken DNS proxying at public wireless hotspots

2007-02-03 Thread Lasher, Donn
>If so, how do you configure your client operating system of choice to use the novel, un-proxied ports instead of using > port 53? * Set up the profile, to your house/work/etc, of your favorite SSH client to forward port 53 local to port 53 on your remote machine. * Make sure your SSH Profile c

Re: broken DNS proxying at public wireless hotspots

2007-02-03 Thread Steven M. Bellovin
On Sat, 03 Feb 2007 13:29:13 -0600 Carl Karsten <[EMAIL PROTECTED]> wrote: > > > Sure I could route dns queries out through a ssh tunnel but the > > latency makes this kind of thing unusable at times. instead of an > > ssh tunnel, how about simple port forwarding? > > /etc/resolv.conf > nameser

Re: broken DNS proxying at public wireless hotspots

2007-02-03 Thread Carl Karsten
Sure I could route dns queries out through a ssh tunnel but the latency makes this kind of thing unusable at times. instead of an ssh tunnel, how about simple port forwarding? /etc/resolv.conf nameserver 127.0.0.1 And then whatever it takes to forward 127.0.0.1:53 to a dns that is listing o

RE: broken DNS proxying at public wireless hotspots

2007-02-03 Thread John van Oppen
Subject: broken DNS proxying at public wireless hotspots Right now, I'm on a swisscom eurospot wifi connection at Paris airport, and this - yet again - has a DNS proxy setup so that the first few queries for a host will return some nonsense value like 1.2.3.4, or will return the records for

Re: broken DNS proxying at public wireless hotspots

2007-02-03 Thread Peter Dambier
I am running djbdns and my own root-server (tinydns) on my laptop. To axfr the root and some other zones, I use port 3001 (Cesidian Root). With cloned (not actually slaved) zones I have no problem at all but others might still get me. I have seen the Mac can use things like nameserver 192.168.2

Re: broken DNS proxying at public wireless hotspots

2007-02-02 Thread Gadi Evron
On Sat, 3 Feb 2007, Suresh Ramasubramanian wrote: > What do nanogers usually do when caught in a situation like this? Important question: if memory serves, and you are in the "Paris Charles de Gaulle International Airport", wireless costs money. This is after paying, right? I had this problem i

Re: broken DNS proxying at public wireless hotspots

2007-02-02 Thread Trent Lloyd
On Sat, Feb 03, 2007 at 01:00:29AM -0600, Stephen Sprunk wrote: > Thus spake "Trent Lloyd" <[EMAIL PROTECTED]> > >One thing I have noticed to be unfortunately more common that I would > >like is routers that misunderstand IPv6 requests and return an > >A record of 0.0.0.1 > > > >So if you are

Re: broken DNS proxying at public wireless hotspots

2007-02-02 Thread Stephen Sprunk
Thus spake "Trent Lloyd" <[EMAIL PROTECTED]> One thing I have noticed to be unfortunately more common that I would like is routers that misunderstand IPv6 requests and return an A record of 0.0.0.1 So if you are using (for the most part) anything other than windows, or Windows Vista, thi

Re: broken DNS proxying at public wireless hotspots

2007-02-02 Thread Chris L. Morrow
On Sat, 3 Feb 2007, Fergie wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Use OpenDNS? > > - -- "Suresh Ramasubramanian" <[EMAIL PROTECTED]> wrote: > > > Right now, I'm on a swisscom eurospot wifi connection at Paris > airport, and this - yet again - has a DNS proxy setup so tha

Re: broken DNS proxying at public wireless hotspots

2007-02-02 Thread Fergie
Yes, then he's screwed. :-) As we all are in a similar situation. Mea culpa. - ferg -- Joe Abley <[EMAIL PROTECTED]> wrote: On 3-Feb-2007, at 06:20, Fergie wrote: > Use OpenDNS? OpenDNS provides service on other than 53/tcp and 53/udp? If so, how do you configure your client operating sy

Re: broken DNS proxying at public wireless hotspots

2007-02-02 Thread william(at)elan.net
On Sat, 3 Feb 2007, Fergie wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Use OpenDNS? - - ferg How can that make a difference when he already said that setting NS in "resolv.conf" does not help. BTW - personally if name resolution at hotspot is not working (and sometimes even if

Re: broken DNS proxying at public wireless hotspots

2007-02-02 Thread Joe Abley
On 3-Feb-2007, at 06:20, Fergie wrote: Use OpenDNS? OpenDNS provides service on other than 53/tcp and 53/udp? If so, how do you configure your client operating system of choice to use the novel, un-proxied ports instead of using port 53? Joe

Re: broken DNS proxying at public wireless hotspots

2007-02-02 Thread Trent Lloyd
One thing I have noticed to be unfortunately more common that I would like is routers that misunderstand IPv6 requests and return an A record of 0.0.0.1 So if you are using (for the most part) anything other than windows, or Windows Vista, this may be related to what you are seeing. Cheers,

Re: broken DNS proxying at public wireless hotspots

2007-02-02 Thread Fergie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Use OpenDNS? - - ferg - -- "Suresh Ramasubramanian" <[EMAIL PROTECTED]> wrote: Right now, I'm on a swisscom eurospot wifi connection at Paris airport, and this - yet again - has a DNS proxy setup so that the first few queries for a host will retu

broken DNS proxying at public wireless hotspots

2007-02-02 Thread Suresh Ramasubramanian
Right now, I'm on a swisscom eurospot wifi connection at Paris airport, and this - yet again - has a DNS proxy setup so that the first few queries for a host will return some nonsense value like 1.2.3.4, or will return the records for com instead. Some 4 or 5 minutes later, the dns server might