0

First of all I read a lot of thread about problems with connections but all referred to a Wi-Fi LAN adapter. My problem is on the eth0 LAN port.

I have a Raspberry Pi 2 Model B with the latest stable Raspbian installed. I use it as a DHCP server so I configured a static IP. The problem is: after a reboot, the LAN port seems disabled. No ping, ssh or VNC work. But if I connect via real VNC over the cloud I can access the RPi and immediately after connected eth0 starts and i can ping or access ssh.

It seems the LAN port wakes up after an external input.

But after some minutes after disconnect from VNC again the LAN port goes to sleep.

This is my /etc/network/interfaces:

iface eth0 inet static
        address 192.168.3.91
        netmask 255.255.255.0
        broadcast 192.168.3.255
        network 192.168.3.0
        mtu 1500
        gateway 192.168.3.1

And this is my /etc/dhcpcd.conf:

interface eth0
static ip_address=192.168.3.91
static routers=192.168.3.1
static domain_name_servers=208.67.222.222 208.67.220.220
static domain_search=

I tried with

  • auto eth0
  • inet manual (instead static)
  • using a script executed on boot with sudo ifup eth0

but nothing worked...

On boot, the LAN port is not responding to pings.

Aurora0001
  • 6,357
  • 3
  • 25
  • 39
Simone Bissi
  • 1
  • 3

1 Answers1

0

Solved the problem. My RPi was setted up correctly. The real problem was on LAN. There was another linux router with some network services still active that make conflicts with RPi. I supposed i stopped all network services on that machine but i was wrong. Without that machine on LAN, RPi working perfectly. Thanks to all for help.

Simone Bissi
  • 1
  • 3