I appreciate all the help. I have learned some things but the
shorewall/dhcpd "problem" is vanishing before my eyes.
1. the dhcpd boot messages are a red herring. Yes dhcpd has changed
slightly, but I now see that the boot message order has changed - there
aren't missing messages, I just didn't
HI Timothy;
Am Freitag, 3. Juni 2016, 18:58:09 schrieb Timothy Wegner:
> I have a LEAF router on a Soekris box.
>
> LEAF Bering-uClibc 5.2.6-rc1 works perfectly. But 5.2.6 does not. Shorewall
> complains that it can't get an ip and won't start, and the boot messages
> just before shorewall runs
Tom, sorry for the confusion, the 5.2.6 version numbers in my post are for
Bering-uClibc, not Shorewall. I was comparing Bering-uClibc 5.2.6rc1
(release candidate 1) with Bering-uClibc 5.2.6 release version. I believe
that the Shorewall version is the same in both (4.6.13.4) so I think we can
On 6/3/2016 4:58 PM, Timothy Wegner wrote:
> I have a LEAF router on a Soekris box.
>
> LEAF Bering-uClibc 5.2.6-rc1 works perfectly. But 5.2.6 does not. Shorewall
> complains that it can't get an ip and won't start, and the boot messages
> just before shorewall runs indicate that an ipv6 ip was
I have a LEAF router on a Soekris box.
LEAF Bering-uClibc 5.2.6-rc1 works perfectly. But 5.2.6 does not. Shorewall
complains that it can't get an ip and won't start, and the boot messages
just before shorewall runs indicate that an ipv6 ip was obtained but not
ipv4. After boot, the ip addr show
