Hallo, Matthias,
Du meintest am 17.12.14:
I have a setup in which the DHCP range is 192.168.2.128 to
192.168.2.250, and I manually give some devices an IP in range
192.168.2.1 to 192.168.2.127, using the dhcp-host line. So that I
can use the u32 traffic classifier to split traffic streams.
Am 17.12.2014 um 09:38 schrieb Helmut Hullen:
Hallo, Matthias,
Du meintest am 17.12.14:
I don't know one, but it should be in the interface address ranges
that dnsmasq is responsible for.
Sure?
On my machines I define the dhcp-host IP-addresses outside the dhcp-
range, and that works
Am 16.12.2014 um 06:54 schrieb 五月:
Greetings,
I have a setup in which the DHCP range is 192.168.2.128 to
192.168.2.250, and I manually give some devices an IP in range
192.168.2.1 to 192.168.2.127, using the dhcp-host line. So that I can
use the u32 traffic classifier to split traffic
*ex:
dhcp-host=00:0c:29:ea:0d:a3,192.168.1.199*
(so dhcp-host=MAC_ADDRESS,STATIC_IP )
That MAC address will always be given the same, explicit IP Address
(which should be in the DHCP Range that dnsmasq is responsible for).
-AJ
On 12/15/2014 1:37 PM, Chris Green wrote:
As per the subject,
On Mon, Dec 15, 2014 at 02:07:46PM -0500, AJ Weber wrote:
ex:
dhcp-host=00:0c:29:ea:0d:a3,192.168.1.199
(so dhcp-host=MAC_ADDRESS,STATIC_IP )
That MAC address will always be given the same, explicit IP Address
(which should be in the DHCP Range that dnsmasq is responsible for).
Greetings,
I have a setup in which the DHCP range is 192.168.2.128 to 192.168.2.250, and I
manually give some devices an IP in range 192.168.2.1 to 192.168.2.127, using
the dhcp-host line. So that I can use the u32 traffic classifier to split
traffic streams.It looks working well. Is there some
