| #
a5615c90 |
| 28-Jun-2011 |
Peter Grehan <grehan@FreeBSD.org> |
IFC @ r222830
|
| #
81c02539 |
| 06-Jun-2011 |
Attilio Rao <attilio@FreeBSD.org> |
MFC
|
| #
9d94a468 |
| 06-Jun-2011 |
Bjoern A. Zeeb <bz@FreeBSD.org> |
Remove TODO which is not longer needed and the default.
|
| #
d7073a2b |
| 03-Jun-2011 |
Attilio Rao <attilio@FreeBSD.org> |
MFC
|
| #
d63d020e |
| 02-Jun-2011 |
Bjoern A. Zeeb <bz@FreeBSD.org> |
Write the multi step netconfig to a temporary file and only move that
to the final name if netconfig was completely finished. This fixes
reentrance problems even better than r222611.
Suggested by:
Write the multi step netconfig to a temporary file and only move that
to the final name if netconfig was completely finished. This fixes
reentrance problems even better than r222611.
Suggested by: nwhitehorn
Reviewed by: nwhitehorn
Sponsored by: The FreeBSD Foundation
Sponsored by: iXsystems
show more ...
|
| #
5b6ea0b5 |
| 31-May-2011 |
Attilio Rao <attilio@FreeBSD.org> |
MFC
|
| #
f07f97be |
| 30-May-2011 |
Bjoern A. Zeeb <bz@FreeBSD.org> |
Contrary to the rc.conf framework, when manualy enabling IPv6 we have
to -ifdiabled ourselves.
Sponsored by: The FreeBSD Foundation
Sponsored by: iXsystems
|
| #
2cdbac6c |
| 30-May-2011 |
Bjoern A. Zeeb <bz@FreeBSD.org> |
While doing it right for current configuration, fix the entry for rc.conf
adding the missing mandatory "inet6" keyword.
Sponsored by: The FreeBSD Foundation
Sponsored by: iXsystems
|
| #
7986af23 |
| 29-May-2011 |
Bjoern A. Zeeb <bz@FreeBSD.org> |
Split netconfig into three parts:
- netconfig - what auto will call which in turn will check for
IPv4 and IPv6 to be available and ask the user to configure it
by calling
- netconfig_ipv4 doing D
Split netconfig into three parts:
- netconfig - what auto will call which in turn will check for
IPv4 and IPv6 to be available and ask the user to configure it
by calling
- netconfig_ipv4 doing DHCP and static IPv4 addresses, and
- netconfig_ipv6 doing rtsol and static IPv6 addresses,
and then checking, querying and updating resolv.conf upon return.
Both DHCP and rtsol (in the future) might update resolv.conf already so
we seed ourselves from that file if available.
Reviewed by: nwhitehorn
Sponsored by: The FreeBSD Foundation
Sponsored by: iXsystems
show more ...
|