<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><font style="" face="Tahoma,sans-serif" color="#000000">Bryan,<br><br> That is great. Very glad to hear you got it working. IP addresses will stay the same throughout the cell system with just a very brief glitch between cells. The initial up to 10 minute delay for connecting is not unique to portable operation. The node database at each node is only updated every 10 minutes on a random basis. Your database on the portable node is updated immediately at boot but the node you want to connect to may take as long as 10 minutes to receive your IP address. You will get a connection fail message until BOTH ends have valid node data. It would be 10 minutes or less, often less as it is random per node.<br><br>We are working on a fix to greatly reduce that time which will be in a future update.<br id="FontBreak"></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">http://www.crompton.com/hamradio</font></b><font style="font-size:16pt;" size="4"><br></font><br><br><div><hr id="stopSpelling">Date: Mon, 29 Aug 2016 19:50:43 -0700<br>To: arm-allstar@hamvoip.org<br>Subject: Re: [arm-allstar] Another Wifi Issue<br>From: arm-allstar@hamvoip.org<br>CC: bryan@k6cbr.us<br><br><div dir="ltr">Doug,<div><br></div><div>Your magic is strong. :)</div><div><br></div><div>I performed the setup again (did not clear the file just for testing) and tried to connect. It failed.</div><div><br></div><div>I then performed the <span style="font-family:Tahoma,sans-serif;font-size:12.8px;">clear_wpa_passwd_file.sh command and started setup again. Loaded the home wifi and key. Removed ethernet connection and restarted the box. Synced right up and got online.</span></div><div><span style="font-family:Tahoma,sans-serif;font-size:12.8px;"><br></span></div><div><span style="font-family:Tahoma,sans-serif;font-size:12.8px;">Not sure what I did wrong, sure I may of hand a typo, but on both network configs... I doubt it. Dunno.</span></div><div><span style="font-family:Tahoma,sans-serif;font-size:12.8px;"><br></span></div><div><font face="Tahoma, sans-serif"><span style="font-size:12.8px;">I loaded the 2nd network credentials and jumped in the truck to go pick up dinner, turned on the MiFi and it connected. Had a little worry for a few mins, as the node did no show online for about 10 mins. It finally refreshed and it appears we are working! Hope to get a modified 888 if I can get an order placed, so I can finally have the real fun... audio adjustments.</span></font></div><div><font face="Tahoma, sans-serif"><span style="font-size:12.8px;"><br></span></font></div><div><font face="Tahoma, sans-serif"><span style="font-size:12.8px;">Thank you for the help (and your site).. first round is on me.</span></font></div><div><font face="Tahoma, sans-serif"><span style="font-size:12.8px;"><br></span></font></div><div><font face="Tahoma, sans-serif"><span style="font-size:12.8px;">Bryan</span></font></div><div><font face="Tahoma, sans-serif"><span style="font-size:12.8px;">K6CBR</span></font></div></div><div class="ecxgmail_extra"><br><div class="ecxgmail_quote">On Mon, Aug 29, 2016 at 4:38 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="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;">
<div><div dir="ltr"><font face="Tahoma,sans-serif" color="#000000">Bryan,<br><br> Yes, what you show is what would be expected for a wired connection.<br></font><span><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/<wbr>hamradio</a></font></b><font style="font-size:16pt;" size="4"><br></font><br><br></span><div><hr>Date: Mon, 29 Aug 2016 15:10:25 -0700<br>To: <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>Subject: Re: [arm-allstar] Another Wifi Issue<div><div class="h5"><br>From: <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>CC: <a href="mailto:bryan@k6cbr.us" target="_blank">bryan@k6cbr.us</a><br><br><div dir="ltr"><span style="font-size:12.8px;">Doug, thanks for the response.</span><div style="font-size:12.8px;"><br>I am at work and the box is at home, but a quick connection returned the following: (on ethernet)</div><div style="font-size:12.8px;"><br></div><div style="font-size:12.8px;">[root@bryan01 ~]# ifconfig<br><span>eth0: flags=4163<UP,BROADCAST,RUNNIN<wbr>G,MULTICAST> mtu 1500<br></span> inet 192.168.1.140 netmask 255.255.255.0 broadcast 192.168.1.255<br> =
2� inet6 fe80::ba27:ebff:fe02:2b0c prefixlen 64 scopeid 0x20<link><br> ether b8:27:eb:02:2b:0c txqueuelen 1000 (Ethernet)<br> RX packets 265505 bytes 48419285 (46.1 MiB)<br> RX errors 0 dropped 283 overruns 0 frame 0<br> TX packets 88767 bytes 10078681 (9.6 MiB)<br><span> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br><br><br>lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536<br> inet 127.0.0.1 netmask 255.0.0.0<br> inet6 ::1 prefixlen 128 scopeid 0x10<host><br></span> loop txqueuelen 0 (Local Loopback)<br> RX packets 36095 bytes 4110502 (3.9 MiB)<br><span> RX errors 0 dropped 0 overruns 0 frame 0<br></span> TX packets 36095 bytes 4110502 (3.9 MiB)<br><span> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br><br><br></span>wlan0: flags=4099<UP,BROADCAST,MULTIC<wbr>AST> mtu 1500<br> inet6 fe80::ba27:ebff:fe57:7e59 prefixlen 64 scopeid 0x20<link><br> ether b8:27:eb:57:7e:59 txqueuelen 1000 (Ethernet)<br> RX packets 898554 bytes 384794749 (366.9 MiB)<br> RX errors 0 dropped 898046 overruns 0 frame 0<br> TX packets 505 bytes 80048 (78.1 KiB)<br><span> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br><br><br></span>I will repeat your steps again tonight when home and report back.<br>Thanks again.<br></div></div><div><br><div>On Mon, Aug 29, 2016 at 2:50 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">
<div dir="ltr"><font face="Tahoma,sans-serif" color="#000000">Bryan,<br><br> Sorry to hear you are having problems there with wifi. I use it extensively here and have not had any problems. <br><br>First I am pretty sure you are using the latest wifi version since in has been out there several weeks. The latest package is:<br><br><a href="https://hamvoip.org/downloads/hamvoip-wireless-config-0.1-7.pkg.tar.xz" target="_blank">https://hamvoip.org/downloads/<wbr>hamvoip-wireless-config-0.1-7.<wbr>pkg.tar.xz</a><br></font><br><font face="Tahoma,sans-serif">The prior version 1-6 had some problems with spaces in SSID's and no passphrase SSID's<br><br>The very best way to work on wireless is to use an HDMI monitor and keyboard attached to the Pi. That way you will always have access, be able to send commands, and be able to see what is going on.<br><br>Connect wired and you should see something like this of course with your IP address range. The command is 'ifconfig' In this case I only have wired connected and it shows an IP address for eth0 and not wlan0.<br><br>[root@Pi3-1 ~]# ifconfig<br>eth0: flags=4163<UP,BROADCAST,RUNNIN<wbr>G,MULTICAST> mtu 1500<br> inet 192.168.0.39 netmask 255.255.255.0 broadcast 192.168.0.255<br> inet6 fe80::ba27:ebff:fe40:4958 prefixlen 64 scopeid 0x20<link><br> ether b8:27:eb:40:49:58 txqueuelen 1000 (Ethernet)<br> RX packets 406326 bytes 93161259 (88.8 MiB)<br> RX errors 0 dropped 28 overruns 0 frame 0<br> TX packets 345946 bytes 24742387 (23.5 MiB)<br> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br><br>lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536<br> inet 127.0.0.1 netmask 255.0.0.0<br> inet6 ::1 prefixlen 128 scopeid 0x10<host><br> loop txqueuelen 1 (Local Loopback)<br> RX packets 3309 bytes 368385 (359.7 KiB)<br> RX errors 0 dropped 0 overruns 0 frame 0<br> TX packets 3309 bytes 368385 (359.7 KiB)<br> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br><br>wlan0: flags=4099<UP,BROADCAST,MULTIC<wbr>AST> mtu 1500<br> ether b8:27:eb:15:1c:0d txqueuelen 1000 (Ethernet)<br> RX packets 1 bytes 60 (60.0 B)<br> RX errors 0 dropped 1 overruns 0 frame 0<br> TX packets 0 bytes 0 (0.0 B)<br> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br><br></font><font face="Tahoma,sans-serif">Now here is the same thing for a wireless only connection showing the IP address for wlan0 and NOT eth0.</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif">[root@41139-Mobile ~]# ifconfig</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif">eth0: flags=4099<UP,BROADCAST,MULTIC<wbr>AST> mtu 1500</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> ether b8:27:eb:01:2c:73 txqueuelen 1000 (Ethernet)</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> RX packets 0 bytes 0 (0.0 B)</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> RX errors 0 dropped 0 overruns 0 frame 0</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> TX packets 0 bytes 0 (0.0 B)</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif">lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> inet 127.0.0.1 netmask 255.0.0.0</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> inet6 ::1 prefixlen 128 scopeid 0x10<host></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> loop txqueuelen 0 (Local Loopback)</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> RX packets 36095=
2�
bytes 4238619 (4.0 MiB)</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> RX errors 0 dropped 0 overruns 0 frame 0</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> TX packets 36095 bytes 4238619 (4.0 MiB)</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif">wlan0: flags=4163<UP,BROADCAST,RUNNIN<wbr>G,MULTICAST> mtu 1500</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> inet 192.168.0.33 netmask 255.255.255.0 broadcast 192.168.0.255</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> inet6 fe80::ba27:ebff:fe54:7926 prefixlen 64 scopeid 0x20<link></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> ether b8:27:eb:54:79:26 txqueuelen 1000 (Ethernet)</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> RX packets 913850 bytes 119998148 (114.4 MiB)</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> RX errors 0 dropped 255 overruns 0 frame 0</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> TX packets 342010 bytes 42302139 (40.3 MiB)</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif">So that is what it should look like in both instances. If you are not seeing an IP address in either case then you obviously have a problem. I have seen older routers that for some reason did not issue IP addresses properly. In one case I had to buy a new router to make it work. </font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif">I think you already did this but make sure the wpa_supplicant file is deleted. </font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> clear_wpa_passwd_file.sh</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif">Then run the wireless setup again for you home wireless. Make sure you have everything defined properly. You need to check (spacebar) the SSID you want then enter passphrase on the next screen. It will then come up and show and ask you to confirm those entries.</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif">You can also issue -</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> systemctl stop wpa_supplicant@wlan0.service</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif">wait a few seconds and then issue -</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"> systemctl start wpa_supplicant@wlan0.service</font><br><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif">Then check the IP's again.</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif">At boot the system should tell you what IP address it has found on the radio if oyu have it connected and configured.</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif">If you go into rpt.conf and uncomment the 'A1' line in the functions section a *A1 DTMF will repeat back your IP address. </font><br><br><font face="Tahoma,sans-serif">I hope some of that helps. Let us know.</font><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/hamrad<wbr>io</a></font></b><font style="font-size:16pt;" size="4"><br></font><br><br><div><hr>Date: Mon, 29 Aug 2016 10:45:22 -0700<br>To: <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>Subject: [arm-allstar] Another Wifi Issue<br>From: <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>CC: <a href="mailto:bryan@k6cbr.us" target="_blank">bryan@k6cbr.us</a><div><div><br><br><div dir="ltr">Hello all!<div><br></div><div>I have an issue with WiFi on my first build.</div><div><br>Specs:</div><div><br></div><div>Raspberry Pi3 B (built in WiFi)</div><div>AllStar v1.02Beta (crompton site download)</div><div><br></div><div>I have the node online and connecting to show status and can connect to another node. (No radio as of today, will have it shortly) </div><div><br></div><div>Of course, I didn't read the 'readme' until I noticed I had no WiFi, went back and read the note. Installed the WiFi and had no errors.</div><div><br>I can launch wireless-setup.sh and am able to see my network, select it and add the key. Here is where my problem starts, it simply won't connect. I tried my home network first then did the setup process again and did my MiFi device for Verizon. Neither will get online. Both networks are confirmed online and I have the correct keys.</div><div><br></div><div>My steps were: Install wireless software, run setup process, select home network and added key. Said no to reboot and finished setup. Went to box, removed ethernet cable and did a hard restart. Repeated the same setups for the MiFi card and no luck.</div><div><br>I checked the ...custom-wlan0.conf file and I think the switch between networks messed things up. I saw the home network SSID but the key for the MiFi. I edited the .conf file to correct the SSID, saved and hard reboot, same result. I then cleared the .conf file and did setup again, the .conf file re-created itself but was not able to connect via WiFi.</div><div><br></div><div>Any help would be appreciated.</div><div><br clear="all"><div><br></div>-- <br><div data-smartmail="gmail_signature"><div dir="ltr">Bryan aka K6CBR </div><div dir="ltr"><a href="mailto:bryan@k6cbr.us" target="_blank">bryan@k6cbr.us</a><div><a href="http://www.k6cbr.us" target="_blank">www.k6cbr.us</a></div><div><a href="http://www.qrz.com/db/K6CBR" target="_blank">QRZ</a></div></div></div></div></div>
<br></div></div>______________________________<wbr>_________________
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-b<
wbr>in/mailman/listinfo/arm-allsta<wbr>r</a>
Visit the BBB and RPi2 web page - <a href="http://hamvoip.org" target="_blank">http://hamvoip.org</a></div></div>
</div></div>
<br>______________________________<wbr>_________________<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-b<wbr>in/mailman/listinfo/arm-allsta<wbr>r</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 clear="all"><div><br></div>-- <br><div data-smartmail="gmail_signature"><div dir="ltr">Bryan aka K6CBR<div><a href="http://www.k6cbr.us" target="_blank">www.k6cbr.us</a></div><div><a href="http://www.qrz.com/db/K6CBR" target="_blank">QRZ</a></div></div></div>
<br>______________________________<wbr>_________________
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-<wbr>bin/mailman/listinfo/arm-<wbr>allstar</a>
Visit the BBB and RPi2 web page - <a href="http://hamvoip.org" target="_blank">http://hamvoip.org</a></div></div></div> </div></div>
<br>______________________________<wbr>_________________<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-<wbr>bin/mailman/listinfo/arm-<wbr>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 clear="all"><div><br></div>-- <br><div class="ecxgmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Bryan aka K6CBR<div><a href="http://www.k6cbr.us" target="_blank">www.k6cbr.us</a></div><div><a href="http://www.qrz.com/db/K6CBR" target="_blank">QRZ</a></div></div></div>
<br>_______________________________________________
arm-allstar mailing list
arm-allstar@hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
Visit the BBB and RPi2 web page - http://hamvoip.org</div> </div></body>
</html>