Jump to content

teranaut

Active Members
  • Content Count

    7
  • Joined

  • Last visited

About teranaut

  • Rank
    Newbie

Recent Profile Visitors

442 profile views
  1. How dare you not offer 24/7 support on a volunteer service! For shame! </sarcasm>
  2. Able to connect now. I ended up having to enable "Use SSL for all the servers on this network" in HexChat to get a connection. NickServ gives some funky errors...not sure what that's about.
  3. ::CORRECTION:: When I try to connect using :6697 the remote host closes the socket immediately. Connections to :7000 time out. For the record, I'm using HexChat on Debian and have tried connections using "Accept invalid SSL certificates" enabled and disabled with the same results. Login method is set to /msg nickserv + password.
  4. I was wondering if anybody was having trouble connecting to irc.hak5.org:6667, :6697 or :7000. When I try to connect to :6667 I get an error that my ident is not found and the socket is closed by the remote host. Connection attempts to :6697 and :7000 time out. Just ran into this issue when I got back from DefCon and thought I would ask about it while I was thinking about it. Tried connecting with and without my VPN with the same results.
  5. Seb, take a nap. I'll vouch that you earned it.
  6. You can also find your recon scans in /tmp if you SSH to your nano. They come up on mine as "recon_ap-##########" and "recon_clients-#########" Just SCP those (via a local machine terminal, not the SSH session one) to your local machine and you can read through them at your leisure. An export button would be neat, but they're still there for you if you want them now.
  7. Interestingly, I had this same issue with my Nano's first boot last night. Running route -n showed me that the only available gateway was 172.16.42.1, but didn't provide a gateway for the shared internet connection. It looked a bit like this: Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 172.16.42.1 0.0.0.0 UG 0 0 0 eth2 172.16.42.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan1 I ended up having to add a route to 192.168.1.1 using
×
×
  • Create New...