[94735] in North American Network Operators' Group
Re: broken DNS proxying at public wireless hotspots
daemon@ATHENA.MIT.EDU (Roy)
Sun Feb 4 02:05:05 2007
Date: Sat, 03 Feb 2007 22:54:37 -0800
From: Roy <r.engehausen@gmail.com>
To: Trent Lloyd <lathiat@bur.st>
Cc: "Lasher, Donn" <DLasher@newedgenetworks.com>, nanog@merit.edu
In-Reply-To: <20070204055821.GA16714@bur.st>
Errors-To: owner-nanog@merit.edu
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 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
>
>
Looks like someone already has this exact case figured out
http://zarb.org/~gc/html/udp-in-ssh-tunneling.html
