Hello Seth,
Not sure why you want to do this, since you could just assign a static private
IP to the other user. Also, now-a-days, most NATs don't break PPTP or IPSEC, so I
don't think you really need to do this, unless this user plans on hosting servers or
services on their network. If they plan to (not sure what type of equipment you have),
but you could bridge real IPs across a wireless setup, or could do One to One (real IP
to NAT addressing). I still think this is unnecessary, and just give the user a static
private IP.
-Ben
----- Original Message -----
From: "Seth Rothenberg" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 12, 2002 12:14 PM
Subject: [nycwireless] Re: NAT Squared ?
>
> One of my neighbors asked if we could give him
> a static IP (i.e., across the wireless LAN).
> In Corporate VPN terms, that means
> a real Internet IP address, not NAT'd or
> Firewalled. I had 2 ideas how to do it,
> and wondered if anyone has experience.
>
> 1) VPN. Still don't know much about VPN,
> but I imagine I could use creative netmasks
> to subnet my ISP's space, allowing some of
> my segments to have "real" IP addresses, but
> only routing the ones that my ISP gave to me.
> (I have done similar things in Solaris).
>
> 2) This one knocked me out when I thought
> of it, but don't know if it can work.
> What if I use static NAT'ing....
> eg 128.2.3.44-NAT->192.168.1.44 ((my cloud))
> 192.168.1.1---routed to---192.168.56.1
> (last link)
> 192.168.56.44<<--NAT-->>128.2.3.44
> This is oversimplified, but NAT-aware people
> will get it and will affirm or reject my idea.
> Thanks
> Seth
>
>
>
>
>
> --
> NYCwireless - http://www.nycwireless.net/
> Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/
> Archives: http://lists.nycwireless.net/pipermail/nycwireless/
>
--
NYCwireless - http://www.nycwireless.net/
Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/
Archives: http://lists.nycwireless.net/pipermail/nycwireless/
