| #
ad2571a2 |
| 18-Jul-2011 |
Bjoern A. Zeeb <bz@FreeBSD.org> |
If compiling RESCUE always ignore feature_present(3) calls so that a /rescue/ifconfig more modern than the kernel could still configure IPv4 or IPv6 addresses.
Reported by: Andrzej Tobola (ato iem.p
If compiling RESCUE always ignore feature_present(3) calls so that a /rescue/ifconfig more modern than the kernel could still configure IPv4 or IPv6 addresses.
Reported by: Andrzej Tobola (ato iem.pw.edu.pl) Reported by: gcooper MFC after: 1 day X-MFC: will not MFC any time soon, just reminder for r222527
show more ...
|
| #
a5615c90 |
| 28-Jun-2011 |
Peter Grehan <grehan@FreeBSD.org> |
IFC @ r222830
|
| #
61b92692 |
| 31-May-2011 |
Attilio Rao <attilio@FreeBSD.org> |
MFC
|
| #
5af3fa9a |
| 31-May-2011 |
Bjoern A. Zeeb <bz@FreeBSD.org> |
Conditionally compile in the af_inet and af_inet6, af_nd6 modules. If compiled in for dual-stack use, test with feature_present(3) to see if we should register the IPv4/IPv6 address family related op
Conditionally compile in the af_inet and af_inet6, af_nd6 modules. If compiled in for dual-stack use, test with feature_present(3) to see if we should register the IPv4/IPv6 address family related options.
In case there is no "inet" support we would love to go with the usage() and make the address family mandatory (as it is for anything but inet in theory). Unfortunately people are used to ifconfig IF up/down etc. as well, so use a fallback of "link". Adjust the man page to reflect these minor details.
Improve error handling printing a warning in addition to the usage telling that we do not know the given address family in two places.
Reviewed by: hrs, rwatson Sponsored by: The FreeBSD Foundation Sponsored by: iXsystems MFC after: 2 weeks
show more ...
|
|
Revision tags: release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0 |
|
| #
1a0fda2b |
| 04-Mar-2010 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
IFH@204581
|
| #
40efe37e |
| 14-Jan-2010 |
Ed Maste <emaste@FreeBSD.org> |
Reject invalid CIDR widths rather than silently stopping at the first non-digit character.
Due to an issue with rc(8) in a test configuration, ifconfig was being invoked with the address used again
Reject invalid CIDR widths rather than silently stopping at the first non-digit character.
Due to an issue with rc(8) in a test configuration, ifconfig was being invoked with the address used again as the width - for example,
ifconfig vlan0 10.0.0.1/10.0.0.1
Prior to this change, that address/width would be interpreted as 10.0.0.1/10.
show more ...
|
|
Revision tags: release/8.0.0_cvs, release/8.0.0 |
|
| #
10b3b545 |
| 17-Sep-2009 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
Merge from head
|
| #
09c817ba |
| 03-Jul-2009 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
- MFC
|
| #
b59dcaee |
| 24-Jun-2009 |
Xin LI <delphij@FreeBSD.org> |
- Use size_t instead of int when appropriate; - Use C99 sparse initialization.
With these changes ifconfig(8) is WARNS=2 clean.
|
| #
e7153b25 |
| 07-May-2009 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
Merge from HEAD
|
|
Revision tags: release/7.2.0_cvs, release/7.2.0 |
|
| #
7e820087 |
| 15-Apr-2009 |
Brooks Davis <brooks@FreeBSD.org> |
The structs ifaliasreq and in_aliasreq have exactly the same layout and member names, but we really do mean to use in_aliasreq here.
MFC after: 1 week
|
|
Revision tags: release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0 |
|
| #
cb8c905a |
| 25-Feb-2007 |
Sam Leffler <sam@FreeBSD.org> |
use getifaddrs from libc instead of private code
Reviewed by: bms MFC after: 1 month
|
|
Revision tags: release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0 |
|
| #
73bbc449 |
| 16-Jun-2005 |
Hajimu UMEMOTO <ume@FreeBSD.org> |
only show a tunnel information of an adequate address family.
Approved by: re (dwhite)
|
|
Revision tags: release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0 |
|
| #
5faf8dcb |
| 08-Dec-2004 |
Sam Leffler <sam@FreeBSD.org> |
Overhaul to cleanup some of the tangled logic that's grown over the years.
o break per-address family support out into separate files o modularize per-address family and functional operations using
Overhaul to cleanup some of the tangled logic that's grown over the years.
o break per-address family support out into separate files o modularize per-address family and functional operations using a registration mechanism; this permits configuration according to which files you include (but beware that order of the files is important to insure backwards compatibility) o many cleanups to eliminate incestuous behaviour, global variables, and poor coding practices (still much more to fix)
The original motivation of this work was to support dynamic addition of functionality based on the interface so we can eliminate the various little control programs and so that vendors can distribute ifconfig plugins that support their in-kernel code. That work is still to be completed.
o Update 802.11 support for all the new net80211 functionality; some of these operations (e.g. list *) may be better suited in a different program
show more ...
|
| #
40efe37e |
| 14-Jan-2010 |
Ed Maste <emaste@FreeBSD.org> |
Reject invalid CIDR widths rather than silently stopping at the first non-digit character.
Due to an issue with rc(8) in a test configuration, ifconfig was being invoked with the address used again
Reject invalid CIDR widths rather than silently stopping at the first non-digit character.
Due to an issue with rc(8) in a test configuration, ifconfig was being invoked with the address used again as the width - for example,
ifconfig vlan0 10.0.0.1/10.0.0.1
Prior to this change, that address/width would be interpreted as 10.0.0.1/10.
show more ...
|
| #
09c817ba |
| 03-Jul-2009 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
- MFC
|
| #
b59dcaee |
| 24-Jun-2009 |
Xin LI <delphij@FreeBSD.org> |
- Use size_t instead of int when appropriate; - Use C99 sparse initialization.
With these changes ifconfig(8) is WARNS=2 clean.
|
| #
e7153b25 |
| 07-May-2009 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
Merge from HEAD
|
|
Revision tags: release/7.2.0_cvs, release/7.2.0 |
|
| #
7e820087 |
| 15-Apr-2009 |
Brooks Davis <brooks@FreeBSD.org> |
The structs ifaliasreq and in_aliasreq have exactly the same layout and member names, but we really do mean to use in_aliasreq here.
MFC after: 1 week
|
|
Revision tags: release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0 |
|
| #
cb8c905a |
| 25-Feb-2007 |
Sam Leffler <sam@FreeBSD.org> |
use getifaddrs from libc instead of private code
Reviewed by: bms MFC after: 1 month
|
|
Revision tags: release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0 |
|
| #
73bbc449 |
| 16-Jun-2005 |
Hajimu UMEMOTO <ume@FreeBSD.org> |
only show a tunnel information of an adequate address family.
Approved by: re (dwhite)
|
|
Revision tags: release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0 |
|
| #
5faf8dcb |
| 08-Dec-2004 |
Sam Leffler <sam@FreeBSD.org> |
Overhaul to cleanup some of the tangled logic that's grown over the years.
o break per-address family support out into separate files o modularize per-address family and functional operations using
Overhaul to cleanup some of the tangled logic that's grown over the years.
o break per-address family support out into separate files o modularize per-address family and functional operations using a registration mechanism; this permits configuration according to which files you include (but beware that order of the files is important to insure backwards compatibility) o many cleanups to eliminate incestuous behaviour, global variables, and poor coding practices (still much more to fix)
The original motivation of this work was to support dynamic addition of functionality based on the interface so we can eliminate the various little control programs and so that vendors can distribute ifconfig plugins that support their in-kernel code. That work is still to be completed.
o Update 802.11 support for all the new net80211 functionality; some of these operations (e.g. list *) may be better suited in a different program
show more ...
|