03-08-2024 09:06 PM
I have been provided with an EE72E dongle to connect to the internet via WiFi which seems to work fine when I connect to the internet via the donge's WiFi directly from my Macbook. However my need is to connect my Linux-based firewall/router for the house to the internet, rather than just one computer, so I have connected a USB Wifi dongle to the router, and established a WiFi connection from the router to the EE dongle.
Theoretically this should be sufficient, IMO. However any outgoing packets sent to the WiFi interface on the router just disappear - none are ever replied to, whether DNS query or anything else. I do have a default route set to use the WiFi connection, and I am monitoring the packets using "tshark -i wlx50*****fc8".
What is going wrong? How can I make this all work?
[I have obscured some text for privacy]
$ iwconfig wlx503e****5fc8
wlx503e****5fc8 IEEE 802.11 ESSID:"4G-WiFi-****-2.4GHz"
Mode:Managed Frequency:2.462 GHz Access Point: 3C:EF:****:65:46
Bit Rate=65 Mb/s Tx-Power=14 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=47/70 Signal level=-63 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:1786 Missed beacon:0
Typical tshark dump:
140 7.516882707 192.168.1.227 → 8.8.8.8 DNS 105 Standard query 0x835e A rABNa0zw9.ebl.msbl.org OPT
141 7.519401426 192.168.1.227 → 8.8.8.8 DNS 105 Standard query 0x835e A rABNa0zw9.ebl.msbl.org OPT
142 7.538458880 192.168.1.227 → 192.203.230.10 DNS 98 Standard query 0x3c9c A registry.k8s.io OPT
143 7.548033283 192.168.1.227 → 192.168.1.1 DNS 77 Standard query 0xa0c4 A 2.uk.pool.ntp.org
144 7.548096380 192.168.1.227 → 192.168.1.1 DNS 77 Standard query 0x41b8 AAAA 2.uk.pool.ntp.org
145 7.549894096 192.168.1.227 → 192.203.230.10 DNS 97 Standard query 0x9749 A auth.docker.io OPT
146 7.552442914 192.168.1.227 → 192.203.230.10 DNS 98 Standard query 0x3c9c A registry.k8s.io OPT
...
170 8.481124541 192.168.1.227 → 4.4.4.4 DNS 97 Standard query 0x4b36 A auth.docker.io OPT
171 8.483271934 192.168.1.227 → 4.4.4.4 DNS 97 Standard query 0x4b36 A auth.docker.io OPT
172 8.525839762 192.168.1.227 → 199.7.83.42 DNS 82 Standard query 0x9d03 NS <Root> OPT
173 8.528317529 192.168.1.227 → 199.7.83.42 DNS 82 Standard query 0x9d03 NS <Root> OPT
174 8.789675224 192.168.1.227 → 4.4.4.4 DNS 98 Standard query 0x8a18 A p2p.reolink.com OPT
175 8.791941526 192.168.1.227 → 4.4.4.4 DNS 98 Standard query 0x8a18 A p2p.reolink.com OPT
...
Interface status:
17: wlx503e****5fc8: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 50:3e:aa:52:5f:c8 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.227/24 brd 192.168.1.255 scope global dynamic wlx503e****5fc8
valid_lft 79866sec preferred_lft 79866sec
Routes:
$ ip route
default via 192.168.1.1 dev wlx503e****5fc8 metric 50
192.168.1.0/24 dev wlx503e****5fc8 proto kernel scope link src 192.168.1.227 metric 50
...
04-08-2024 03:45 PM
Sorry, I had picked up the wrong mobile router. Now put the right 1 in I should have said:
Login to your MBB router at http://192.168.1.1 with the admin password found under the battery cover. Then look at Status > Connected devices.
@rivimey wrote:
You are misunderstanding the WiFi connection's addressing:
I don't think so! It's just that we speak a diff tech lingo. However I did get confused between your USB WiFi dongle attached to your other router & the 4GEE WiFi router (which is not a dongle at all).
So the upshot is that 192.168.1.1 is the IP addy of the 4GEE WiFi router & 192.168.1.227 is the IP addy of your other router, via its USB WiFi dongle.
I do understand how packets & NAT work.
IPv4 should work between the 4GEE WiFi router & the other router.