No internet post install

MaxRusse11 said:
so this is very interesting because 8.8.4.4, and 1.1.1.1 were both unreachable but freebsd.org was immediately responding
Click to expand...
When pinging it shows the target IP address. Did freebsd.org perhaps ping the IPv6 address?
 
that, to me, looks like an IPv4 address because it is a flat 192.168.172.1.

Should I enable IPv6 (somewhere)?
 
MaxRusse11 said:
I added the ipv6 enable line in rc.conf, but that's not improved it.
Click to expand...
Most everything is IPV4, unless you have something special. Not being able to ping an IPV4 address number like 8.8.8.8 or 1.1.1.1 or 192.168.1.1 or ping your router ip number. Means something is not configure correctly in your wifi access point router to the outside world?

root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # drill he.net
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 14671
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; he.net. IN A

;; ANSWER SECTION:
he.net. 6962 IN A 216.218.236.2

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 24 msec
;; SERVER: 192.168.1.1
;; WHEN: Mon May 27 12:40:13 2024
;; MSG SIZE rcvd: 40
root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # drill 192.168.1.1
\;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN, id: 42591
;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;; 192.168.1.1. IN A

;; ANSWER SECTION:

;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2024052701 1800 900 604800 86400

;; ADDITIONAL SECTION:

;; Query time: 14 msec
;; SERVER: 192.168.1.1
;; WHEN: Mon May 27 12:40:50 2024
;; MSG SIZE rcvd: 104
root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # \
Click to expand...

Example of using the Drill command as Sir Dice Suggested. Sir Dice, thank you so very much for providing answers and help to MaxRusse11. I very much appreciate your giving of time to answer these questions from your experience and wealth of knowledge about FreeBSD. Thank You, Sir Dice.

Ping from your FreeBSD computer to your route IP address number
Ping from your FreeBSD computer to a known IP address number out on the internet

use Commands drill and traceroute and netstat See my forums.ghostbsd.org topic Networking for examples. Sir Dice what might you offer for testing?
root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # drill he.net
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 14671
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; he.net. IN A

;; ANSWER SECTION:
he.net. 6962 IN A 216.218.236.2

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 24 msec
;; SERVER: 192.168.1.1
;; WHEN: Mon May 27 12:40:13 2024
;; MSG SIZE rcvd: 40
root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # drill 192.168.1.1
\;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN, id: 42591
;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;; 192.168.1.1. IN A

;; ANSWER SECTION:

;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2024052701 1800 900 604800 86400

;; ADDITIONAL SECTION:

;; Query time: 14 msec
;; SERVER: 192.168.1.1
;; WHEN: Mon May 27 12:40:50 2024
;; MSG SIZE rcvd: 104
root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # \
Click to expand...
traceroute he.net
traceroute to he.net (216.218.236.2), 64 hops max, 40 byte packets
1 unknown (192.168.1.1) 0.536 ms 0.361 ms 0.593 ms
2 174.127.182.46 (174.127.182.46) 8.181 ms 8.260 ms 7.830 ms
3 be10.cr1-silverton.bb.as11404.net (174.127.141.210) 7.964 ms 8.118 ms 7.972 ms
4 174.127.138.14 (174.127.138.14) 9.979 ms 11.028 ms 9.646 ms
5 be17.cr3-sea-b.bb.as11404.net (174.127.136.154) 13.903 ms 13.986 ms 13.444 ms
6 be10.cr3-sea-a.bb.as11404.net (65.50.198.62) 14.258 ms 14.883 ms 14.318 ms
7 be55.cr2-sea-a.bb.as11404.net (65.50.198.67) 13.690 ms 14.133 ms 15.285 ms
8 be1.cr2-sea-b.bb.as11404.net (174.127.149.137) 13.730 ms 13.488 ms 13.931 ms
9 * 100ge14-2.core1.sea1.he.net (206.81.80.40) 13.711 ms *
10 hurricane.nwax.net (198.32.195.42) 11.854 ms * *
11 * * *
12 100ge14-1.core3.fmt1.he.net (72.52.92.66) 28.404 ms 45.904 ms 28.629 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
^C
Click to expand...
netstat -nr4

 
No, sorry, but in my limited technical opinion it isn't the routing out from the wifi point. I've used this with multiple devices (Win laptops, Apple, Kindle, Android, iPhones). I'd say that isn't the problem on either my home network, or this one (the mobile/holiday one).

This is laptop -> wifi -> wider world.

if it isn't something in my loaded kernel drivers, rc.conf, wpa_supplicant.conf etc. if I can find which bit I need, I'll try changing that
 
