RE: Faking multiple physical adapters for DHCPDISCOVER



-----Original Message-----
From: Chuck Swiger [mailto:cswiger@xxxxxxx]
Sent: Tuesday, April 11, 2006 6:17 PM
Subject: Re: Faking multiple physical adapters for DHCPDISCOVER

Terrence Koeman wrote:
[ ... ]
I need to 'clone' the xl1 adapter to appear as three adapters, each
with a distinct MAC address. This because my provider has assigned me
three semi-static addresses of which I want to use 1 for outbound
NAT-traffic and two for static NAT.

These addresses are semi-static because they are basically MAC-based
reservations on the providers DHCP server, and it happens to be that
I'm required to aquire a DHCP lease for all three addresses for
routing to work properly. If I configure the addresses statically the
connectivity 'disappears' after a while.

The reason why your ISP has configured their system in such a fashion is to
prevent people from claiming multiple static IPs from a single machine.

If you're not happy with their AUP, use another provider, or pay for a
dedicated IP allocation of whatever size you need.

--
-Chuck

That's not the case here, I'm actually trying to use less IP's. And besides
that my ISP allows up to 16 IP's to be used in their AUP.

I have about 5 clients that can share 1 IP with NAT and I have 2 other
clients that need to have an IP of their own.

If I can have all IP's bound to the server then I can simply NAT the 5
clients and static-NAT the remaining 2. Otherwise I'd need to bridge/route
and do NAT at the same time, which is not possible here, because then the 5
NAT-ed clients would need to get their IP's from the local DHCP server and
the 2 bridged clients would need to get them from the ISP DHCP server. I
could block DHCP from being bridged and do DHCP proxying for the other 2
clients, but it'd make it all much more complicated.

--
Regards,
Terrence Koeman

MediaMonks B.V. (www.mediamonks.com)
Please quote all replies in correspondence.

Attachment: smime.p7s
Description: S/MIME cryptographic signature



Relevant Pages

  • Very large client network - NATing woes
    ... network (50,000 clients). ... The backend is all private IP (dhcp), so at some point we have to NAT ... As for the dhcp server, ...
    (comp.dcom.sys.cisco)
  • Re: DDNS Issues
    ... not so much the DHCP server itself. ... the clients themselves can register directly with DNS instead of the DHCP ...
    (microsoft.public.windows.server.dns)
  • Re: Multiple PTR records wont go away in the reverse zone.
    ... What about the DHCP setting "Dynamically update DNS A and PTR records only ... if requested", so clients will specify. ... I do agree with all your DHCP server recommendations (especially entering ... there is no other reason for a client to register in DNS when off ...
    (microsoft.public.windows.server.dns)
  • Re: SuSe10.0 - windowsXP networking problem !! plz help!!!!
    ... >>> The ADSL modem is a DHCP server, not a client one merely decided to ... >>> the ADSL modem, and ALL clients get assigned Local IP addresses by the ... >>> ports and some 16 WAN ports. ... >>it's DHCP server to pass out the default gateway parameter to the clients. ...
    (alt.os.linux.suse)
  • Re: Strange DHCP Problems
    ... clients which get incorrect subnet mask; maybe it's the hardware that causes ... try plugging 2-3 of the clients which get incorrect mask into a simple ... You can also use sniffer on different network segments between DHCP server ... > 2 months ago random clients began to get the wrong subnetmask. ...
    (microsoft.public.windows.server.networking)