[Dnsmasq-discuss] Incorrect broadcast address given
ob.lutz at gmail.com
Tue Oct 14 14:18:55 BST 2008
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.8.224 * 255.255.255.224 U 0 0 0 br-lan
126.96.36.199 * 240.0.0.0 U 0 0 0 bmf0
# ip route show
192.168.8.224/27 dev br-lan proto kernel scope link src 192.168.8.225
188.8.131.52/4 dev bmf0 scope link
Nothing crazy going on there.
Yes, manually specifying it works.
On Tue, Oct 14, 2008 at 9:16 AM, Simon Kelley <simon at thekelleys.org.uk> wrote:
> OB Lutz wrote:
>> I'll get that output tomorrow. When multiple routers are in the
>> network, there will be routes to other sets of ips, like
>> 184.108.40.206/27 going out the wireless (ath0), but theres never another
>> route to 192.168.8.224/27. A default route is only present when
>> another router is setup as an internet gateway. This output was from a
>> router isolated from the rest of the mesh network (it was on a
>> different wireless channel). The problem exists both when the router
>> is alone or when its talking to its brethren, so I chose the isolated
>> version to make everything as simple as possible.
> I'm not very keen on touching the relevant code in dnsmasq to make it work
> in this case: getting "always correct" behaviour would be difficult and my
> gut says there's a risk of nasty regressions on existing, working systems.
> My understanding is that the workaround of manually specifying the broadcast
> address works, is that true? If so, I'd probably be inclined to add this to
> the set of cases where the broadcast address must be given. (That's already
> the case for using relays, for instance.)
More information about the Dnsmasq-discuss