<div dir="ltr">Most interesting, Doug. I completely missed the message you posted to the list. The ONLY thing I did was to try the <span style="font-size:12.8px">wifi-menu -o command after running the first time setup script. I found the command in the 'How To Notes' section. I noticed that the 'Wireless How To' covered only the BBB, but thought I'd give the command a try anyway. That's why I was pleasantly surprised when it seemed to work. The new node logged in to my wifi router via Wifi, I could ping Google from the node, and my new node was listed on Allstar. </span><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">I'm out of play time today, but I'll fire up the Pi3 Wifi using your notes tomorrow. First, I'll boot with the existing setup just to see what happens before I make any changes. </span><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">J. </span></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 21, 2016 at 3:40 PM, Doug Crompton via arm-allstar <span dir="ltr"><<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr"><font color="#000000" face="Tahoma,sans-serif">John,<br><br> What are you using to get wifi running - this was my message to the list. You need to get this package.<br></font><br>A Hamvoip package for utilizing wireless on the RPi3 is now available. This package <b>ONLY</b>
works on the RPi3 and with the current RPi2-3 1.02beta download on the
<a href="http://hamvoip.org" target="_blank">hamvoip.org</a> website. So far tests show that wireless on the Pi3 works
very well and has good range. The recommendation at this point is to get
an RPi3 if you want to use wireless or use the IOgear or equivalent
adapter as describe in the wireless howto on the Pi2 or BBB. The
wireless howto will be updated soon to include the RPi3. For now all the
instructions you need are below....<br><br>If you would like to try wireless on the RPi3 download this package to your RPi3<br><br>Web download -<br><br>
<a href="https://hamvoip.org/downloads/hamvoip-wireless-config-0.1-6.pkg.tar.xz" target="_blank">https://hamvoip.org/downloads/hamvoip-wireless-config-0.1-6.pkg.tar.xz</a><br><br>Or on your Pi3 go to the the root directory <br><br>cd <br><br>then<br><br>wget <a href="https://hamvoip.org/downloads/hamvoip-wireless-config-0.1-6.pkg.tar.xz" target="_blank">https://hamvoip.org/downloads/hamvoip-wireless-config-0.1-6.pkg.tar.xz</a><br><br>Then install the package with the following command<br><br>pacman -U --force hamvoip-wireless-config-0.1.6.pkg.tar.xz"<div dir="ltr"><div><br></div><div>when done, execute:</div><div><br></div><div>wireless-setup.sh</div><div><br></div><div>Select
your wireless access point and give the passphrase. It will then give
you further instructions and ask you to disconnect the wired connection.
When the system is rebooted it will be using the wireless connection.<br><br>Note
that the wireless connection will be a new local IP address. You should
hear this in your radio if you had everything setup in the wired mode
previously. You could also get this IP address from your router or by
reading the CW from the LED on the board. <br><br>While port forwarding
is not necessary especially in mobile nodes if you don't have it enabled
you will only be able to connect outbound. To setup port forwarding
first make the assigned wireless IP address permanent in your router.
Every router does this differently but most all have the capability
based on the Pi boards MAC address to come up on the same IP every time
it is booted. Once you have that setup if you desire port forwarding you
can set that up pointing to the permanently assigned wireless IP
address.<br></div><div><br></div><div>There is a "wireless-control.sh" script to enable and disable the wifi interface as well as showing status.</div><div><br>Example screen for selecting wireless access point -<br><br></div></div><span dir="ltr"></span><span></span><div><blockquote style="border-left:1px #ccc solid;padding-left:1ex"><div><div dir="ltr"><span></span><div><div><div><div><div><blockquote style="border-left:1px #ccc solid;padding-left:1ex"><div><div dir="ltr"><div><div><div><div dir="ltr"><br><div><img alt="Inline image 1" height="298" width="425"><br></div><div><br></div></div><div><br></div></div></div></div></div></div></blockquote></div></div></div></div></div></div></div></blockquote></div><br><br><br><b><font style="font-size:16pt" size="4">73 Doug</font><font style="font-size:16pt" size="4"><br></font><font style="font-size:16pt" size="4">WA3DSP</font><font style="font-size:16pt" size="4"><br></font><font style="font-size:16pt" size="4"><a href="http://www.crompton.com/hamradio" target="_blank">http://www.crompton.com/hamradio</a></font></b><font style="font-size:16pt" size="4"><br></font><br><br><div><hr>Date: Thu, 21 Apr 2016 14:50:53 -0500<br>To: <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>Subject: Re: [arm-allstar] RPi2-3 V1.02beta - Initial Setup - CRDA Error<br>From: <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>CC: <a href="mailto:wb5nfc@gmail.com" target="_blank">wb5nfc@gmail.com</a><br><br><div dir="ltr">Perhaps I spoke too soon. The Pi3 disconnected from the wireless network after a few minutes. Ran <span style="font-size:12.8px">wifi-menu -o again, and after reboot, it seems to be working again. Is there a value I'm missing to ensure that the wifi configuration is written to the Pi?</span><div><br></div><div>J. </div></div><div><br><div>On Thu, Apr 21, 2016 at 2:29 PM, Doug Crompton via arm-allstar <span dir="ltr"><<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>></span> wrote:<br><blockquote style="border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr"><font color="#000000" face="Tahoma,sans-serif">John,<br><br> Thanks for the input. I am glad it is working well for you.<br><br>The CDRA message is a missing module that we will correct. Long story short wifi has different rules in different countries about what frequencies can be used and this is a method to enforce that. It will, as you experienced, timeout after about 8 tries. So ignore it for now.<br></font><br><b><font style="font-size:16pt" size="4">73 Doug</font><font style="font-size:16pt" size="4"><br></font><font style="font-size:16pt" size="4">WA3DSP</font><font style="font-size:16pt" size="4"><br></font><font style="font-size:16pt" size="4"><a href="http://www.crompton.com/hamradio" target="_blank">http://www.crompton.com/hamradio</a></font></b><font style="font-size:16pt" size="4"><br></font><br><br><div><hr>Date: Thu, 21 Apr 2016 13:23:57 -0500<br>To: <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>Subject: [arm-allstar] RPi2-3 V1.02beta - Initial Setup - CRDA Error<br>From: <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>CC: <a href="mailto:wb5nfc@gmail.com" target="_blank">wb5nfc@gmail.com</a><br><br><div dir="ltr">My RPi3 came in today. Initial configuration went well - except for one recurring error message: "Calling CRDA to update world regulatory domain." Attempts time out after about 8 tries. The remainder of the setup went well after getting past the "CRDA" error. <div><br></div><div>Even Wifi configuration was a snap. Issued a wifi-menu -o at the prompt, it scanned for available connections and logged in without error after selecting my device and entering the password (That was easy...). <div><br></div><div>Lots of little things to set properly including audio levels, but I just wanted to provide some initial feedback and say, "well done" to the team. Thanks for making life simpler for those of us who couldn't do it without your forethought and efforts. Thank you!</div><div><br></div><div>John / WB5NFC</div></div></div>
<br>_______________________________________________
arm-allstar mailing list
<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>
Visit the BBB and RPi2 web page - <a href="http://hamvoip.org" target="_blank">http://hamvoip.org</a></div> </div></div>
<br>_______________________________________________<br>
<br>
arm-allstar mailing list<br>
<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a><br>
<br>
Visit the BBB and RPi2 web page - <a href="http://hamvoip.org" rel="noreferrer" target="_blank">http://hamvoip.org</a><br></blockquote></div><br></div>
<br>_______________________________________________
arm-allstar mailing list
<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>
Visit the BBB and RPi2 web page - <a href="http://hamvoip.org" target="_blank">http://hamvoip.org</a></div> </div></div>
<br>_______________________________________________<br>
<br>
arm-allstar mailing list<br>
<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a><br>
<br>
Visit the BBB and RPi2 web page - <a href="http://hamvoip.org" rel="noreferrer" target="_blank">http://hamvoip.org</a><br></blockquote></div><br></div>