Email address obfuscation in effect -- please
click here to turn it off.
[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
- To: "MLUG Members" <EMAIL:PROTECTED>
- Subject: Re: [MLUG] wildcard with dyndns
- From: "Nimrod Levy" <EMAIL:PROTECTED>
- Date: Mon, 12 Feb 2007 06:39:23 -0600
- Delivery-date: Mon, 12 Feb 2007 06:41:08 -0600
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=bGZZSrg/KDplv2bKyNNyQ6XRnJ8BkKdaNnzDEUUyDiEWSo/xg+1h8uGG53njoKcIRejChiiB/7lCxzrSVIvAW85YzJfwlteLbVvY4dRUHGqEF4gz5zQbpbmSgoJLQafWCgDhzvFxLUaUcIAzoSp2OxDtU+3mCxUFtwvXEuIWwes=
- Envelope-to: EMAIL:PROTECTED
- In-reply-to: <EMAIL:PROTECTED>
- References: <EMAIL:PROTECTED> <EMAIL:PROTECTED> <EMAIL:PROTECTED>
- Reply-to: MLUG Members <EMAIL:PROTECTED>
- Sender: EMAIL:PROTECTED
It wasn't clear to me that both machines were behind a NAT router.
AFAIK, the only way to do this would be with an application layer proxy. For example if it were web traffic you were dealing with, you'd need to have a web proxy set up to receive all traffic and direct the requests to the appropriate internal box. Not all protocols will play nice with a scheme like this.
--
Nimrod
--
Nimrod
_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members