[arm-allstar] RPi3 wireless.

[Doug Crompton]

The system logging can be viewed by  journalctl.   journalctl -b  shows
boot.  Do a man journalctl for more info. It is very powerful and has lots
of options.

Did you try  dhcpcd wlan0 ?


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Sat, Apr 29, 2017 at 1:28 AM, "Larry via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Thanks for the feedback Doug.
>
> I still assume it was more than likely something here.
>
> One of the options in the setup is to view your wpa_supplicant file. Does
> that file look correct? It should show your selected SSID and passphrase as
> well as an encrypted key.
>
> Yes that shows what you noted and appears to be correct
>
> The Pi and our code is IPv4. Are you getting any other
> messages on the HDMI connected terminal when you boot?
>
> The boot screen scrolls so fast it is hard to tell. However after it
> completes and I log into the node
> while it sits after announcing the 127.0.0.1 IP it does feed back some
> message about not finding an IPV6 Setting.
>
> Where is there a boot log stored that I can look at?
>
> Larry - N7FM
>
>
>
>
>
> On 04/28/2017 10:11 PM, "Doug Crompton via arm-allstar" wrote:
>
>> Larry,
>>
>> Sorry you are having problems. It works for most everyone else but usually
>> in the few times when there are problems it is on a cell connection and
>> not
>> on a home network. It does not matter where the DHCP server is as long as
>> it is on your LAN and accessible and you only have one server configured.
>>
>> I would not recommend playing with other network packages as the one
>> supplied does work. We just have to figure out why it is not in your case.
>>
>> One of the options in the setup is to view your wpa_supplicant file. Does
>> that file look correct? It should show your selected SSID and passphrase
>> as
>> well as an encrypted key.
>>
>> Do you have anything else you can try connecting to wireless? A Phone
>> hotspot etc.? The Pi and our code is IPv4. Are you getting any other
>> messages on the HDMI connected terminal when you boot?
>>
>> I did have a situation where I could not connect to a wireless router no
>> matter what I did while it would connect to others. I ended up replacing
>> the router as it was old.
>>
>> The other thing you can try after it boots and it does not get an address
>> is:
>>
>> dhcpcd wlan0
>>
>> and see what messages you get.
>>
>> Also you can have both wired and wireless connected for testing. It won't
>> work correctly that way but if you look at   ifconfig   it should show
>> both
>> interfaces and they both should get an IP address from your router. Wired
>> and wireless use different mac addresses.
>>
>>
>>
>> *73 Doug*
>>
>> *WA3DSP*
>>
>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>
>> On Sat, Apr 29, 2017 at 12:27 AM, "Larry via arm-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>> I am unable to get my wireless network to work on the latest Arm 1.5
>>> version. (I did the latest upgrade)
>>>
>>> I know I must be doing something wrong but haven't any idea what.
>>> The new menu shows no errors when I configure the wireless but I can
>>> never
>>> obtain an IP from the wireless access point. Wired Internet works
>>> perfect.
>>>
>>> I do have somewhat of a different set up. I am using a wireless router
>>> configured as just an access point and it does not do DHCP.
>>> DHCP addresses are provided by the main router for all wired and wireless
>>> devices.
>>> I have numerous other wireless devices all auto connecting that work
>>> fine.
>>>
>>> I tried setting the access point's wireless security to Open, WEP,
>>> WPA-PSK
>>> and matched the settings on the Pi3. Rebooted and get nothing.
>>> Do see a message pop on the screen when using a monitor/keyboard about it
>>> not having a IPv6 connection. My system is set only for IPv4.
>>> Don't know if that might be something I need to look at.
>>> Tried #7 menu everyway I can think of. Wireless detects my SSID and has
>>> 40/70 signal strength. just doesn't obtain an IP
>>> IP readback gives 127.0.0.1 whenever it boots without wired Internet
>>> hooked up.
>>>
>>> What (non menu) wireless program is used to configure the wireless device
>>> on the Arm PI3?
>>>
>>> I did have a friends Pi3 IRLP node that had wired connect issues. I was
>>> told to download and use wcid to do network configure for both
>>> wired/wireless for the IRLP Pi3 node.
>>> Did that and afterwards it all worked perfect while it was at my
>>> location.
>>> Didn't know if doing that would break anything on the Arm 1.5 version as
>>> the IRLP unit was a debian Jessie node.
>>>
>>> I am assuming this Pi3 wireless works for everyone else and its just me
>>> having trouble?
>>>
>>> So asking for pointers.
>>>
>>> Larry - N7FM
>>>
>>>
>>> _______________________________________________
>>>
>>> arm-allstar mailing list
>>> arm-allstar at hamvoip.org
>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>
>>> Visit the BBB and RPi2/3 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/3 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/3 web page - http://hamvoip.org
>
>