[arm-allstar] Network Configuration

John wb5nfc at gmail.com
Mon Jul 28 09:10:23 EST 2014 

I aborted the firsttime script, Doug. Bet I don't abort it for the next node I bring up <g>. You may remember that I moved the node from dynamic to static IP. That's when all my 'fun' began. No matter how hard you work to make something 'idiot proof' someone like me will always find a way to break it. 

John

Sent from my iPhone

> On Jul 28, 2014, at 8:48 AM, Doug Crompton <doug at crompton.com> wrote:
> 
> John,
> 
> Great to hear you got that fixed. I am confused why that happened. The firsttime script when you initially boot the image sets up the network. You can bypass it but it is best not to. It does checks on what you enter and makes sure you don't enter something wrong for network settings. If you did use that method to set the network when you made that mistake maybe we need to do some more checking in the script. Did you use that script or edit the file yourself?
> 
> You can rerun that script at any time to change the network settings. It is located at -
> 
> /usr/local/sbin/firsttime.sh
> 
> 73 Doug
> WA3DSP
> http://www.crompton.com/hamradio
> 
> 
> Date: Mon, 28 Jul 2014 05:24:31 -0500
> From: wb5nfc at gmail.com
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Network Configuration
> 
> Gentlemen: it is with elation and trepidation that I write this post.... I'm delighted to have found the problem, but embarrassed to share the cause. Chalk yet another one up to operator error. An ID10T error to be precise. 
> 
> In editing /etc/netctl/eth0, I inadvertently added /24 to my gateway (Gateway= 10.159.66.1/24)
> 
> /24 removed. Problem solved. The boot message errors are still there, but as Doug indicated, they do not seem to matter.  
> 
> Perhaps the hours spent chasing ghosts will be worthwhile if my stupidity can keep others from making the same mistake. 
> Thanks to all for your help. Maybe now I can get a little sleep....
> 
> John
> 
> 
> On Sun, Jul 27, 2014 at 11:53 PM, Doug Crompton <doug at crompton.com> wrote:
> Here is my network boot messages on one of my systems....
> 
> [    9.018101] net eth0: initializing cpsw version 1.12 (0)
> [    9.022485] net eth0: phy found : id is : 0x7c0f1
> [    9.022523] libphy: PHY 4a101000.mdio:01 not found
> [    9.027620] net eth0: phy 4a101000.mdio:01 not found on slave 1
> [    9.101282] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [    9.254230] usbcore: registered new interface driver snd-usb-audio
> [   12.098811] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
> [   12.098876] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> 
> This system is working normally. So as I mentioned the not found messages can be ignored. Does your boot look like this?  Also do an  'ifconfig' and send the output so we can see it.
> 
> 73 Doug
> WA3DSP
> http://www.crompton.com/hamradio
> 
> 
> > Date: Sun, 27 Jul 2014 20:45:48 -0700
> > From: ar at dseven.org
> > To: arm-allstar at hamvoip.org
> > Subject: Re: [arm-allstar] Network Configuration
> 
> > 
> > You don't necessarily need a serial cable - you can see them in
> > `dmesg` (kernel messages). Here's what mine says...
> > 
> > [ 9.907251] net eth0: initializing cpsw version 1.12 (0)
> > [ 9.910123] net eth0: phy found : id is : 0x7c0f1
> > [ 9.910153] libphy: PHY 4a101000.mdio:01 not found
> > [ 9.915279] net eth0: phy 4a101000.mdio:01 not found on slave 1
> > [ 9.956453] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> > [ 11.916167] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
> > [ 11.916242] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> > 
> > If John's not seeing "Link is Up", there may be a physical problem
> > (bad cable, switch, etc.), or maybe some config issue that's causing
> > the NIC to not get initialised....
> > 
> > 73,
> > 
> > ~iain / N6ML
> > 
> > 
> > On Sun, Jul 27, 2014 at 8:32 PM, Doug Crompton <doug at crompton.com> wrote:
> > > John,
> > >
> > > I believe those errors can be safely ignored. I will be hooking up my
> > > serial cable tomorrow and I will check but as I remember I have seen them on
> > > all boots and the network works.
> > >
> > > Can you describe your network issues again? What router, isp, static or
> > > dhcp? Unless you are setting something wrong in the BBB it should work as
> > > it has for everyone else. Perhaps we can sked or talk on the phone. Node
> > > 27225 works for me if you have a node that works.
> > >
> > > 73 Doug
> > > WA3DSP
> > > http://www.crompton.com/hamradio
> > >
> > >
> > > ________________________________
> > > Date: Sun, 27 Jul 2014 21:34:52 -0500
> > > From: wb5nfc at gmail.com
> > > To: arm-allstar at hamvoip.org
> > > Subject: [arm-allstar] Network Configuration
> > >
> > >
> > > I have been struggling with router and basic network setup for several weeks
> > > thinking that I have a major router configuration problem. I finally got
> > > USB-serial communication established with my BBB tonight. The following
> > > (apparent) errors appear at the very end of the boot process:
> > >
> > > [ OK ] Started Automatic wired network connection using netctl profiles.
> > > [ 6.203253] libphy: PHY 4a101000.mdio:01 not found
> > > [ 6.208395] net eth0: phy 4a101000.mdio:01 not found on slave 1
> > >
> > > Arch Linux 3.8.13-24-ARCH (ttyO0)
> > >
> > > bbb2186 login: [ 11.527052] libphy: PHY 4a101000.mdio:01 not found
> > > [ 11.532149] net eth0: phy 4a101000.mdio:01 not found on slave 1
> > >
> > > Arch Linux 3.8.13-24-ARCH (ttyO0)
> > >
> > > bbb2186 login: root
> > > Password: xxxxxxx
> > > BBB Allstar Release Version 1.1 June 25, 2014 WA3DSP
> > >
> > > -------------------------
> > >
> > > What do these error messages mean and how do I correct them?
> > >
> > > Thanks in advance for any guidance you can provide.
> > > --
> > > John Kenney
> > >
> > > _______________________________________________ arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit the BBB
> > > web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
> > >
> > > _______________________________________________
> > >
> > > arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB web page -
> > > http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
> > _______________________________________________
> > 
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > 
> > Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
> > 
> 
> _______________________________________________
> 
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> 
> Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
> 
> 
> 
> -- 
> John Kenney
> 
> _______________________________________________ arm-allstar mailing list arm-allstar at hamvoip.org http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
> _______________________________________________
> 
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> 
> Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20140728/78933702/attachment.html>

More information about the arm-allstar mailing list