A bit more detail…Matt also needs both DHCP clients to operate from the same 
source MAC address.

I sent him a solution that uses two MAC addresses on the same physical port and 
does not involve VLANs, although its obviously of no use because it does not 
meet his requirements.

What MikroTik needs is the ability to specify DHCP Client ID's when creating 
DHCP client instances. Most servers support using client ID's to identify hosts 
so this would be an acceptable way to issue two IPs to a single MAC as the 
client ID would be the identifier between the two.

--
Blake Covarrubias

On Nov 15, 2010, at 4:23 PM, Matt Jenkins wrote:

> In this instance, I have no control upstream beyond the mikrotik....
> 
> On 11/15/2010 03:16 PM, Josh Luthman wrote:
>> You can only have 1 dhcp server port per interface.  You'll need to do vlans.
>> 
>> On Nov 15, 2010 6:12 PM, "Matt Jenkins" <m...@smarterbroadband.net> wrote:
>> > Ok simplification of what I need to do. I need to get more than 1 DHCP 
>> > address on the same physical ethernet port.... I can assign more than 1 
>> > static address, so why not more than 1 dynamic address?
>> > 
>> > On 11/02/2010 01:15 PM, Matt Jenkins wrote:
>> >> How do I create a subinterface on an ethernet port on a rb750?
>> >>
>> >> Bridged CPE -> Tik Port1 -> Port2 Cust 1
>> >> -> Port3 Cust 2
>> >>
>> >> I need to create two sub interfaces on Port 1. One for each customer to
>> >> receive an IP via DHCP. Then I need to NAT each of those sub interfaces
>> >> to each of cooresponding customer interfaces.
>> >>
>> >> Thanks,
>> >>
>> >> - Matt
>> >>
>> >>
>> >> --------------------------------------------------------------------------------
>> >> WISPA Wants You! Join today!
>> >> http://signup.wispa.org/
>> >> --------------------------------------------------------------------------------
>> >>
>> >> WISPA Wireless List: wireless@wispa.org
>> >>
>> >> Subscribe/Unsubscribe:
>> >> http://lists.wispa.org/mailman/listinfo/wireless
>> >>
>> >> Archives: http://lists.wispa.org/pipermail/wireless/
>> >> 
>> > 
>> > 
>> > --------------------------------------------------------------------------------
>> > WISPA Wants You! Join today!
>> > http://signup.wispa.org/
>> > --------------------------------------------------------------------------------
>> > 
>> > WISPA Wireless List: wireless@wispa.org
>> > 
>> > Subscribe/Unsubscribe:
>> > http://lists.wispa.org/mailman/listinfo/wireless
>> > 
>> > Archives: http://lists.wispa.org/pipermail/wireless/
>> 
>> 
>> 
>> --------------------------------------------------------------------------------
>> WISPA Wants You! Join today!
>> 
>> http://signup.wispa.org/
>> 
>> --------------------------------------------------------------------------------
>>  
>> WISPA Wireless List: 
>> wireless@wispa.org
>> 
>> 
>> Subscribe/Unsubscribe:
>> 
>> http://lists.wispa.org/mailman/listinfo/wireless
>> 
>> 
>> Archives: 
>> http://lists.wispa.org/pipermail/wireless/
> 
> 
> --------------------------------------------------------------------------------
> WISPA Wants You! Join today!
> http://signup.wispa.org/
> --------------------------------------------------------------------------------
> 
> WISPA Wireless List: wireless@wispa.org
> 
> Subscribe/Unsubscribe:
> http://lists.wispa.org/mailman/listinfo/wireless
> 
> Archives: http://lists.wispa.org/pipermail/wireless/



--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Reply via email to