06-05-2018, 02:32 PM
Alright, that didn't work, I guess I'm stuck calling it wlx48022a9d4d57.
But I re-did my simple interfaces file (using the wlx48022a9d4d57 name) and rebooted. Now ip a shows
I got a lease, and an IP. Sort of. Still can't ping the AP/router, or www.google.com. BUT oddly enough I can get back in. On a phone I scanned my subnet and saw it. So I FTPed a file out as a test. Then I started wondering what was open so I port scanned it with Zenmap on my portable Pi.
I get "destination host unreachable" trying to get out of the Rock but I can reach in. Sounds like a netmask problem to me but I don't know where it would be.
But I re-did my simple interfaces file (using the wlx48022a9d4d57 name) and rebooted. Now ip a shows
Code:
: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether de:0a:fc:15:fc:d9 brd ff:ff:ff:ff:ff:ff
3: wlx48022a9d4d57: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 48:02:2a:9d:4d:57 brd ff:ff:ff:ff:ff:ff
inet 192.168.43.117/24 brd 192.168.43.255 scope global wlx48022a9d4d57
valid_lft forever preferred_lft forever
inet6 fe80::4a02:2aff:fe9d:4d57/64 scope link
valid_lft forever preferred_lft forever
I got a lease, and an IP. Sort of. Still can't ping the AP/router, or www.google.com. BUT oddly enough I can get back in. On a phone I scanned my subnet and saw it. So I FTPed a file out as a test. Then I started wondering what was open so I port scanned it with Zenmap on my portable Pi.
I get "destination host unreachable" trying to get out of the Rock but I can reach in. Sounds like a netmask problem to me but I don't know where it would be.