kernel: Remove ndis(4) and associated tools and stuff.

ndis(4) was a wrapper to allow running binary Windows network
drivers that conformed to the Network Driver Interface Specification,
i.e. NDIS.

kernel: Remove ndis(4) and associated tools and stuff.

ndis(4) was a wrapper to allow running binary Windows network
drivers that conformed to the Network Driver Interface Specification,
i.e. NDIS.

It only ever supported drivers from the days of Windows XP and
Windows Server 2003 (i.e. NDIS 5.1). And even if one was actually
able to extract the .sys and .inf files from the driver package and
successfully convert them to a building module, which both were
adventures in itself, it could be any result when trying to run it,
depending on the card and driver, from resonably working to not
working, even crashing. But it did work for some cards, so it had
some limited merit in its time.

NetBSD removed it in 2018, FreeBSD in January 2021, so let's follow
suit now.

show more ...

etc/network.subr: enhance wlan initialization

Teach wlan_up() and wlan_down() to process just a single interface
passed as optional argument. If no argument is given, process all
"net.wlan.devices"

etc/network.subr: enhance wlan initialization

Teach wlan_up() and wlan_down() to process just a single interface
passed as optional argument. If no argument is given, process all
"net.wlan.devices" just like before.

Reviewed by: Aaron LI

show more ...

etc/network.subr: enhance wlan initialization

Introduce new functions wlan_get_unused() and wlan_is_parent(),
and extend wlan_up() to utilize them.

With this change, devices configured the traditio

etc/network.subr: enhance wlan initialization

Introduce new functions wlan_get_unused() and wlan_is_parent(),
and extend wlan_up() to utilize them.

With this change, devices configured the traditional way in rc.conf(5)
are created first, and then all other wireless interfaces are assigned
to next available wlan<index> devices automatically.

This allows either to have wlan configured manually in rc.conf(5) via
"wlans_<iface>" or to remove the static assignment and let devices be
auto-created. With dhcpcd_enable and wpa_supplicant_enable in rc.conf,
no further configuration is then needed to get network connectivity.

Furthermore, this will allow to enhance devd(8) default configuration,
so that also hot-pluggable wireless interfaces are automatically detected
and brought up (ie. assigned to wlan<index> devices).

Reviewed by: Aaron LI

show more ...

wpa_supplicant: Adjust master for the 2.9 upgrade.

- update README.DRAGONFLY and README.DELETED
- apply local modifications to contrib/wpa_supplicant
- adapt build to vendor update
- update manpages

wpa_supplicant: Adjust master for the 2.9 upgrade.

- update README.DRAGONFLY and README.DELETED
- apply local modifications to contrib/wpa_supplicant
- adapt build to vendor update
- update manpages wpa_cli(8), wpa_passphrase(8) and wpa_supplicant(8)
- update /etc/wpa_supplicant.conf

Adapt rc script:

- add is_wired_interface() and is_ndis_interface() to network.subr (taken
from FreeBSD)
- remove "security" warning
- don't consider DPorts wpa_supplicant anymore
- allow wpa_supplicant to be launched either for a single interface or in
interface matching mode, ie. single daemon handling multiple interfaces
- add wpa_supplicant_* variables to /etc/defaults/rc.conf

show more ...

network.subr: Workaround race between wpa_supplicant and dhcpcd

Insert a 1-second delay after starting wpa_supplicant(8) to workaround
the race between it and dhcpcd(8), which can modify the interfa

network.subr: Workaround race between wpa_supplicant and dhcpcd

Insert a 1-second delay after starting wpa_supplicant(8) to workaround
the race between it and dhcpcd(8), which can modify the interface's
state and break wpa_supplicant's ongoing SSID scan.

dhclient(8) doesn't have such an issue with wpa_supplicant.

Tested-by: me, Daniel Bilik <ddb@neosystem.org>

show more ...

Allow optional "inet6" keyword in ipv6_ifconfig_<ifname>

rc.d/netif: Rework wlan interface configuration

* wlan interfaces are more similar to clonable interfaces rather than
vlan interfaces, so move the relevant code from childif_create() to
network.

rc.d/netif: Rework wlan interface configuration

