dhclient sending request to port 67 locking system up

[Xen]

Scott Blair schreef op 06-11-2017 18:24:

> I have been getting the following errors in my syslog file and it is 
> causing my system to hard lock.
> 
> dhclient[1300]: DHCPREQUEST of 192.168.0.108 on enp6s0 to 192.168.0.1 
> port 67 (xid=0x7a4f385)
> dhclient[1300]: send_packet: Operation not permitted
> dhclient[1300]: dhclient.c:2386: Failed to send 300 byte long packet 
> over fallback interface.
> dhclient[1300]: DHCPREQUEST of 192.168.0.108 on enp6s0 to 192.168.0.1 
> port 67 (xid=0x7a4f385)
> dhclient[1300]: send_packet: Operation not permitted

I don't know what the problem is; dhclient only requires an interface to 
be in the "up" state.

It should never really cause a real "lock".

> I opened port 67 in the firewall and that didn't work.

Normal Linux computers come without a firewall configured, so there 
should be no blocking.

> I also tried this :
> 
> $IPTABLES  -I INPUT -i $LAN_IFACE -p udp --dport 67:68 --sport 67:68 -j 
> ACCEPT
> 
> But it comes back -I command not found.

That means $IPTABLES is empty.

iptables -I INPUT -i enp6s0 -p udp --dport 67:68 --sport 67:68 -j ACCEPT

Would do the trick.

> Any Ideas?

Well I don't know what locking up means.

This is also locked up from the console?

Try

ip link set dev enp6s0 up


> If you don't stand behind our troops,
> feel free to stand in front of them.

That is advisable behaviour when they are still at home so they don't go 
to war.