> The netmask problem needs fixing before we can say that this approach
> won't work, I think.
Thanks for the hint. We fixed this now, but still did not manage to get the
desired behavior (see log). It seems that dnsmasq only uses the most recently
assigned ip address of an interface for context
Benjamin Collar wrote:
Greetings
Thank you for the previous information. We're still working on it and
have come to the following. (The following was forwarded to me by the
colleague who actually performed the work, so it's written from his
POV...). Any other tips/leads you could give us would b
CPACK(eth1) 10.128.150.35 00:10:5a:5a:05:e2 INT1_IOD_MB_EXT0_SLV
Am Donnerstag, 21. Juli 2005 17:35 schrieb Benjamin Collar:
> Forwarded Message
> From: Simon Kelley
> To: Benjamin Collar
> Cc: dnsmasq-disc...@thekelleys.org.uk
> Subject: Re: [Dnsmasq-discuss] a
Benjamin Collar wrote:
Greetings
We have set up two interfaces that are physically connected to the same
network:
eth0: 10.0.150.10 netmask 255.254.0.0
eth1: 10.128.150.10 netmask 255.254.0.0
dnsmasq is configured to only statically assign IP addresses via
the client id. Excerpt from dnsmasq.
Greetings
We have set up two interfaces that are physically connected to the same
network:
eth0: 10.0.150.10 netmask 255.254.0.0
eth1: 10.128.150.10 netmask 255.254.0.0
dnsmasq is configured to only statically assign IP addresses via
the client id. Excerpt from dnsmasq.conf:
dhcp-host:id=Linda,1
