No internet post install

MaxRusse11, Yes I can appreciate the difficulty in connecting WiFi the first time manually. That is why I wrote my forums.ghostbsd.org template to assist users like yourself in getting started.

Is your VodaPhone Wifi access point, use WPA encrypted (WEP encrypted) or just Open Access (with no encryption)?

I spent more than 8 hours myself, trying to connect to an OPEN ACCESS (ie no WPA or WEP used to connect ) wifi access point, because the /etc/rc.conf file had the term WPA in the line
Open Access just needs
DHCP not the full text for encryption "WPA DHCP".
#/etc/rc.conf add 2 lines for Intel iwn chipset wifi card
Code: 
wlans_iwn0="wlan0"
ifconfig_wlan0="WPA DHCP"
For Open Access, use only "DHCP" here!


my post at Forums GhostBSD for helping you. Refer to this, use as a template. Go step by step. That is why I wrote it down in this manner. To help new users, step by step. Please do ask questions. I want you to easily have, what I spent time and effort to learn by reading the Handbook and many URLs and forum posts.

# create wlan0, the "symbol hook for O/S to wifi wlan0 block " ? I can't describe correctly this operation command below. My apology for adding confusion.

# ifconfig wlan0 create wlandev urtwn0
# above is for a USB Realtek chipset like rtl8192cu rtl8188eu rtl8188ee
# use commands, below for your Intel iwn chipset


# create wlan0 for your iwn0 kernel module device driver iwn0

ifconfig wlan0 create wlandev iwn0
ifconfig wlan0
dmesg | tail -10


# would be nice to see the PCI Vendor IDs, and Product IDs from your Intel PCI wifi card chipset This is so we can know exactly which version Intel Wifi Chipset you are using. Details matter. when trying to solve a problem, one can not see. please Share wifi chipset output from the following comand.

pciconf -lv

Here are step directions for using commands

https://forums.freebsd.org/threads/setup-wifi-network-step-by-step.67577/post-645896
manually run this command one time to create an entry

ifconfig wlan0 create wlandev iwn0


and run about 3 commands to connect to wifi:


killall dhclient
wpa_supplicant -b -i wlan0 -c /etc/wpa_supplicant.conf
dhclient wlan0


#Need debugging information when trying to connect?
Use the following manual command lines for testing with the Debug and Password debug printout options

killall dhclient
# wpa_supplicant -d -i wlan0 -c /etc/wpa_supplicant.conf
wpa_supplicant -d -K -i wlan0 -c /etc/wpa_supplicant.conf
dhclient wlan0



my other forum post example of connecting to a PCI wifi card.

is the iwn kernel module device driver loaded? kldload iwn

kldstat | grep iwn

 
MaxRusse11 said:
groups: wlan ssid "" channel 1 (2412 MHz 11b) regdomain FCC country US authmode OPEN privacy OFF txpower 30
Click to expand...
OPEN privacy OFF, MaxRusse11, The above says is using authmode OPEN (not encrypted) wifi access point signal. You have to edit the line in the /etc/rc.conf file and remove the word " WPA "
DO NOT use line in
/etc/rc.conf
file:
ifconfig_wlan0="WPA DHCP"

DO use line in
/etc/rc.conf
file :
Code: 
ifconfig_wlan0="DHCP"

This will get you connected, MaxRusse11, to your Vodaphone access point wifi

Cath O'Deray and ericbsd and others. Yes I should file a bug report soon.
Everyone using FreeBSD is
NOT A NETWORK GURU! The WIFI connection steps should, with a DMESG error written, remove WPA part of rc.conf command line and silently connect to an OPEN WIFI ACCESS POINT. Unless you wish for security & safety sakes to MAKE IT DIFFICULT to connect to your Local Free Coffee House wifi access point !!!. I think Eric Turgeon's NetworkMGR, can edit the file /etc/rc.conf and remove WPA word when trying to connect to an open access WIFI point. But higher ups and administrators have their security methods and precise wording, to cause the end user to remove 3 characters 'WPA' from the /etc/rc.conf file line, so that he does not automatically connect to an OPEN WIFI (not secured) Access point. Someone guiding FreeBSD and GhostBSD networking security choses the wifi network connection policy.

I lost 8 hours time to this minor irritating network connection policy. Can a RED Flag error message be popped up on GUI screen? or some other method (kernel message to dmesg list ) be added to the steps for connecting to an OPEN ACCESS Wifi point?

Your thoughts about connecting to an OPEN ACCESS Wifi point?

MaxRusse11, I do hope you finally get connected to your Open Access Point Vodaphone wifi connection.

Fred
 
Can I have entries for multiple wifi in my conf? Currently I'm not working off my main household (Vodafone), I'm on my 4G wireless router
 
