[94733] in North American Network Operators' Group
Re: broken DNS proxying at public wireless hotspots
daemon@ATHENA.MIT.EDU (Trent Lloyd)
Sun Feb 4 01:03:47 2007
Date: Sun, 4 Feb 2007 14:58:21 +0900
From: Trent Lloyd <lathiat@bur.st>
To: "Lasher, Donn" <DLasher@newedgenetworks.com>
Cc: nanog@merit.edu
In-Reply-To: <DEB70BE9B019B14EBE4D34B2FD2E741024F26790@jabba.ad.newedgenetworks.com>
Errors-To: owner-nanog@merit.edu
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 local to port 53 on your remote machine.
<snip>
> Same type of config works great for HTTP (with squid, and browser proxy
> settings) etc..
The flaw here is that DNS operates over 53(UDP), last time I checked SSH
doesn't do UDP port forwarding?
Cheers,
Trent
