rodrigo

Comments

  • Again, tried the 192.168.1.0/24 address, but no dice. The result from running "arp -a" is ? (192.168.1.2) at <incomplete> on wlp170s0 So there's something there, but there are no open ports and pings fail with "Destination Host Unreachable"
  • I tried the Nebula registration as a hail Mary to revive the AP. If you check further you'll see that the registration was made with the MAC and serial number, but that it never actually connected to any off-site servers. I'll try the manual route now that I have a minute
  • BTW, ARP and nmap scans of 192.168.0.0/16 will occasionally show something in 192.168.230.2, but the MAC address of these hits was never resolved. I did get a curious hit at 192.168.1.22, which brought me to a Ingitenet Metrolinq login page. Still not sure what device that corresponded to
  • I already have tried these things, but they did not work. Connecting the AP to the router turns on the Zyxel-XXXX SSID, and I was finally able to connect to it. However, while the AP forwarded traffic to the router and outside world, I was still not able to reach the AP itself — via 1.1.1.1 (since it would reach…
Avatar