* wlan interfaces are more similar to clonable interfaces rather than
vlan interfaces, so move the relevant code from childif_create() to
network.subr as wlan_up(), which will be called to create the wlan
interfaces before setting up them.

Now, list_net_interfaces() shouldn't list "net.wlan.devices".

* Add the wlan_down() function in network.subr to destroy the wlan
devices.

* Meanwhile, fix childif_destroy() to properly destroy the vlan
interfaces created by childif_create(). Also tweak the order of this
function in netif_stop().

* The 2-second delay in netif_start() doesn't apply anymore, since the
DHCP and WPA configurations are now handled in ifconfig_up() called by
ifn_start().

This patch is loosely based on FreeBSD's code. Thanks to them.

show more ...

network.subr: Properly bring up/down interfaces

Now that the interface will be properly brought up in ifconfig_up(),
clean up the rc.d/wpa_supplicant script.

network.subr: Add IPv6 support to ifalias_{up,down}()

* Factor out the common parts of ifalias_{up,down}() to be
ifalias_common().
* Add IPv6 support to ifalias_common().
* Use ifalias_up() in net

network.subr: Add IPv6 support to ifalias_{up,down}()

* Factor out the common parts of ifalias_{up,down}() to be
ifalias_common().
* Add IPv6 support to ifalias_common().
* Use ifalias_up() in network6_interface_setup().

show more ...

network.subr: Clean up list_net_interfaces()

The rc.d/netif takes care of DHCP/non-DHCP interfaces appropriately, and
thus the interface type filter feature in list_net_interfaces() is no
longer nee

network.subr: Clean up list_net_interfaces()

The rc.d/netif takes care of DHCP/non-DHCP interfaces appropriately, and
thus the interface type filter feature in list_net_interfaces() is no
longer needed since long ago.

show more ...

network.subr: Cleanups and minor improvements

* Localize variables in all functions.
* Better name several variables (e.g., $i -> $_if).
* Simplify several test and case usages.
* Use the newly adde

network.subr: Cleanups and minor improvements

* Localize variables in all functions.
* Better name several variables (e.g., $i -> $_if).
* Simplify several test and case usages.
* Use the newly added "-n" option for ifconfig(8) in ifexists().
* Improve comments, debug messages, and styles.
* Print a message when calling rtsol(8) to auto configure an interface,
since it may take several seconds.

show more ...

rc: Use SYSCTL{,_N,_W} variables

With minor cleanups to IO redirections.

network.subr: Handle DHCP in ipv6_ifconfig_<ifname>

Commit 329743def50a061489debcd9682983235c8f5b42 allows to set
'ipv6_ifconfig_<ifname>="DHCP"' to tell dhcpcd(8) to configure DHCPv6
for interface

network.subr: Handle DHCP in ipv6_ifconfig_<ifname>

Commit 329743def50a061489debcd9682983235c8f5b42 allows to set
'ipv6_ifconfig_<ifname>="DHCP"' to tell dhcpcd(8) to configure DHCPv6
for interface <ifname>. However, the "DHCP" argument shouldn't be
passed to ifconfig(8). Handle this case by using 'ifconfig_getargs()'
in 'network6_interface_setup()'.

show more ...

rc.d: Introduce 'dhcp_client' to wrap over dhclient and dhcpcd

The new 'dhcp_client' rc script is a wrapper to start either dhclient(8)
or dhcpcd(8) based on the value of the 'dhcp_client' rc variab

rc.d: Introduce 'dhcp_client' to wrap over dhclient and dhcpcd

The new 'dhcp_client' rc script is a wrapper to start either dhclient(8)
or dhcpcd(8) based on the value of the 'dhcp_client' rc variable.

Other rc scripts are updated to depend on this wrapper instead of the
explicit 'dhclient'. This eases the migration from dhclient(8) to
dhcpcd(8) later.

Update rc.conf.5 and dhcp.8 man pages accordingly.

Meanwhile, remove the two obsolete variables 'dhcp_{program,flags}' from
/etc/rc.subr.

show more ...

network.subr: Support IPv6 in dhcpif()

Extend the 'dhcpif()' to support checking the interface needs DHCP for
IPv4-only, IPv6-only or either.

The 'dhcpcd' rc script in the following commit will use