running dhclient returns
wlan0: no link ................. giving up

kldstat | grep iwn returns
11 1 0xffffffff82582000 551c0 iwn100fw.ko

which presumably means that kernel object for the iwn (driver) is loaded up from boot time?

The chipset as I mentioned before is the Intel centrino N100.

I have two entries in my wpa_supplicant one for the home network and one for my wifi dongle.
They both use WPA_PSK as far as I know (they're not open)
 
for my mobile dongle, when I run:
ifconfig wlan0 up list scan

HUAWEI_E5577_A6FA -
the end of line options are HTCAP RSN WME WPS
 
MaxRusse11 said:
kldstat | grep iwn returns
11 1 0xffffffff82582000 551c0 iwn100fw.ko

which presumably means that kernel object for the iwn (driver) is loaded up from boot time?
Click to expand...

That's what I expect to load, automatically (without using loader.conf). Thanks.


Next:

kldstat | grep iwlwifi

You might find if_iwlwifi.ko automatically loaded.

It is loaded on my computer, not used, harmless in my case.

I vaguely recall some cases where it was useful to suppress, explicitly not load, this module.
 
Right, latest output from ifconfig seems (to me) to suggest that the interface is alive and is aware of the wifi (the Huawei). However, I still can't get out to pkg install and I'm not confident I'm seeing out to the net:

wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=0
ether 78:92:9c:05:f4:e4
inet 192.168.172.168 netmask 0xffffff00 broadcast 192.168.172.255
groups: wlan
ssid Loco5AC:E43883C44CE9 channel 6 (2437 MHz 11g ht/20) bssid e6:38:83:c4:4c:e9
regdomain ETSI country GB authmode OPEN privacy OFF txpower 30
bmiss 10 scanvalid 60 protmode CTS ampdulimit 64k -amsdutx amsdurx
shortgi -stbc -ldpc -uapsd wme
parent interface: iwn0
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

when I try to use PKG I still get:
pkg+ // implies srv mirror type

and that is with the conf in /usr/local/etc/pkg/repos

what other steps can I take, please?
 
Example of my Arm64 aarch64 FreeBSD.conf file

cat FreeBSD.conf.orig
# $FreeBSD$
#
# To disable this repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file:
#
# mkdir -p /usr/local/etc/pkg/repos
# echo "FreeBSD: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
#

FreeBSD: {
# url: "pkg+http://pkg.freebsd.org/${ABI}/latest",
# url: "pkg+http://pkg.freebsd.org/FreeBSD:14:aarch64/latest",
url: "http://pkg.freebsd.org/FreeBSD:14:aarch64/latest",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}

You can use this line in your FreeBSD.conf file.
url: "https://pkg.freebsd.org/${ABI}/latest",
Click to expand...
mirror_type: "srv"


I think something changed in Release 14.0 that pkg+https does not work so well anymore. So I dropped the "pkg+" changed http to https

From networking changes mirror_type:"srv" for server is neccessary to get through the multiple IP address given out from the content delivery network CDN
 
Cath O'Deray said:
That's what I expect to load, automatically (without using loader.conf). Thanks.


Next:

kldstat | grep iwlwifi

You might find if_iwlwifi.ko automatically loaded.

It is loaded on my computer, not used, harmless in my case.

I vaguely recall some cases where it was useful to suppress, explicitly not load, this module.
Click to expand...
Thanks, no hits for that module when I grepped it.
 
wb7odyfred said:
Example of my Arm64 aarch64 FreeBSD.conf file

cat FreeBSD.conf.orig
# $FreeBSD$
#
# To disable this repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file:
#
# mkdir -p /usr/local/etc/pkg/repos
# echo "FreeBSD: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
#

FreeBSD: {
# url: "pkg+http://pkg.freebsd.org/${ABI}/latest",
# url: "pkg+http://pkg.freebsd.org/FreeBSD:14:aarch64/latest",
url: "http://pkg.freebsd.org/FreeBSD:14:aarch64/latest",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}
Click to expand...
so, my /usr/local/etc/pkg/repos.FreeBSD.conf is very much like that, apart from being for the default x86/AMD64 arch and not using srv as I was mentioning:
"pkg+http://pkg.freebsd.org/${ABI}/latest"
mirror_type: "none"

should I possibly reinstate the SRV type? Or os there some other reason why I don't get to packages?
 
MaxRusse11 said:
should I possibly reinstate the SRV type?
Click to expand...
Just remove that mirror_type line. Your 'latest' pkg config only has to contain the URL:
Code: 
FreeBSD: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest"
}
Everything else will get 'inherited' from /etc/pkg/FreeBSD.conf. You only want to set mirror_type to none if you point to any of the mirrors directly (i.e. not using the automatic selection).
 
