[arm-allstar] Another Wifi Issue
Bryan St Clair
bryan at k6cbr.us
Mon Aug 29 21:50:43 EST 2016
Doug,
Your magic is strong. :)
I performed the setup again (did not clear the file just for testing) and
tried to connect. It failed.
I then performed the 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.
Not sure what I did wrong, sure I may of hand a typo, but on both network
configs... I doubt it. Dunno.
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.
Thank you for the help (and your site).. first round is on me.
Bryan
K6CBR
On Mon, Aug 29, 2016 at 4:38 PM, Doug Crompton via arm-allstar <
arm-allstar at hamvoip.org> wrote:
> Bryan,
>
> Yes, what you show is what would be expected for a wired connection.
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> ------------------------------
> Date: Mon, 29 Aug 2016 15:10:25 -0700
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Another Wifi Issue
>
> From: arm-allstar at hamvoip.org
> CC: bryan at k6cbr.us
>
> Doug, thanks for the response.
>
> I am at work and the box is at home, but a quick connection returned the
> following: (on ethernet)
>
> [root at bryan01 ~]# ifconfig
> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.1.140 netmask 255.255.255.0 broadcast 192.168.1.255
> inet6 fe80::ba27:ebff:fe02:2b0c prefixlen 64 scopeid 0x20<link>
> ether b8:27:eb:02:2b:0c txqueuelen 1000 (Ethernet)
> RX packets 265505 bytes 48419285 (46.1 MiB)
> RX errors 0 dropped 283 overruns 0 frame 0
> TX packets 88767 bytes 10078681 (9.6 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
>
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> inet6 ::1 prefixlen 128 scopeid 0x10<host>
> loop txqueuelen 0 (Local Loopback)
> RX packets 36095 bytes 4110502 (3.9 MiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 36095 bytes 4110502 (3.9 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
>
> wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> inet6 fe80::ba27:ebff:fe57:7e59 prefixlen 64 scopeid 0x20<link>
> ether b8:27:eb:57:7e:59 txqueuelen 1000 (Ethernet)
> RX packets 898554 bytes 384794749 (366.9 MiB)
> RX errors 0 dropped 898046 overruns 0 frame 0
> TX packets 505 bytes 80048 (78.1 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
>
> I will repeat your steps again tonight when home and report back.
> Thanks again.
>
> On Mon, Aug 29, 2016 at 2:50 PM, Doug Crompton via arm-allstar <
> arm-allstar at hamvoip.org> wrote:
>
> Bryan,
>
> Sorry to hear you are having problems there with wifi. I use it
> extensively here and have not had any problems.
>
> First I am pretty sure you are using the latest wifi version since in has
> been out there several weeks. The latest package is:
>
> https://hamvoip.org/downloads/hamvoip-wireless-config-0.1-7.pkg.tar.xz
>
> The prior version 1-6 had some problems with spaces in SSID's and no
> passphrase SSID's
>
> 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.
>
> 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.
>
> [root at Pi3-1 ~]# ifconfig
> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.0.39 netmask 255.255.255.0 broadcast 192.168.0.255
> inet6 fe80::ba27:ebff:fe40:4958 prefixlen 64 scopeid 0x20<link>
> ether b8:27:eb:40:49:58 txqueuelen 1000 (Ethernet)
> RX packets 406326 bytes 93161259 (88.8 MiB)
> RX errors 0 dropped 28 overruns 0 frame 0
> TX packets 345946 bytes 24742387 (23.5 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> inet6 ::1 prefixlen 128 scopeid 0x10<host>
> loop txqueuelen 1 (Local Loopback)
> RX packets 3309 bytes 368385 (359.7 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 3309 bytes 368385 (359.7 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> ether b8:27:eb:15:1c:0d txqueuelen 1000 (Ethernet)
> RX packets 1 bytes 60 (60.0 B)
> RX errors 0 dropped 1 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> Now here is the same thing for a wireless only connection showing the IP
> address for wlan0 and NOT eth0.
>
> [root at 41139-Mobile ~]# ifconfig
> eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> ether b8:27:eb:01:2c:73 txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> inet6 ::1 prefixlen 128 scopeid 0x10<host>
> loop txqueuelen 0 (Local Loopback)
> RX packets 36095 bytes 4238619 (4.0 MiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 36095 bytes 4238619 (4.0 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.0.33 netmask 255.255.255.0 broadcast 192.168.0.255
> inet6 fe80::ba27:ebff:fe54:7926 prefixlen 64 scopeid 0x20<link>
> ether b8:27:eb:54:79:26 txqueuelen 1000 (Ethernet)
> RX packets 913850 bytes 119998148 (114.4 MiB)
> RX errors 0 dropped 255 overruns 0 frame 0
> TX packets 342010 bytes 42302139 (40.3 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> 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.
>
> I think you already did this but make sure the wpa_supplicant file is
> deleted.
>
> clear_wpa_passwd_file.sh
>
> 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.
>
> You can also issue -
>
> systemctl stop wpa_supplicant at wlan0.service
>
> wait a few seconds and then issue -
>
> systemctl start wpa_supplicant at wlan0.service
>
> Then check the IP's again.
>
> At boot the system should tell you what IP address it has found on the
> radio if oyu have it connected and configured.
>
> If you go into rpt.conf and uncomment the 'A1' line in the functions
> section a *A1 DTMF will repeat back your IP address.
>
> I hope some of that helps. Let us know.
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> ------------------------------
> Date: Mon, 29 Aug 2016 10:45:22 -0700
> To: arm-allstar at hamvoip.org
> Subject: [arm-allstar] Another Wifi Issue
> From: arm-allstar at hamvoip.org
> CC: bryan at k6cbr.us
>
>
> Hello all!
>
> I have an issue with WiFi on my first build.
>
> Specs:
>
> Raspberry Pi3 B (built in WiFi)
> AllStar v1.02Beta (crompton site download)
>
> 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)
>
> 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.
>
> 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.
>
> 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.
>
> 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.
>
> Any help would be appreciated.
>
>
> --
> Bryan aka K6CBR
> bryan at k6cbr.us
> www.k6cbr.us
> QRZ <http://www.qrz.com/db/K6CBR>
>
> _______________________________________________ arm-allstar mailing list
> arm-allstar at hamvoip.org http://lists.hamvoip.org/cgi-b
> in/mailman/listinfo/arm-allstar Visit the BBB and RPi2 web page -
> http://hamvoip.org
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2 web page - http://hamvoip.org
>
>
>
>
> --
> Bryan aka K6CBR
> www.k6cbr.us
> QRZ <http://www.qrz.com/db/K6CBR>
>
> _______________________________________________ arm-allstar mailing list
> arm-allstar at hamvoip.org http://lists.hamvoip.org/cgi-
> bin/mailman/listinfo/arm-allstar Visit the BBB and RPi2 web page -
> http://hamvoip.org
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2 web page - http://hamvoip.org
>
--
Bryan aka K6CBR
www.k6cbr.us
QRZ <http://www.qrz.com/db/K6CBR>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160829/fae1c329/attachment-0001.html>
More information about the arm-allstar
mailing list