Bug 160549

Summary: [handbook] link aggreggation (lagg) page does not have any static IP examples and whether or not to use inet keyword is ambiguous
Product: Documentation Reporter: Peter Maloney <peter.maloney>
Component: Books & ArticlesAssignee: Brad Davis <brd>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Peter Maloney 2011-09-08 08:10:02 UTC
The link aggreggation (lagg) handbook page http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-aggregation.html does not have any static IP examples, and whether or not to use inet keyword is ambiguous.

This is a problem because many people would think to put the keyword "inet" before the IP address, as you would in other static IP situations.

For example, in this thread, the posters were using the inet keyword; I used their examples and tested, and it wasn't working until I removed the inet keyword. 
http://forums.freebsd.org/showthread.php?t=20263

Please add a static IP example, with a special note that the "inet" keyword should not be used.

Fix: 

You could just add a note to the end of "Example 31-2. Failover mode", something like this:

To use a static IP address, add it to the command like this:
# ifconfig lagg0 create
# ifconfig lagg0 up laggproto failover laggport fxp0 laggport fxp1 1.2.3.4 netmask 255.255.255.0

Where 1.2.3.4 is your static IPv4 address, and 255.255.255.0 is your netmask.
How-To-Repeat: Look in http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-aggregation.html to determine whether or not to use the "inet" keyword in specifying an ip address.
Comment 1 Brad Davis freebsd_committer freebsd_triage 2011-09-29 17:26:41 UTC
State Changed
From-To: open->closed

I just committed a fix for this. Unfortunately it was before I saw your PR.  


Comment 2 Brad Davis freebsd_committer freebsd_triage 2011-09-29 17:26:41 UTC
Responsible Changed
From-To: freebsd-doc->brd

I just committed a fix for this. Unfortunately it was before I saw your PR.