Hi;
I've read a little in the extensive shorewall documentation and think it's a
special, though maybe not uncommon use case.
I think we do not need to change dhcpcd defaults (yet).
IMHO it's up to Timothy to either live with the drawbacks Andrew outlined or
to look for a proper solution, whic
Hi.
Practical purpose for 'background' option - this is:
1) dhcpcd will not die if no carrier on WAN during boot
2) boot speedup when something is wrong in network (no lease obtained).
IMHO we need to do something with shorewall - rules should be updated
(at least partially) when new lease is obt
My Shorewall problem is solved for practical purposes, but now I am curious :-)
So what is the dhcpcd configuration option "background" good for? The
documentation says:
background
Background immediately. This is useful for startup scripts which
don't disable link messa
Hi
Am 20.01.2015 um 17:30 schrieb Timothy Wegner:
> Hi kp,
>
> You were exactly right! As you suggested I commented out the bottom
> line of /etc/dhcpcd.conf:
>
> #background
>
> and then shorewall started OK.
My 0.02€ (can't use swiss francs anymore, too expensive)
It cannot be the resposib
Hi kp,
You were exactly right! As you suggested I commented out the bottom
line of /etc/dhcpcd.conf:
#background
and then shorewall started OK.
Thanks!
Tim
On Tue, Jan 20, 2015 at 9:46 AM, kp kirchdoerfer
wrote:
> Am Montag, 19. Januar 2015, 18:56:00 schrieb Timothy Wegner:
>> I have encoun
Am Montag, 19. Januar 2015, 18:56:00 schrieb Timothy Wegner:
> I have encountered a small Shorewall issue after upgrading from
> Bering-uClibc_5.1.3-beta1 to 5.1.3-rc1. I'm using my Bering Soekris
> box as a firewall/router that gets it's IP from Comcast via DHCP. I am
> running the Bering-uClibc_5
I have encountered a small Shorewall issue after upgrading from
Bering-uClibc_5.1.3-beta1 to 5.1.3-rc1. I'm using my Bering Soekris
box as a firewall/router that gets it's IP from Comcast via DHCP. I am
running the Bering-uClibc_5.1.3-rc1_x86_64_syslinux_vga.tar.gz version
modified to use the seria