Hello,
Joan Lledó, on lun. 11 sept. 2017 19:30:07 +0200, wrote:
> > It looks odd not to specify explicitly -a 0.0.0.0, can't we do that?
>
> Yes, "-a" is equivalent to "-a 0.0.0.0 -m 255.0.0.0". Both options are good.
Ok, it just always look odd to me that an option either takes a
parameter or n
>
> It looks odd not to specify explicitly -a 0.0.0.0, can't we do that?
Yes, "-a" is equivalent to "-a 0.0.0.0 -m 255.0.0.0". Both options are good.
> Otherwise it looks good to me, please submit a patch to the
> corresponding upstream & Debian maintainers :)
I'm a bit lost here. Is it enough t
Hello,
Joan Lledó, on lun. 11 sept. 2017 12:59:34 +0200, wrote:
> To avoid applying the patch, I suggest to replace the PREINIT command for
> this:
> fsysopts /servers/socket/2 -i ${interface} -a
>
> The "-a" option sets the address to 0.0.0.0, which works fine for both
> pfinet and lwip.
It lo
Hello,
In my tests on the lwip translator, I've observed that the DHCP client
sets the interface address to 255.255.255.255 before sending the
DHCPDISCOVER messages. I found the source of this behaviour in the
dhclient-script[1].
The script executes "fsysopts /servers/socket/2 -i $
Hi,
Here is some quick and fast hack for pfinet to make dhcp work. I've
added an option "-d" or "--dhcp" to pfinet to make it prepare for
dhcp.
When using this it sets the ip to 1.1.1.1, netmask to 255.0.0.0 and
adds a route like is done for GNU/Linux to be able to send broadcasts
for dhcp.
Perh
