[Dnsmasq-discuss] "dhcp-ignore = myTag, #known" was not what I thought

Mariano Absatz el.baby at gmail.com
Sun Dec 7 14:09:10 GMT 2008


Simon Kelley escribió el 06/12/08 19:04:
> Mariano Absatz wrote:
>>
>> 1) does "dhcp-range" allow me to match more than one tag? or to match
>> one (or more) and set another one?
>
>
> It allows you to match more than one,  but they're combined as AND, so
>
> dhcp-range=net:tag1, net:tag2, ......
>
>
> means use that range if tag1 is set AND tag2 is set.
>
> If you want to OR them, just repeat the ranger statement
>
> dhcp-range=net:tag1, 192.168.0.1, 192.168.0.10
> dhcp-range=net:tag2, 192.168.0.1, 192.168.0.10
>
> will use 192.168.0.1-192.168.0.10 of tag1 is set OR tag2 is set.
>
> You can match one (or more) tags, as above, and set a tag too
>
> dhcp-range=net:tag1, net:tag2, newtag, ......
>
> newtag is set when this range is used. There can only be one tag set
> on a range.
>
>>
>> 2) when I write:
>>
>> ############# OUR PCs ##############
>> dhcp-host=00:22:33:44:55:01,192.168.1.101,net:tagIKnowYou,mycompany-PC-01
>>
>> dhcp-host=00:22:33:44:55:02,192.168.1.101,net:tagIKnowYou,mycompany-PC-02
>>
>> dhcp-host=00:22:33:44:55:03,192.168.1.101,net:tagIKnowYou,mycompany-PC-03
>>
>>
>>
>> I am *setting* (and not trying to */match/*) the tag "tagIKnowYou"
>> for these hosts, am I?
> You're setting it.
>
> It's probably worth enumerating all the ways that tags can be set.
>
> 1) The name of the interface on which a DHCP request is recived is set
> as a tag (2.46 and later only)
>
> 2) Tags can be set based on a match of circuit-id, subscriber-id and
> remote-id in an RFC3046 realy agent option.
>
> 3) Tags can be set based on the MAC address with --dhcp-mac
>
> 4) If a dhcp-host line is used (or an implied one derived from
> /etc/ethers) then "known" is set as a tag
>
> 5) If the used config line includes net:<tag> then that is set.
>
> 6) For BOOTP requests ONLY, tag "bootp" is set, and incoming
> "filename" field (which isn't strictly an filename in BOOTP) is used
> as a tag
>
> 7) Tags are set based in the vendor class and user class.
>
> At this point, if any set tags match a dhcp-ignore tag then the
> request is discarded.
>
> Then a dhcp-range is selected, based on the current tag set, available
> IP addresses etc.
>
> 8) Any tag in the DHCP range line is set.
>
> Finally, dhcp-options are added, filtered using the current tag set.
>

Great explanation... I understood everything and re-wrote my
configuration accordingly (anyway, I have to wait till Tuesday to test
it since I'm remote now and tomorrow is a National Holiday here).

I thank you once again for your time and patience.

-- 
Mariano Absatz - "El Baby"
el.baby at gmail.com
www.clueless.com.ar


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
bashian roulette:
[ $(($RANDOM%6)) -eq 0 ] && rm -rf ~
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* TagZilla 0.066 * http://tagzilla.mozdev.org




More information about the Dnsmasq-discuss mailing list