Copyright © 2008, 2009 The FreeBSD Documentation Project
$FreeBSD: stable/7/release/doc/en_US.ISO8859-1/errata/article.sgml
-186755 2009-01-05 03:50:04Z hrs $
+186763 2009-01-05 08:33:56Z hrs $
[20090105] The Release Notes for 7.1-RELEASE should have mentioned changes that the get_setaffinity() should have been sched_setaffinity().
[20090105] The Release Notes for 7.1-RELEASE should have mentioned changes that the jme(4) driver has +been added to provide support for PCIe adapters based on JMicron JMC250 gigabit Ethernet +and JMC260 fast Ethernet controllers.
-No news.
+[20090105] The Release Notes for 7.1-RELEASE should have mentioned changes that the age(4) driver has +been added to provide support for Attansic/Atheros L1 gigabit Ethernet controller.
+ +[20090105] The Release Notes for 7.1-RELEASE should have mentioned changes that the +malo(4) driver +has been added to provide support for Marvell Libertas 88W8335 based PCI network +adapters.
+ +[20090105] The Release Notes for 7.1-RELEASE should have mentioned changes that the +bm(4) driver has been added to provide support for Apple Big Mac (BMAC) Ethernet +controller, found on various Apple G3 models.
+ +[20090105] The Release Notes for 7.1-RELEASE should have mentioned changes that the +et(4) driver has been added to provide support for Agere ET1310 10/100/Gigabit Ethernet +controller.
+ +[20090105] The Release Notes for 7.1-RELEASE should have mentioned changes that the +glxsb(4) driver +has been added to provide support for the Security Block in AMD Geode LX processors.
+ +[20090105] The Release Notes for 7.1-RELEASE should have mentioned that FreeBSD now +supports multiple routing tables. To enable this, the following steps are needed:
+ +Add the following kernel configuration option and rebuild the kernel. The 2 is the number of FIB (the maximum value is 16).
+ ++options ROUTETABLES=2 ++ +
The procedure for rebuilding the FreeBSD kernel is described in the FreeBSD Handbook.
+ +This number can be modified on boot time. To do so, add the following to /boot/loader.conf and reboot the system:
+ ++net.fibs=6 ++
Set a loader tunable net.my_fibnum if needed. This means
+the default number of routing tables. If not specified, 0 will
+be used.
Set a loader tunable net.add_addr_allfibs if needed. This
+enables to add routes to all FIBs for new interfaces by default. When this is set to 0, it will only allocate routes on interface changes for the FIB of
+the caller when adding a new set of addresses to an interface. Note that this tunable is
+set to 1 by default.
To select one of the FIBs, the new +setfib(1) +utility can be used. This set an associated FIB with the process. For example:
+ ++# setfib -3 ping target.example.com ++ +
The FIB #3 will be used for the +ping(8) +command.
+ +The FIB which the packet will be associated with will be determined in the following +rules:
+ +All packets which have a FIB associated with them will use the FIB. If not, FIB #0 +will be used.
+A packet received on an interface for forwarding uses FIB #0.
+A TCP listen socket associated with an FIB will generate accept sockets which are +associated with the same FIB.
+A packet generated in response to other packet uses the FIB associated with the packet +being responded to.
+A packet generated on tunnel interfaces such as gif(4) and tun(4) will be +encapsulated using the FIB of the process which set up the tunnel.
+Routing messages will be associated with the process's FIB.
+Also, the +ipfw(8) now +supports an action rule setfib. The following action:
+ ++setfib fibnum ++ +
will make the matched packet use the FIB specified in fibnum. The rule processing continues at the next +rule.