Requesting help with Eth0 issue on Raspbian Jessie

Hi Phillip,

You have an IP address assigned for eth0 above. I take it this is not a valid IP for your work network as you mention it working via dhcp and assigning an IP address for the wireless? If this is the case, take a look at /etc/dhcpcd.conf and see how that's configured. Is it set up to give you a static IP address for your home network?

Best Regards,

Rachael

I took a look into my /etc/dhcpcd.conf and this is what I get:

# 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

 

 

# 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.

#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.

# Some interface drivers reset when changing the MTU so disabled by default.

#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

 

 

# A hook script is provided to lookup the hostname if not set by the DHCP

# server, but it should not be run by default.

nohook lookup-hostname

I'm not exactly sure what it is that could be out of place here.

Hi Phillip,

*** UPDATE: Subsequent information in a post below leads me to think this isn't now relevant as it appears to be getting an IP address from DHCP in the correct range ***

I've not seen this issue on my Pi and to be honest haven't used it for a while so I am not 100% sure what I am about to suggest is going to work. However it should be easily reversible if you make backups for files before changing them. Basically my idea is to stop dhcpcd from being involved in eth0 and set up eth0 in /etc/network/interfaces to do dhcp in the normal way. But I am not sure if something else is going on in your configuration as you currently have an IP address on eth0 and I am not sure where this has come from.

In your /etc/dhcpcd.conf file add the following line:

denyinterfaces eth0

In your /etc/network/interfaces file change the eth0 section to look like the following:

auto eth0
iface eth0 inet dhcp

Best Regards,

Rachael

Hi Phillip,

*** UPDATE: Subsequent information in a post below leads me to think this isn't now relevant as it appears to be getting an IP address from DHCP in the correct range ***

I've not seen this issue on my Pi and to be honest haven't used it for a while so I am not 100% sure what I am about to suggest is going to work. However it should be easily reversible if you make backups for files before changing them. Basically my idea is to stop dhcpcd from being involved in eth0 and set up eth0 in /etc/network/interfaces to do dhcp in the normal way. But I am not sure if something else is going on in your configuration as you currently have an IP address on eth0 and I am not sure where this has come from.

In your /etc/dhcpcd.conf file add the following line:

denyinterfaces eth0

In your /etc/network/interfaces file change the eth0 section to look like the following:

auto eth0
iface eth0 inet dhcp

Best Regards,

Rachael