> BeringRC3 system, trying to get both a small DMZ and a Masqueraded WIN
net
> connected to 5 dedicated IP's via cable modem.
>
> My local cable company uses some sort of cisco hardware/software
security
> that matches each IP address to a specific MAC address. The want me to
> connect the Cable Modem ethernet and 5 seperate ethernet cards to a
hub.
> Then each card gets 1 IP routed to it. Then the data could pass thru
the
> firewall and out to a 6th and 7th card for DMZ and Windows net.
>
> YUK
>
> Among other things I dont think I have a motherboard with 7 PCI slots.
>
> Can Bering tag each outgoing packet with a MAC depending on its source
IP?
> Incomming packets should be trivial.
> or
> Can proxy arp pass the MAC address thru the firewall?

Hmm...I'm not familiar with anything that will "spoof" multiple MAC
addresses from a single interface.  It *IS* possible (things like LaBrea
do it), but the things I know about all talk directly to the low-level
network, bypassing things like the kernel's IP stack.  If you don't want
to hand-code a custom application (and can't find anyone who has or is
willing to), I don't think you can do exactly what you describe.

What you *CAN* do is try reading between the lines, and using an
alternate configuration.  Your cable-company is probably using MAC -> IP
mapping in their DHCP servers, which is why they want unique MAC addy's
for each IP.  There is likely *NO* filtering on traffic by destination
MAC address.  If the cable company has given you a range of static IP's,
and you know what they are, simply configure your Bering system for all
of the IP's, and don't worry that they're all coming from the same MAC
addy.  You should only be in trouble if your cable company does
something really fancy, like block traffic to/from IP's with
non-existant/expired DHCP leases, but that would require extra work (not
to mention some finesse), which seems against the grain of the typical
ISP :-)

If your IP's are static, but you don't know them, you can override your
built-in MAC addy, and run your DHCP client to "collect" the list of
IP's assigned to you, then use the procedure above.

HTH...

Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)



-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html

Reply via email to