Re: [PLUG] Wireless access point issues

2019-02-26 Thread Ben Koenig
On 2/26/19 4:43 PM, Rich Shepard wrote: On Tue, 26 Feb 2019, Russell Senior wrote: I gave you the next step in my first email:  "Or, failing everything else, use whatever facility there is to factory reset it and then reconfigure to your liking." Okay, Russell. I'll do that this coming

Re: [PLUG] Wireless access point issues

2019-02-26 Thread Rich Shepard
On Tue, 26 Feb 2019, David wrote: It would probably have everything to do with it if you don't specify the port number when you use you attempt to connect. Try http://192.168.55.200:8080/ dafr, I hoped this was the solution, but it's not. The firefox tab tries to connect and doesn't. This

Re: [PLUG] Wireless access point issues

2019-02-26 Thread Russell Senior
> Next step? > I gave you the next step in my first email: "Or, failing everything else, use whatever facility there is to factory reset it and then reconfigure to your liking." ___ PLUG mailing list PLUG@pdxlinux.org

Re: [PLUG] Wireless access point issues

2019-02-26 Thread David
On 2/26/19 3:29 PM, Rich Shepard wrote: On Tue, 26 Feb 2019, Rich Shepard wrote: Since nmap sees the WAP (line 5 of the results) and it's up what might be preventing me (and root) from pinging it or accessing its admin page using the browser? More information: # nmap -sS 192.168.55.200

Re: [PLUG] Wireless access point issues

2019-02-26 Thread Rich Shepard
On Tue, 26 Feb 2019, Rich Shepard wrote: Since nmap sees the WAP (line 5 of the results) and it's up what might be preventing me (and root) from pinging it or accessing its admin page using the browser? More information: # nmap -sS 192.168.55.200 Starting Nmap 7.12 ( https://nmap.org ) at

Re: [PLUG] Wireless access point issues

2019-02-26 Thread Rich Shepard
On Tue, 26 Feb 2019, Rich Shepard wrote: Off to read on using nmap. # nmap -sP 192.168.55.2-200 Starting Nmap 7.12 ( https://nmap.org ) at 2019-02-26 15:23 PST Nmap scan report for router1.appl-ecosys.com (192.168.55.4) Host is up (0.0023s latency). MAC Address: 00:0F:66:09:8C:BE

Re: [PLUG] Wireless access point issues

2019-02-26 Thread Rich Shepard
On Tue, 26 Feb 2019, Tomas Kuchta wrote: Check DHCP leases if your AP took a lease. Other than that nmap is the network scanner. Tomas, DHCP is off on all hosts, including the router and WAP. I'll read about nmap as I've not used it in years. Oh One more idea, are you connecting to

Re: [PLUG] Wireless access point issues

2019-02-26 Thread Tomas Kuchta
Check DHCP leases if your AP took a lease. Other than that nmap is the network scanner. I know, you said static IPs... You are debugging unknown problem, so it is usually worth it to verify all your assumptions. Oh One more idea, are you connecting to AP using http or https? Would the other

Re: [PLUG] Wireless access point issues

2019-02-26 Thread Rich Shepard
On Tue, 26 Feb 2019, Russell Senior wrote: So, ping ipaddrs instead. for i in $(seq 2 254) ; do echo $i $(ping -q -c5 192.168.55.$i) ; done There are only three hosts now active on the LAN: this desktop, the router, and the WAP. Running this script from this desktop generated results from

Re: [PLUG] Wireless access point issues

2019-02-26 Thread Russell Senior
If you are going to go all "tool"y, there is nmap. :-) On Tue, Feb 26, 2019, 10:34 Steve Dum wrote: > I always found Angry IP Scanner https://angryip.org > A convenient java based tool to scan the local network. I reports the IP > addresses, Hostname, Mac Address and even MAC Vendor. (as well

Re: [PLUG] Wireless access point issues

2019-02-26 Thread Steve Dum
I always found Angry IP Scanner https://angryip.org A convenient java based tool to scan the local network. I reports the IP addresses, Hostname, Mac Address and even MAC Vendor.  (as well as other things, all configurable from a tools menu). Much quicker than manual pinging. It launches lots

Re: [PLUG] Wireless access point issues

2019-02-26 Thread Russell Senior
> > Try pinging all the addresses. I assume there are only 253 possibilities, > > so that's easy to script. > > Cannot ping the MAC addresses from the shell. > So, ping ipaddrs instead. for i in $(seq 2 254) ; do echo $i $(ping -q -c5 192.168.55.$i) ; done

Re: [PLUG] Wireless access point issues

2019-02-26 Thread Rich Shepard
On Tue, 26 Feb 2019, Russell Senior wrote: Have you tried power cycling it? Russell, Yes. This makes no difference. And I should have written that my friend connects through this WAP from her laptop daily with no issues. It's working as the wireless connection between her laptop and the

Re: [PLUG] Wireless access point issues

2019-02-26 Thread Russell Senior
Have you tried power cycling it? Do you know the MAC address (probably printed on the case)? Check the DHCP leases on your gateway router for that MAC address. Try pinging all the addresses. I assume there are only 253 possibilities, so that's easy to script. It might have lost its settings,

Re: [PLUG] Wireless access point issues

2019-02-26 Thread Rich Shepard
On Sun, 24 Feb 2019, Rich Shepard wrote: I want to connect my Nokia 6.1 Plus phone to the LAN's wireless access point. This means connecting to the WAP so I can figure out how to configure it to allow access to it from the phone. Let me rephrase my request: I cannot log in to the WAP admin

[PLUG] Wireless access point issues

2019-02-24 Thread Rich Shepard
I want to connect my Nokia 6.1 Plus phone to the LAN's wireless access point. This means connecting to the WAP so I can figure out how to configure it to allow access to it from the phone. The first problem is that I no longer can connect to the WAP with a browser so I can log in as admin.