dhcpcd: Update to 6.9.3 - with or without '10-mtu'?

dhcpcd: Update to 6.9.3 - with or without '10-mtu'?

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

Hi list,

I'd like to have a small problem, so I'm asking here before something 
goes bork...: ;-)

I found this update for 'dhcpcd' to 6.9.3. So I decided to test it. 
Building was ok, but I'm not sure if the result would fit into our 
current IPFire builds.

First, I had to disable a 'sed'-line in lfs-file, the file '10-mtu' is 
no longer included:

...
sed -i -e "s|-ge 576|-gt 576|g" $(CONFIG_ROOT)/dhcpc/dhcpcd-hooks/10-mtu
...

This is intentional by the programmer, source says in 
'/dhcpcd-hooks/Makefile':

...
	# We need to remove the old MTU change script if we at all can.
	rm -f ${DESTDIR}${SCRIPTSDIR}/10-mtu
...

Accordingly, building stopped with a file-not-found error. After 
commenting the 'sed'-line, everything went ok, but 
'/var/ipfire/dhcpc/dhcpcd-hooks/10-mtu' is now missing.

My questions:

Do we really need this missing '10-mtu' file?
Sorry if this is a dumb question, but I'm just not sure about the 
relationsships.

Is a complete reboot required during an eventual upgrade? Or would it be 
sufficient to disconnect / connect / reboot network, whatever...?

Thanks for any hints!

Regards
Matthias

Re: dhcpcd: Update to 6.9.3 - with or without '10-mtu'?

[Arne Fitzenreiter]

[-- Attachment #1: Type: text/plain, Size: 429 bytes --]

On 2015-10-09 15:31, Matthias Fischer wrote:
> Hi list,
> 
> I'd like to have a small problem, so I'm asking here before something
> goes bork...: ;-)

The 10-mtu file take the mtu from the dhcp server and apply it the the 
client. The sed is a work-around for cable modems that try to set a too 
small mtu. (768)

I think we need to test this at cable user or check the mtu settings in 
the new version first.

Greetings,
Arne