network.subr: Support IPv6 in dhcpif()

Extend the 'dhcpif()' to support checking the interface needs DHCP for
IPv4-only, IPv6-only or either.

The 'dhcpcd' rc script in the following commit will use this new feature
to determine whether dhcpcd should do DHCPv4 or DHCPv6 or both.

show more ...

network.subr: Add ipv6if()

This function determines whether the given interface should be
configured for IPv6. This function will be used to determine whether to
apply DHCPv6 to an interface in the

network.subr: Add ipv6if()

This function determines whether the given interface should be
configured for IPv6. This function will be used to determine whether to
apply DHCPv6 to an interface in the following commit.

Taken from FreeBSD, but modified to consider ${ipv6_enable}.

show more ...

network.subr: Support IPv6 in ifconfig_getargs()

Update the 'ifconfig_getargs()' to accept the address family option
to support the extraction of IPv6 arguments of an interface, which
is configured

network.subr: Support IPv6 in ifconfig_getargs()

Update the 'ifconfig_getargs()' to accept the address family option
to support the extraction of IPv6 arguments of an interface, which
is configured using 'ipv6_ifconfig_<ifname>="..."'.

Obtained from FreeBSD; but FreeBSD uses 'ifconfig_<ifname>_ipv6'.

show more ...

Sync /etc/pccard_ether with FreeBSD

Our original 'pccard_ether' became unnecessarily complex as a big part of
the work is already implemented in 'network.subr', so just bring FreeBSD's
version over

Sync /etc/pccard_ether with FreeBSD

Our original 'pccard_ether' became unnecessarily complex as a big part of
the work is already implemented in 'network.subr', so just bring FreeBSD's
version over (with 'checkauto()' ignored as we don't support it).

NOTE: The 'pccard_ether' is still disabled by default on DragonFly.

show more ...

Remove faith(4) and faithd(8) from the tree.

FreeBSD did that 3 years ago (r274331). Quoting from their commit msg:

-----8<-----
It looks like industry have chosen different (and more traditional)

Remove faith(4) and faithd(8) from the tree.

FreeBSD did that 3 years ago (r274331). Quoting from their commit msg:

-----8<-----
It looks like industry have chosen different (and more traditional)
stateless/stateful NAT64 as translation mechanism. Last non-trivial
commits to both faith(4) and faithd(8) happened more than 12 years
ago, so I assume it is time to drop RFC3142 in FreeBSD.
----->8-----

Some more info here:

https://lists.freebsd.org/pipermail/freebsd-net/2014-October/040224.html

Discussed-with: sephe

show more ...

rc - Add unconfigured wifi interfaces to the netif list

* Use sysctl net.wlan.devices to get a list of wifi interfaces.
This sysctl is not yet active in master but will be when the wifi
update g

rc - Add unconfigured wifi interfaces to the netif list

* Use sysctl net.wlan.devices to get a list of wifi interfaces.
This sysctl is not yet active in master but will be when the wifi
update goes in (at which point the devices no longer show up in
ifconfig -l).

* This will allow existing wifi configurations in /etc/rc.conf to just
work with the upcoming update.

show more ...

network.subr - use get_if_var extensively

network.subr - move get_if_var here

Remove support for the IPX and NCP protocols, and for NWFS.

This was on the list for a longer time now. FreeBSD removed it
recently, too. Their commit msg has some more info:

"IPX was a network tra

Remove support for the IPX and NCP protocols, and for NWFS.

This was on the list for a longer time now. FreeBSD removed it
recently, too. Their commit msg has some more info:

"IPX was a network transport protocol in Novell's NetWare network
operating system from late 80s and then 90s. The NetWare itself
switched to TCP/IP as default transport in 1998. Later, in this
century the Novell Open Enterprise Server became successor of
Novell NetWare. The last release that claimed to still support
IPX was OES 2 in 2007. Routing equipment vendors (e.g. Cisco)
discontinued support for IPX in 2011."

The commit removes support for NCP (NetWare Core Protocol) and
NWFS (NetWare File System) along with it (both gone from FreeBSD
too since a while).

show more ...

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.

Make sure lo0 is brought up before any other interfaces to avoid problems
if network startup script is interrupted by user.