[arm-allstar] wireless

[Christopher Kovacs]

This usually indicates a gateway issue (ip route). The DNS can be verified
using "nslookup" utility and see if it resolves correctly.

What is interesting is that you are using netctl and not systemd for
network control.  For the Allstar RPI2 release 1.0, you should only be
using systemd for control.  If you use netctl, it will be a direct conflict
with systemd networking services  and cause issues like this.

You must be use systemd and DHCP for a wireless FOB device to work
correctly for the wireless fob and eth0 network device.

I have successfully used a wireless fob under the rpi2 1.0 code. However,
if you want to run wireless, I would recommend using the IO gear ethernet
wireless to wire dongle, it's simple and plug and play and the rpi2 thinks
it's connected to a wired connection.  You don't need to play with systemd,
wpa_supplicant services, etc.

73,
Chris w0anm

On Sun, Aug 16, 2015 at 7:23 PM, Eric Harrison <n7jys at yahoo.com> wrote:

> I have looked through and followed the RPI2 wireless notes and was able to
> get a netgear micro usb wireless
> dongle to work. However when i ping the outside world it comes back
> unreachable. I have tried setting DNS
> parameters in the netctl config file that did not fix the issue. I dealt
> withe the same issue with an IRLP node but
> got it working  with adding DNS parameters in the network config file. Not
> sure what I'm overlooking.
>
>
> Eric (N7JYS) Marshall's Communications
>
> _______________________________________________
>
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150817/c5b0ead5/attachment.html>