| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Approved by: re (kib)
|
|
|
|
|
|
| |
interface configuration and before running network daemons.
Approved by: re (kib)
|
|
|
|
|
|
|
|
|
| |
as a symbolic link.
PR: conf/160711
Submitted by: Jase Thew
Approved by: re (kib)
MFC after: 1 week
|
|
|
|
|
| |
Reviewed by: bz
Approved by: re (kib)
|
|
|
|
|
|
|
| |
PR: 155984
Submitted by: gcooper
Approved by: re (kib)
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
of an IPv6 address. (r225489)
- Use eval for ${ifconfig_args} to fix an issue fixed in r223506. (r225489)
Approved by: re (bz)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(r225485). When setting an interface name to it, the following
configurations will be enabled:
1. "no_radr" is set to all IPv6 interfaces automatically.
2. "-no_radr accept_rtadv" will be set only for $ipv6_cpe_wanif. This is
done just before evaluating $ifconfig_IF_ipv6 in the rc.d scripts (this
means you can manually supersede this configuration if necessary).
3. The node will add RA-sending routers to the default router list
even if net.inet6.ip6.forwarding=1.
This mode is added to conform to RFC 6204 (a router which connects
the end-user network to a service provider network). To enable
packet forwarding, you still need to set ipv6_gateway_enable=YES.
Note that accepting router entries into the default router list when
packet forwarding capability and a routing daemon are enabled can
result in messing up the routing table. To minimize such unexpected
behaviors, "no_radr" is set on all interfaces but $ipv6_cpe_wanif.
Approved by: re (bz)
|
|
|
|
|
|
|
|
|
| |
- Update OpenBSD fingerprints through OpenBSD 4.9
- Fix typos.
Obtained from: OpenBSD
MFC after: 2 weeks
Approved by: re (kib)
|
|
|
|
|
|
| |
was not added at installation time.
Approved by: re (blackend)
|
|
|
|
|
| |
MFC after: 1 week
Approved by: re (kib)
|
|
|
|
|
|
| |
the _compat entries in the WITHOUT_NIS case rather then delete them.
Approved by: re (kib)
|
|
|
|
|
|
|
|
|
|
| |
comment out the NIS _compat options by default, but leave them in
the file for the convenience of users who want to enable it.
Update the comment in the file accordingly.
Reviewed by: ed
Approved by: re (hrs)
|
|
|
|
|
|
|
|
|
|
| |
We already modify various configuration files in /etc based on build
configuration. This is not done for nsswitch.conf right now when setting
WITHOUT_NIS. This breaks various utilities, including crond, that depend
on working databases.
Approved by: re (kib)
MFC after: 1 month
|
|
|
|
| |
Approved by: re (kib)
|
|
|
|
|
|
|
|
|
| |
Print a separate "Additional routing options" line for each address family
which has additional options, so that it does not get mixed up with the
output from adding routes.
This also reverts r224048 which added newlines to two arbitrary routing
options.
|
|
|
|
| |
our default empty zones. No functional changes.
|
|
|
|
| |
address for D.
|
|
|
|
| |
Reviewed by: dougb
|
|
|
|
|
|
| |
* Add HT40 entries for the two new Japan bands
* Fix a channel separation bug in one of the new bands I introduced
in a previous commit.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Specifics:
* add 4920MHz-4980MHz for 11a and 11n/HT20
* add 5040MHz-5080MHz for 11a and 11n/HT20
* add 5500MHz-5700MHz for 11a and 11n/HT20 (DFS needed)
* add 5500MHz-5680MHz for 11n/HT40 (DFS needed)
TODO:
* add correct HT40 bands for 4920-4980 and 5040-5080
For the curious:
There's been many revisions to the Japan regulatory rules.
Apparently, the requirements require old cards certified on a previous
version of the rules to obey the older rules, not the newer rules.
The regdomain.xml outlines the -current- restrictions.
The card driver (eg the ath_hal regulatory domain code) may include
previous revisions of the Japan rules.
The ath_hal regdomain code populates the initial channel list based on
what the EEPROM indicates is possible. The regdomain.xml database imposes
further restrictions on this.
So regdomain.xml only needs to have the -current- rules. If the card
was certified on an earlier set of JP rules, it may only support a subset
of those channels - these are calculated at device attach and this
restricted list is kicked to net80211. regdomain.xml operates on -this-
list of channels.
And thus, the correct regulatory behaviour for Japan is handled with only
one regdomain.xml Japan database entry.
(phew.)
Obtained from: Linux wireless-regdb
|
| |
|
|
|
|
|
|
|
|
| |
longer used by /etc/rc.d/nfsd and it is no longer necessary
to load the old nfs server by default, when nfs_server_enable="YES".
Tested by: sgk at troutmask.apl.washington.edu
Reviewed by: rc (Andrzej Tobola)
|
|
|
|
|
|
|
|
| |
the /etc/rc.d/nfsserver script to load the old nfs server
module.
Tested by: sgk at troutmask.apl.washington.edu
Reviewed by: rc (hrs)
|
|
|
|
|
|
|
|
| |
is correctly expanded inside stop_cmd instead of getting nothing.
PR: conf/157687
Reported by: Dmitry Banschikov <d.banschikov peterhost ru>
MFC after: 1 week
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
latter.
It appears that the addition to uath(4) came in through PR kern/135009,
which had tested another device, the SMCWUSBTG2, successfully with uath(4)
and included the SMCWUSBG as it "has the same chipset". I can find no
other evidence that these two do actually share the same chipset. Moreover,
Linux treats the SMCWUSBG as a zyd(4) device also.
This reverts r223537.
Discussed with: hselasky, kevlo
MFC after: 1 week
|
|
|
|
|
|
|
| |
antenna
gain; I believe net80211 doesn't take antenna gain into account and leaves it
up to the driver to enforce. (ath_hal(4) certainly tries to do this.)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The frequency range 5490MHz -> 5710MHz was opened up sometime in 2009, but
regdomain.xml wasn't updated.
FCC reference: (Section 15.407): http://louise.hallikainen.org/FCC/FccRules/2009/15/407/
The hole between 5600-5650MHz is due to a request from Airports using
a weather radar system which also utilises this range.
The GIT commit explaining this hole in more detail can be found here:
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-regdb.git;a=commit;h=fcbf9225d56e82d9a4e506187d42285e76d81523
|
| |
|
|
|
|
|
|
|
| |
- Rename bus_auto.conf into usb.conf
Requested by: imp @
MFC after: 14 days
|
|
|
|
|
|
|
| |
- Regenerate file after bugfix in the generator.
Suggested by: Jeremy Messenger
MFC after: 14 days
|
|
|
|
|
|
| |
- Update bus_auto.conf accordingly.
MFC after: 3 days
|
|
|
|
| |
MFC after: 14 days
|
|
|
|
|
|
|
|
|
|
|
|
| |
parameters accepting them (such as description, group).
Changes discussed on freebsd-rc.
PR: conf/156675
Reported by: "Alexander V. Chernikov" <melifaro att ipfw ru>
Suggested by: hrs
Analyzed with: Alexander V. Chernikov via IRC
MFC after: 2 weeks
|
| |
|
|
|
|
| |
Noticed-by: bschmidt@
|
|
|
|
| |
Noticed by: bschmidt@
|
|
|
|
|
| |
The FCC opened up this band sometime in 2009 (and ath was updated);
but regdomain.xml wasn't updated.
|
| |
|
| |
|
|
|
|
|
|
|
| |
network to become active.
PR: conf/151063
Submitted by: Jeremy Chadwick <freebsd@jdc.parodius.com>
|
| |
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
| |
This method is many times faster than doing it in /boot/loader.conf.
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the current sh, placing eval in a command substitution always results
in a fork(), even if it is the only command and only executes a single
simple command. Therefore, avoid it where it can be avoided easily.
Side effect: values starting with a hyphen and all whitespace are preserved.
The values are defaults and names for rc.conf variables and messages to be
given about obsolete ones.
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
This knob removes the tools that are exclusively used to view and
maintain the databases maintained by utmpx, namely last, users, who,
wtmpcvt, ac, lastlogin and utxrm.
The tool w is not in this list, because it has some other functionality
which is unrelated to utmpx; it is hardlinked to the uptime tool.
|
|
|
|
|
|
|
| |
The WITHOUT_ACCT switch is supposed to omit tools related to process
accounting, namely accton and sa. ac(8) is just a simple tool that
prints statistics based on data in the utx.log database. It has nothing
to do with the former.
|
|
|
|
|
| |
Approved by: kib (mentor)
MFC after: 3 days
|
|
|
|
|
|
| |
built to use the new sendmail-8.14.5/cf tree.
MFC after: 4 days
|