On Mon, Oct 9, 2017 at 12:00 AM, Nerijus Baliunas <neri...@users.sourceforge.net> wrote: > On Sun, 8 Oct 2017 23:44:58 +0300 Sergey Ryazanov <ryazanov....@gmail.com> > wrote: >> > I assigned IP with a command >> > ip a a 192.168.0.10/24 dev eth0 >> > >> > but ping from PC does not answer. >> >> Have you bring eth0 UP? I mean, could you do "ifconfig eth0 >> 192.168.0.10 up" and try pinging again? > > Just tried: > # ifconfig eth0 192.168.0.10 up > ifconfig: SIOCSIFFLAGS: Out of memory > # dmesg|grep eth > [ 0.998445] eth0: MII PHY 32 on NPE-B > [ 1.005134] eth1: MII PHY 1 on NPE-C > [ 6.540687] eth0: link up, speed 100 Mb/s, full duplex > [ 9.323993] eth0: link down > [ 36.266247] device eth0 entered promiscuous mode
Check please, is there any new kernel messages after 'ifconfig ... up' failure (may be not directly related to eth0). Just run dmesg without grep. It is also stranger that something bring eth0 up and then putting it back to down. Is these strings (eth0: link up/eth0: link down) appear in the kernel log during preinit procedure? -- Sergey _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
