[Dnsmasq-discuss] Test release with tag-if support.

[Simon Kelley]

Ignacio.Bravo at belden.com wrote:
>  Hello Simon, I tried the following on 2.53-test8:
> 
> tag-if= set:fixedport, tag:puerto3, tag:switch1
> dhcp-range=net:switch1,net:puerto3,10.10.35.2,10.10.35.5,255.255.255.0
> #dhcp-option=net:switch1,net:puerto3,54,10.10.35.251
> dhcp-circuitid=puerto3,b9:06:00:00:01:01:01:03
> dhcp-remoteid=switch1,00:06:00:80:63:60:e1:64
> 
> 
> dhcp-range=net:#fixedport,10.10.35.40,10.10.35.50,255.255.255.0
> dhcp-option=net:#fixedport,option:router,10.10.35.100
> dhcp-option=net:#fixedport,option:dns-server,8.8.8.8
> #dhcp-option=net:#fixedport,54,10.10.35.251
> 
> Tag-if works ok in this example. I get 10.10.35.5 when at port3 and 
> 10.10.35.41 at any other B^)
> 
> Now, if I get 10.10.35.5 at port3 and then connect my pc to port1, my IP 
> is still .5 (no renewal yet). If I try a ipconfig/renew (force the unicast 
> renewal), I get an ACK for 10.10.35.5 instead of a proposal 10.10.35.41

Yes, that's expected. The tags are now ignored for unicast renewals, to
make them work even though the packets aren't modified by the switch.
Try ipconfig /release first, to release the current address, then /renew
to get a new one.

> 
> I tried the dhcp-server-identifier:
> dhcp-option=net:switch1,net:puerto3,54,10.10.35.251
> dhcp-option=net:#fixedport,54,10.10.35.251
> But no success (request is directly sent to the server ip instead of 
> relay's)
> Maybe these two lines are not ok or I should activate any other option 
> instead
They won't work, option 54 cannot be altered like that.

Cheers,

Simon.