root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # traceroute theregister.com
traceroute: Warning: theregister.com has multiple addresses; using 104.18.5.22
traceroute to theregister.com (104.18.5.22), 64 hops max, 40 byte packets
1 unknown (192.168.1.1) 0.506 ms 0.363 ms 0.785 ms
2 174.127.182.46 (174.127.182.46) 10.301 ms 10.584 ms 7.171 ms
3 be10.cr1-silverton.bb.as11404.net (174.127.141.210) 7.996 ms 11.428 ms 8.738 ms
4 174.127.138.14 (174.127.138.14) 8.720 ms 10.207 ms 11.307 ms
5 be17.cr3-sea-b.bb.as11404.net (174.127.136.154) 13.935 ms 13.004 ms 22.264 ms
6 be10.cr3-sea-a.bb.as11404.net (65.50.198.62) 13.823 ms 14.323 ms 14.480 ms
7 be11.cr5-sea.bb.as11404.net (174.127.151.10) 14.617 ms 23.805 ms 13.310 ms
8 216.243.15.161 (216.243.15.161) 15.102 ms 14.975 ms 13.220 ms
9 172.71.144.3 (172.71.144.3) 20.125 ms

root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # drill 8.8.8.8
;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN, id: 28389
;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;; 8.8.8.8. IN A

;; ANSWER SECTION:

;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2024052701 1800 900 604800 86400

;; ADDITIONAL SECTION:

;; Query time: 28 msec
;; SERVER: 192.168.1.1
;; WHEN: Mon May 27 13:30:27 2024
;; MSG SIZE rcvd: 100
root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg #

172.68.20.3 (172.68.20.3) 14.032 ms
108.162.243.11 (108.162.243.11) 39.576 ms
10 104.18.5.22 (104.18.5.22) 13.222 ms 13.730 ms 13.883 ms

root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # drill theregister.com
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 39307
;; flags: qr rd ra ; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; theregister.com. IN A

;; ANSWER SECTION:
theregister.com. 73 IN A 104.18.4.22
theregister.com. 73 IN A 104.18.5.22

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 1 msec
;; SERVER: 192.168.1.1
;; WHEN: Mon May 27 13:26:16 2024
;; MSG SIZE rcvd: 65


Example you can test for yourself to verify your connectivity with the outside world. Yes, I am considering and thinking about what you said that other computer machines work fine on this wifi connection and it must be something in a configuration file in FreeBSD.

netstat -4 or netstat -nr
sockstat -4 or sockstat -6
traceroute theregister.com
traceroute 8.8.8.8
Click to expand...
 
wb7odyfred said:
root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # traceroute theregister.com
traceroute: Warning: theregister.com has multiple addresses; using 104.18.5.22
traceroute to theregister.com (104.18.5.22), 64 hops max, 40 byte packets
1 unknown (192.168.1.1) 0.506 ms 0.363 ms 0.785 ms
2 174.127.182.46 (174.127.182.46) 10.301 ms 10.584 ms 7.171 ms
3 be10.cr1-silverton.bb.as11404.net (174.127.141.210) 7.996 ms 11.428 ms 8.738 ms
4 174.127.138.14 (174.127.138.14) 8.720 ms 10.207 ms 11.307 ms
5 be17.cr3-sea-b.bb.as11404.net (174.127.136.154) 13.935 ms 13.004 ms 22.264 ms
6 be10.cr3-sea-a.bb.as11404.net (65.50.198.62) 13.823 ms 14.323 ms 14.480 ms
7 be11.cr5-sea.bb.as11404.net (174.127.151.10) 14.617 ms 23.805 ms 13.310 ms
8 216.243.15.161 (216.243.15.161) 15.102 ms 14.975 ms 13.220 ms
9 172.71.144.3 (172.71.144.3) 20.125 ms

root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # drill 8.8.8.8
;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN, id: 28389
;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;; 8.8.8.8. IN A

;; ANSWER SECTION:

;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2024052701 1800 900 604800 86400

;; ADDITIONAL SECTION:

;; Query time: 28 msec
;; SERVER: 192.168.1.1
;; WHEN: Mon May 27 13:30:27 2024
;; MSG SIZE rcvd: 100
root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg #

172.68.20.3 (172.68.20.3) 14.032 ms
108.162.243.11 (108.162.243.11) 39.576 ms
10 104.18.5.22 (104.18.5.22) 13.222 ms 13.730 ms 13.883 ms

root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # drill theregister.com
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 39307
;; flags: qr rd ra ; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; theregister.com. IN A

;; ANSWER SECTION:
theregister.com. 73 IN A 104.18.4.22
theregister.com. 73 IN A 104.18.5.22

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 1 msec
;; SERVER: 192.168.1.1
;; WHEN: Mon May 27 13:26:16 2024
;; MSG SIZE rcvd: 65


Example you can test for yourself to verify your connectivity with the outside world. Yes, I am considering and thinking about what you said that other computer machines work fine on this wifi connection and it must be something in a configuration file in FreeBSD.
Click to expand...
ps aux | grep dhclient

