-
Notifications
You must be signed in to change notification settings - Fork 23
Ninja-upribox wireless SSID no connectivity #25
Comments
Hi @jziggy101, so the tissue with the ninja Wifi is - that you never get a valid IP address for the WiFi network? If you connect successfully to the ninja WiFi your devices should get an IP starting with 192.168.56.. Which clients/devices are you using? |
Markus I understand how it did work until about the same time my other ssid On 3:19PM, Fri, Sep 16, 2016 Markus Huber notifications@github.com wrote:
|
Markus I see a new version on my upribox so I tested the ninja ssid and it connected, received ip and is on the tor network. |
Great to hear, thanks for reporting issues back to us - very much appreciated. |
I enabled the Ninja-upribox SSID and neither my laptop or tablet can connect to the SSID. My devices will attempt connection, attempt to resolve an ip address then fail and start the process again.
Sometimes the laptop will connect with only a 169.255.x.x address and no network connectivity nor internet.
Back in August I had used the ninja SSID with great success, it connected and I had access to the TOR network via that connection. Sometime late in August I was no longer able to connect to the ninja SSID.
tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:192.168.155.1 P-t-P:192.168.155.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr 02:de:27:1d:1f:30
inet addr:192.168.55.254 Bcast:192.168.55.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24886 errors:0 dropped:0 overruns:0 frame:0
TX packets:30589 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4129706 (3.9 MiB) TX bytes:23487945 (22.3 MiB)
wlan0_0 Link encap:Ethernet HWaddr 02:de:27:1d:1f:31
inet addr:192.168.56.254 Bcast:192.168.56.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:518 errors:0 dropped:12 overruns:0 frame:0
TX packets:569 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:70800 (69.1 KiB) TX bytes:94564 (92.3 KiB)
root@upribox:/home/upri# iwconfig
tun0 no wireless extensions.
wlan0 IEEE 802.11bgn Mode:Master Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
lo no wireless extensions.
wlan0_0 IEEE 802.11bgn Mode:Master Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
eth0 no wireless extensions.
root@upribox:/var/tmp/log/tor# more log
Sep 14 16:23:18.000 [notice] Tor 0.2.5.12 (git-3731dd5c3071dcba) opening new log file.
Sep 14 16:23:18.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Sep 14 16:23:22.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Sep 14 16:23:26.000 [notice] Bootstrapped 0%: Starting
Sep 14 16:23:35.000 [notice] Bootstrapped 5%: Connecting to directory server
Sep 14 16:23:35.000 [notice] We now have enough directory information to build circuits.
Sep 14 16:23:35.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Sep 14 16:23:35.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Sep 14 16:23:37.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Sep 14 16:23:38.000 [notice] Tor has successfully opened a circuit. Looks like client functio
nality is working.
Sep 14 16:23:38.000 [notice] Bootstrapped 100%: Done
root@upribox:/var/tmp/log/tor#
The text was updated successfully, but these errors were encountered: