search

XSCE / xsce

xsce code base
Other
32 stars 32 forks source link

move br0 to interfaces, disable resolvconf #913

Closed georgejhunt closed 7 years ago

georgejhunt commented 7 years ago

testing to date: applied to Josh's pixel and pixel-lite images. results: pixel: reboot went from 3:02 to 0:44 lite: reboot went from 3:55 to 0:31 without ethernet: pixel reboots in 0:31 "box" and "box.lan" still resolve on attached client

No testing on other-than-rpi

tim-moody commented 7 years ago

for gateway you changed eth0 from dhcp to manual. are you sure you get an ip address when it is connected?

georgejhunt commented 7 years ago

That seems to be the whole function of dhcpcd. But specifying manual, the networking.service is instructed to let dhcpcd do it.

On Sat, May 13, 2017 at 6:23 AM, Tim Moody notifications@github.com wrote:

for gateway you changed eth0 from dhcp to manual. are you sure you get an ip address when it is connected?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/XSCE/xsce/pull/913#issuecomment-301248063, or mute the thread https://github.com/notifications/unsubscribe-auth/AB04HIWQeOEtTJi7GZRw3q4jMLFaa8Zxks5r5a7OgaJpZM4NaD-k .

jvonau commented 7 years ago

Please remove the now unused template files. Should the APPLIANCE section receive the same treatment? Sounds more like a race for control of the network card. Something is not quite right, network.service using dhcp in the interface file should call a dhcp client daemon without manually enabling the dhcpdcd service. If the dhcpcd.service is enabled and has been started before network.service then there will be a stall while network.service is trying to enable and the take control of the card then can't. Same holds true during shutdown. Have a closer look at the logs.

jvonau commented 7 years ago

There is a typo in rpi_debian.yml also: "command: ifdown etho"