From: "Peter Marshall" <peter.marshall@caris.com>
To: Daniel Chemko <dchemko@smgtec.com>,
Ramin Dousti <ramin@cannon.eng.us.uu.net>
Cc: Thorsten Scherf <tscherf@web.de>, netfilter@lists.netfilter.org
Subject: Re: Nat with a dynamic IP
Date: Fri, 5 Sep 2003 16:28:57 -0300 [thread overview]
Message-ID: <03d101c373e3$f388dff0$49caa8c0@caris.priv> (raw)
In-Reply-To: 7C9884991ADAE0479C14F10C858BCDF52E3680@alderaan.smgtec.com
yep. (but I wish I had access to their switches and vlans :)
Thanks for the tips. everyone.
----- Original Message -----
From: "Daniel Chemko" <dchemko@smgtec.com>
To: "Ramin Dousti" <ramin@cannon.eng.us.uu.net>
Cc: "Peter Marshall" <peter.marshall@caris.com>; "Thorsten Scherf"
<tscherf@web.de>; <netfilter@lists.netfilter.org>
Sent: Friday, September 05, 2003 4:23 PM
Subject: RE: Nat with a dynamic IP
> It is to an ISP, so no beans...
>
> -----Original Message-----
> From: Ramin Dousti [mailto:ramin@cannon.eng.us.uu.net]
> Sent: Friday, September 05, 2003 12:14 PM
> To: Daniel Chemko
> Cc: Peter Marshall; Thorsten Scherf; netfilter@lists.netfilter.org
> Subject: Re: Nat with a dynamic IP
>
> Here is an idea, It might cost you some vlanning efforts on both the
> dhcp client and the dhcp server:
>
> vconfig add eth2 10
> vconfig add eth2 11
> vconfig add eth2 12
> vconfig add eth2 13
>
> dhcpcd eth2.10
> dhcpcd eth2.11
> dhcpcd eth2.12
> dhcpcd eth2.13
>
>
next prev parent reply other threads:[~2003-09-05 19:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 19:23 Nat with a dynamic IP Daniel Chemko
2003-09-05 19:28 ` Peter Marshall [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-05 17:16 Daniel Chemko
2003-09-05 17:47 ` Peter Marshall
2003-09-05 19:17 ` Ramin Dousti
2003-09-06 0:34 ` Jim Carter
2003-09-05 19:13 ` Ramin Dousti
2003-09-05 13:34 Peter Marshall
2003-09-05 14:05 ` Thorsten Scherf
2003-09-05 14:36 ` Peter Marshall
2003-09-05 17:11 ` Ramin Dousti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='03d101c373e3$f388dff0$49caa8c0@caris.priv' \
--to=peter.marshall@caris.com \
--cc=dchemko@smgtec.com \
--cc=netfilter@lists.netfilter.org \
--cc=ramin@cannon.eng.us.uu.net \
--cc=tscherf@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox