Forums » Software Development »
Networking requires ifup
Added by Joe Bauman over 11 years ago
Starting a new post for this question.
When the MityDSP (L138F) boots up, I am unable to connect via SSH. I have to login through the serial port and run "ifup eth0" first - then everything works just fine.
Occurs using static (bootargs ip=192.168.0.110) or dhcp (bootargs ip=dhcp) and the /etc/network/interfaces adjusted accordingly.
xxxx
auto eth0
iface eth0 inet static
address 192.168.0.110
netmask 255.255.255.0
network 192.168.0.0
gateway 192.168.0.1
xxxx
Strangely, it seems to work fine on our office network (not sure exactly how it is set up), but doesn't work on my home network (through wrt54gl router and optional netgear 5 port switch). Is there something in my simple home network that I am missing?
In response to Jonathan's suggestion, networking is linked in rcS, rc0, and rc6.
Thanks much,
Joe.
Replies (4)
RE: Networking requires ifup - Added by Jonathan Cormier over 11 years ago
Joe,
Looking at the networking startup script, all it does is run ifup -a to bring the interfaces up. Could you try running this command instead or "ifup eth0" and see if the command works? Also watch the kernel messages during boot to see if any errors jump out at you.
-Jonathan
RE: Networking requires ifup - Added by Joe Bauman over 11 years ago
The only thing in the boot log that jumps out at me is:
davinci_mdio davinci_mdio.0: phy[3]: device 0:03, driver unknown
"ifup -a" seems to work just fine when I run it after the system finishing booting.
root@mityomapl138:~# ifup -a davinci_mdio davinci_mdio.0: resetting idled controller net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:03, id=40005201) ADDRCONF(NETDEV_UP): eth0: link is not ready root@mityomapl138:~# PHY: 0:03 - Link is Up - 100/Full ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
The "resetting idled controller" seems to indicate that something has happened to the controller state, but I don't know if that's a normal response.
Joe.
mityboot.txt (16.8 KB) mityboot.txt |
RE: Networking requires ifup - Added by Jonathan Cormier over 11 years ago
The big difference between your boot and mine is:
I have
rw,rootwait ip=dhcp
and you have
rw,rootwait,ip=192.168.0.110
RE: Networking requires ifup - Added by Joe Bauman over 11 years ago
Bingo. Good catch. I didn't look close enough at the comma/space separators.
Thanks for your help!
Joe.