Date: Tue, 28 Aug 2001 19:05:37 +0900 (JST) From: Toshihiko ARAI <toshi@jp.FreeBSD.org> To: nate@yogotech.com (Nate Williams) Cc: freebsd-mobile@FreeBSD.org, imp@FreeBSD.org Subject: Re: Documentation for rc.conf's removable_interfaces? Message-ID: <200108281005.f7SA5bR50146.toshi@jp.FreeBSD.org> In-Reply-To: <15240.7812.511063.822660@nomad.yogotech.com> References: <15228.2988.181554.313833@nomad.yogotech.com> <200108200357.f7K3vMn18594.toshi@jp.FreeBSD.org> <15233.22136.524384.459698@nomad.yogotech.com> <200108211348.f7LDmTh30188.toshi@jp.FreeBSD.org> <15234.48176.6699.983659@nomad.yogotech.com> <200108231653.f7NGrO802605.toshi@jp.FreeBSD.org> <15237.14941.939157.115769@nomad.yogotech.com> <200108251732.f7PHWst26260.toshi@jp.FreeBSD.org> <15240.7812.511063.822660@nomad.yogotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
+ <15240.7812.511063.822660@nomad.yogotech.com>, Nate Williams wrote: >> I think that removable_interfaces is unnecessary really. However, I >> feel removable_route_flush useful. Of course you may change >> variable name to a fitter thing. > I agree. However, at this late in the game, the Release Engineer wanted > more documentation on the new variables, so it was easier to remove > non-documented variables than it was to make sure the new variables were > properly documentated. I understood it. >> When there is only one network interface to use simultaneously, >> we have only to add line of 'removable_route_flush=YES' to rc.conf. >> When a card was removed, all the old route is cleaned. In addition, >> so far this was action of default. > True. However, it doesn't hurt to leave this route in place if there is > only one network card, because there can only be one 'default_router' in > the current configuration setup. It is the truth in the simplest case, but we use more than one cards by a location (office, my home, etc...). Of course cards to use simultaneously are always one. In this case I can employ more than one default route by environment. I assume a situation as follows. A) ed1: static routing (non DHCP) ifconfig_ed1="inet 10.0.4.1 netmask 255.255.255.0" static_routes_ed1="net1 net2" route_net1="default 10.0.4.2" route_net2="-net 10.0.5 10.0.4.3" B) aue0: using DHCP ifconfig_aue0="DHCP" C) wi0: static routing ifconfig_wi0="inet 192.168.0.1 netmast 255.255.255.0" static_routes_wi0="net3" route_net3="default 192.168.0.2" and I prepare '/etc/start_if.wi0'. In this case, if I put 'removable_route_flush=YES', old route surely is eliminated including a case of DHCP. >> > In particular, in one situation, I have 2 network cards in my computer. >> > If one type of card is removed (my test network), the routes should not >> > be touched. However, if I remove/insert one the other cards (wireless >> > and/or ethernet for connection to the net), I need the route added >> > and/or removed. >> >> In this case you can use static_routes_<interface> for replacement >> of defaultrouter. This variable is the thing which I added anew, >> you replace it in real interface name and describe it in rc.conf as >> follows. > Good idea. I'm so used to hardcoding the default route on my desktop > boxes I never thought to modify the route. 'static_routes_<interface>' exists only with /etc/pccard_ether. 'static_routes' is usable in /etc/rc.network. > Very much agreed, but don't feel that it's solely your responsibility to > document everything. Old document exists, but it is a thing about PAO. Contents are considerably old, too. In addition, good translation is necessary. -- Toshihiko ARAI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108281005.f7SA5bR50146.toshi>