SirDice said:
Just remove that mirror_type line. Your 'latest' pkg config only has to contain the URL:
Code: 
FreeBSD: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest"
}
Everything else will get 'inherited' from /etc/pkg/FreeBSD.conf. You only want to set mirror_type to none if you point to any of the mirrors directly (i.e. not using the automatic selection).
Click to expand...
thanks, but I'm still getting
pkg: Repository FreeBSD has a wrong packagesite
I've got the https, I've removed the mirror type.

reboot? (I hate that as any kind of solution)
 
MaxRusse11 said:
Right, latest output from ifconfig seems (to me) to suggest that the interface is alive and is aware of the wifi (the Huawei).
Click to expand...
Yes. The state is 'associated' which means the wireless network is correctly connected.
MaxRusse11 said:
However, I still can't get out to pkg install and I'm not confident I'm seeing out to the net
Click to expand...
Correct. If you look at the ifconfig(8) output you'll see there's no IP address assigned yet. So your wireless network is active (layer 2) but nothing above that (layer 3 and above). What you need, for test is dhclient wlan0. That should trigger a DHCP request on the network and, hopefully, it will respond with several things, an IP address for the interface, one or more DNS servers and a gateway address.
 
MaxRusse11 said:
However, I still can't get out to pkg install and I'm not confident I'm seeing out to the net:
Click to expand...
# if needed, you can killall dhclient and reissue dhclient wlan0, check connectivity first, before killing dhclient program. No need to reboot


ifconfig wlan0

# use the next two lines for dhclient program, if you see a connectivity problem above from ifconfig wlan0

killall dhclient
dhclient wlan0
ifconfig wlan0
ping -c 3 8.8.4.4
ping -c 3 freebsd.org

First ping a direct IP address number
2nd ping a Domain Name to verify Domain Naming Service DNS is operational



ping -c 3 8.8.4.4
ping -c 3 1.1.1.1
ping -c 3 he.net
ping -c 3 freebsd.org



Ping Google Domain Name Server DNS 8.8.4.4
1.1.1.1 is easy to remember
he.net is Hurricane Electric IPV6 network ISP in Freemont California USA
freebsd.org is where the software and packages comes from
Click to expand...
 
SirDice said:
If you look at the ifconfig(8) output you'll see there's no IP address assigned yet.
Click to expand...
I'm getting old, there is an IP address. I blame a lack of formatting.

Code: 
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=0
ether 78:92:9c:05:f4:e4
inet 192.168.172.168 netmask 0xffffff00 broadcast 192.168.172.255
groups: wlan
ssid Loco5AC:E43883C44CE9 channel 6 (2437 MHz 11g ht/20) bssid e6:38:83:c4:4c:e9
regdomain ETSI country GB authmode OPEN privacy OFF txpower 30
bmiss 10 scanvalid 60 protmode CTS ampdulimit 64k -amsdutx amsdurx
shortgi -stbc -ldpc -uapsd wme
parent interface: iwn0
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

This is looking good, it's 'associated' and it has an IP address/mask that looks appropriate; inet 192.168.172.168 netmask 0xffffff00 broadcast 192.168.172.255

First thing to check is the gateway, is there one and can you access it? Have a look at netstat -rn4. There's probably a default pointing at 192.168.172.1 (it could also be some other address). Ping that address. If that works try to ping something outside your local 192.168.172.0/24 network, 8.8.8.8 is an easy address to remember (it's one of Google's DNS addresses).

If pinging by IP works then you can move on to the next thing to check; DNS. If the above IP addresses don't work DNS isn't going to work either. Check if you got something from DHCP by looking at /etc/resolv.conf. When you use DHCP you almost always get DNS servers too. Query the address(es) that are mentioned in /etc/resolv.conf; drill @192.168.172.1 pkg.freebsd.org for example. That should get you some results.
 
I tried pkg-static bootstrap -f which tells me there isn't a pre-built version on my system.

I'm not really sure if my laptop is or isn't seeing the outside world yet! ifconfig would seem to say so, but I don't think I've got anything too different in my pkg setup and I can't seem to get at pkg or ports.

And that's the bits I want (like everybody)
 
wb7odyfred said:
ping -c 3 8.8.4.4
ping -c 3 1.1.1.1
ping -c 3 he.net
ping -c 3 freebsd.org

Ping Google Domain Name Server DNS 8.8.4.4 1.1.1.1 is easy to remember he.net is Hurricane Electric IPV6 network ISP in Freemont California
freebsd.org is where the software and packages comes from
Click to expand...
so this is very interesting because 8.8.4.4, and 1.1.1.1 were both unreachable but freebsd.org was immediately responding
 
You must log in or register to reply here.
Back
Top