dhcpd problems since last update

This forum is for discussion about general software issues.

Re: dhcpd problems since last update

Postby slackit2 » Wed Dec 28, 2016 7:35 pm

thats the second part, unfortunately i posted too much ;)
$this->bbcode_second_pass_code('', '
Dec 28 20:06:15 alarm systemd-networkd[3144]: lan3: Joined netdev
Dec 28 20:06:15 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_37 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=51 reply_cookie=0 error
Dec 28 20:06:15 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_37 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=52 reply_cookie=0 error
Dec 28 20:06:15 alarm systemd-networkd[3144]: lan3: Configured
Dec 28 20:06:15 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_37 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=53 reply_cookie=0 error
Dec 28 20:06:15 alarm systemd-networkd[3144]: lan4: Joined netdev
Dec 28 20:06:15 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_36 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=54 reply_cookie=0 error
Dec 28 20:06:15 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_36 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=55 reply_cookie=0 error
Dec 28 20:06:15 alarm systemd-networkd[3144]: lan4: Configured
Dec 28 20:06:15 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_36 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=56 reply_cookie=0 error
Dec 28 20:06:15 alarm systemd-networkd[3144]: lan5: Joined netdev
Dec 28 20:06:15 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_35 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=57 reply_cookie=0 error
Dec 28 20:06:15 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_35 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=58 reply_cookie=0 error
Dec 28 20:06:15 alarm systemd-networkd[3144]: lan5: Configured
Dec 28 20:06:15 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_35 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=59 reply_cookie=0 error
Dec 28 20:06:15 alarm systemd-networkd[3144]: eth2: Joined netdev
Dec 28 20:06:15 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_34 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=60 reply_cookie=0 error
Dec 28 20:06:15 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_34 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=61 reply_cookie=0 error
Dec 28 20:06:15 alarm systemd-networkd[3144]: eth2: Updating address: 172.22.30.39/17 (valid for 12h)
Dec 28 20:06:15 alarm systemd-networkd[3144]: eth0: Addresses set
Dec 28 20:06:15 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=62 reply_cookie=0 error
Dec 28 20:06:15 alarm systemd-networkd[3144]: eth0: Configured
Dec 28 20:06:15 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=63 reply_cookie=0 error
Dec 28 20:06:15 alarm systemd-networkd[3144]: lan1: Set link
Dec 28 20:06:15 alarm systemd-networkd[3144]: lan2: Set link
Dec 28 20:06:15 alarm systemd-networkd[3144]: lan3: Set link
Dec 28 20:06:15 alarm systemd-networkd[3144]: lan4: Set link
Dec 28 20:06:15 alarm systemd-networkd[3144]: lan5: Set link
Dec 28 20:06:15 alarm systemd-networkd[3144]: eth2: Configured
Dec 28 20:06:15 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_34 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=64 reply_cookie=0 error
Dec 28 20:06:15 alarm systemd-networkd[3144]: Got message type=signal sender=org.freedesktop.DBus destination=:1.11 object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 error=n/a
Dec 28 20:06:15 alarm systemd-networkd[3144]: Got message type=signal sender=org.freedesktop.DBus destination=:1.11 object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=4 reply_cookie=0 error=n/a
Dec 28 20:06:15 alarm systemd-networkd[3144]: Got message type=error sender=:1.12 destination=:1.11 object=n/a interface=n/a member=n/a cookie=5 reply_cookie=37 error=The name org.freedesktop.PolicyKit1 was not provided by any .service f
Dec 28 20:06:15 alarm systemd-networkd[3144]: eth2: Could not set hostname: The name org.freedesktop.PolicyKit1 was not provided by any .service files
Dec 28 20:06:17 alarm systemd-networkd[3144]: DHCP CLIENT (0xb3d4d713): DISCOVER
Dec 28 20:06:18 alarm systemd-networkd[3144]: DHCP CLIENT (0xb3d4d713): DISCOVER
Dec 28 20:06:23 alarm systemd-networkd[3144]: DHCP CLIENT (0xb3d4d713): DISCOVER
Dec 28 20:06:30 alarm systemd-networkd[3144]: DHCP CLIENT (0xb3d4d713): DISCOVER
Dec 28 20:06:47 alarm systemd-networkd[3144]: DHCP CLIENT (0xb3d4d713): DISCOVER
Dec 28 20:07:19 alarm systemd-networkd[3144]: DHCP CLIENT (0xb3d4d713): DISCOVER
Dec 28 20:08:24 alarm systemd-networkd[3144]: DHCP CLIENT (0xb3d4d713): DISCOVER
Dec 28 20:09:28 alarm systemd-networkd[3144]: DHCP CLIENT (0xb3d4d713): DISCOVER
Dec 28 20:09:53 alarm systemd-networkd[3144]: eth2.132: Adding address: 83.xxx.x.xxx/24 (valid forever)
Dec 28 20:09:53 alarm systemd-networkd[3144]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/network1/link/_311 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=65 reply_cookie=0 erro
Dec 28 20:10:31 alarm systemd-networkd[3144]: DHCP CLIENT (0xb3d4d713): DISCOVER
Dec 28 20:11:05 alarm systemd[1]: Stopping Network Service...
Dec 28 20:11:05 alarm systemd-networkd[3144]: DHCP CLIENT (0x7013b7c2): FREE
Dec 28 20:11:05 alarm systemd-networkd[3144]: DHCP CLIENT (0xb3d4d713): FREE
Dec 28 20:11:05 alarm systemd[1]: Stopped Network Service.
')
slackit2
 
Posts: 15
Joined: Sat Dec 24, 2016 10:08 pm

Re: dhcpd problems since last update

Postby slackit2 » Wed Dec 28, 2016 11:34 pm

Maybe i should write a big tutorial how to setup the clearfog as router ... so much i already learned.
So, i switched from the systemd DHCP client to the dhcpcd package which is shipped by arch linux.
The good news: i get an ip address now for eth2.132 on boot. The bad news is: i have to configure the gateway myself, thats bad.

I have to login and do:
route add default gw 83.xxx.7.1 eth2.132

Can someone please tell me how i can configure dhcpcd.conf to add this information without creating custom post-dhcpcd hooks? Is there a simpler way in the config or am i forced to use the hook scripts?
slackit2
 
Posts: 15
Joined: Sat Dec 24, 2016 10:08 pm

Re: dhcpd problems since last update

Postby fmotsch » Wed Jan 25, 2017 7:30 pm

I wouldn't use dhcpcd at all except for the initial setup until NetworkManager is installed.
systemctl stop dhcpcd
systemctl disable dhcpcd
pacman -S networkmanager
systemctl enable NetworkManager
systemctl status NetworkManager

Update : OK, I read you actually want to create a dhcp-server.
In that case the above doesn't apply. But if your device should
act as client (to obtain it's IP-Address by a server - mostly router)
then the above is much more painless. There are command line
interfaces and environments like Gnome that have also support for
NetworkManager. It can act as dhcp-client.
fmotsch
 
Posts: 1
Joined: Wed Jan 25, 2017 7:14 pm

Re: dhcpd problems since last update

Postby slackit2 » Wed Jan 25, 2017 8:19 pm

This is for a clearfog pro which acts as a router. Of course i need to get the IP from my ISP by a dhcp client. I dont care which one, as long as it works.

$this->bbcode_second_pass_quote('', 'I') wouldn't use dhcpcd at all except for the initial setup until NetworkManager is installed.

why? dhcpcd at least was able to get a request on my vlan for ftth (on the sfp module) with correct routing informations.
why should i use networkmanager? how should networkmanager fix my problem with timing out (dhcpD) on wlp2s0?
slackit2
 
Posts: 15
Joined: Sat Dec 24, 2016 10:08 pm

Previous

Return to General

Who is online

Users browsing this forum: No registered users and 9 guests