root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # ps aux | grep dhclient
root 85726 0.0 0.0 13252 1896 - Is Wed10 0:00.01 dhclient: system.syslog (d
root 85729 0.0 0.0 13252 1948 - Is Wed10 0:00.02 dhclient: genet0 [priv] (d
_dhcp 85730 0.0 0.0 13256 2104 - ICs Wed10 0:00.02 dhclient: genet0 (dhclient
root 11689 0.0 0.0 12844 2284 8 S+ 13:36 0:00.00 grep dhclient
root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg #
Click to expand...
killall dhclient
dhclient wlan0

Sometimes ifconfig wlan0 down ; ifconfig wlan0 up will clear a problem. Other times restart a service will clear a problem

service routing restart
service netif restart


Yes, you may have more than one configuration inside the wpa_supplicant.conf file, so that it remembers how to connect to various access points you have previously used. freshports NetworkMgr python program is a very easy to use program for connection to various wifi Access Points and through wired ethernet connections. Yes, when wifi is connected and your FreeBSD package configuration is working, you may select to install , then.

Freshports.org NetworkMgr


 
MaxRusse11 said:
that, to me, looks like an IPv4 address because it is a flat 192.168.172.1.
Click to expand...
Ok, that's interesting. When you ping freebsd.org it's that IP address that's shown? Looking at the IP, that's very likely the IP address of your router (did you check netstat -rn4). Or in this case your phone's Wifi internet sharing. Pinging any other 'outside' IP address results in a time-out, no response? All this seems to suggest the "Wifi internet sharing/Hotspot" on your phone isn't set up correctly.

MaxRusse11 said:
Should I enable IPv6 (somewhere)?
Click to expand...
No, just leave it for now. I was thinking maybe IPv6 worked but not IPv4, odd configuration but not impossible.
 
SirDice said:
Ok, that's interesting. When you ping freebsd.org it's that IP address that's shown? Looking at the IP, that's very likely the IP address of your router. Or in this case your phone's Wifi internet sharing. Pinging any other 'outside' IP address results in a time-out, no response? All this seems to suggest the "Wifi internet bridge" on your phone isn't set up correctly.


No, just leave it for now. I was thinking maybe IPv6 worked but not IPv4, odd configuration but not impossible.
Click to expand...
this is a wifi router. It's a Smarty 4g device (think they are piggy backing the EE network in UK). I would really have to understand far better what was happening with bridging, here, because as I mentioned - this hardware has worked fine with a load of devices, so although FreeBSD may see some more required correctness, I'm struggling a bit here because this process is a bit more demanding so far.
 
root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # netstat -nr4
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 192.168.1.1 UGS genet0
127.0.0.1 link#2 UH lo0
192.168.1.0/24 link#1 U genet0
192.168.1.57 link#2 UHS lo0
root@Ghost14-selfbuilt-rpi4B-nginx-tst1:/etc/pkg # netstat -nr6
Routing tables

Internet6:
Destination Gateway Flags Netif Expire
::/96 link#2 URS lo0
::1 link#2 UHS lo0
::ffff:0.0.0.0/96 link#2 URS lo0
fe80::%lo0/10 link#2 URS lo0
fe80::%lo0/64 link#2 U lo0
fe80::1%lo0 link#2 UHS lo0
ff02::/16 link#2 URS lo0

192.168.1.57 is the address for this RaspberryPi4B using wired ethernet cable. I share these examples, so that you can use same similar command and compare your results. Maybe the DHCP is giving some misconfigured information to the FreeBSD box, that other connected devices just ignore?? I am not using IPV6, I just wondered what output netstat -nr6 would give.
Click to expand...
 
MaxRusse11 said:
this is a wifi router. It's a Smarty 4g device (think they are piggy backing the EE network in UK).
Click to expand...
It's essentially a phone without a display or keypad running some specific piece of software. The "hotspot" feature on android phones is something similar.

MaxRusse11 said:
because as I mentioned - this hardware has worked fine with a load of devices
Click to expand...
I think it might be doing something more, because it's resolving everything to its own IP address. It's probably forcing you to 'register' at a so-called "captive portal" using a web browser.

To get associated with the hotspot did you use WPA/WPA2 or WEP (don't use)? Or is this an "open" network (not protected)? That probably put you on a guest access and forces you through the captive portal.
 
SirDice said:
It's essentially a phone without a display or keypad running some specific piece of software. The "hotspot" feature on android phones is something similar.


I think it might be doing something more, because it's resolving everything to its own IP address. It's probably forcing you to 'register' at a so-called "captive portal" using a web browser.

To get associated with the hotspot did you use WPA/WPA2 or WEP (don't use)? Or is this an "open" network (not protected)? That probably put you on a guest access and forces you through the captive portal.
Click to expand...
I had thought it needed WPA but changed it to Open based on some of the other advice on this thread. That did appear to allow me to see the wifi dongle.

No other devices using the same hotspot require a registration, There is the admin page which can be reached via the expected address, but I'm still trying to work out what's needed.
 
so not the usual captive portal page like in an open wifi spot. Would having changed the auth to Open make the system expect this somewhere/somehow?
 
back at home, trying to work off the Vodafone router, have followed the instructions to date, I know the entry is correct in wpa_supplicant.conf, a scan shows the correct SSID available, service netif restart, ifconfig wlan0 ssid vodafoneSSID, dhclient shows as already running then when I attempt to ping 8.8.8.8 or freebsd.org, I'm not hitting them.

I know I've tried some stuff... just don't know I'm much further on.
 
I managed to get access to pkg install networkmgr, but still not getting a connection via wifi to the router.
 
You must log in or register to reply here.
Back
Top