dhcpcd-discuss

Re: IPv4LL address not fetched when powering up from PoE injector

shreesha vitthala

Fri Jan 20 06:19:15 2017

*# ps ax|grep dhcpcd*
  434 root     */sbin/dhcpcd eth0*
  459 root     grep dhcpcd

*# cat /etc/dhcpcd.conf *
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

*nolink*

# Use the hardware address of the interface for the Client ID.
clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per
RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
#duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
#option ntp_servers
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu

# A ServerID is required by RFC2131.
#require dhcp_server_identifier

# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private

nodhcp6
noipv6
noipv6rs
waitip 4
#


On Fri, Jan 20, 2017 at 6:09 AM, Roy Marples <roy@xxxxxxxxxxxx> wrote:

> Hi
>
> On 18/01/2017 12:02, shreesha vitthala wrote:
>
>> I connect my PoE powered device to PoE injector's Data+Power port. The
>> injector model is Ault Inc.'s PW130.
>> On boot dhcpcd fails to fetch an 169.254.x.x IP address.
>> However it works fine when powered up from a PoE switch (TP LINK
>> TL-SF1008P).
>>
>> dhcpcd version is 6.11.5
>>
>> Below is the output:
>>
>> eth0: waiting for carrier
>> timed out
>> dhcpcd exited
>>
>> cat /sys/class/net/eth0/carrier outputs 0.
>>
>> However when I pass -K or --nolink option to dhcpcd it issues an IP.
>> Also I no longer see the "eth0: waiting for carrier" message.
>>
>
> This is expected given all of the above.
>
> Next I tried putting nolink option in dhcpcd.conf but I observed that it
>> no longer fetches a dhcp address when powered from the PoE switch
>> connected to a dhcp server.
>> It instead fetches a link local address. Following is the log:
>>
>> read_lease: dhcp_read_lease_fd: Success
>> eth0: soliciting a DHCP lease
>> macb f802c000.ethernet eth0: link up (100/Full)
>> eth0: probing for an IPv4LL address
>> eth0: using IPv4LL address 169.254.113.49
>> eth0: adding route to 169.254.0.0/16 <http://169.254.0.0/16>
>> eth0: adding default route
>> forked to background, child pid 434
>>
>> So how should I configure dhcpcd to be able to work with PoE injector
>> also?
>>
>
> That is not expected.
> Please post your dhcpcd.conf and and ouput of
> ps ax | grep dhcpcd
> with the above running, so I can see command line arguments passed.
>
> Roy
>

Follow-Ups:
Re: IPv4LL address not fetched when powering up from PoE injectorshreesha vitthala
References:
IPv4LL address not fetched when powering up from PoE injectorshreesha vitthala
Re: IPv4LL address not fetched when powering up from PoE injectorRoy Marples
Archive administrator: postmaster@marples.name