Re: [gentoo-user-ru] net.example

[Taz]

кардинальное решение - простыню сюда сувать.
хоть на пастебину бы кинул :)

On Wed, Feb 1, 2012 at 9:05 PM, marlboro <retaw@××××××.ru> wrote:

> 01.02.2012 23:00, Anton Ananich пишет:
> > Здравствуйте!
> >
> > У меня пропал файл /etc/conf.d/net.example (возможно давно, я просто не
> заметил)
> > Откуда его можно скачать?
> >
> > Спасибо,
> > Антон
>
> # For link bonding/trunking emerge net-misc/ifenslave
>
> # To bond interfaces together
> #slaves_bond0="eth0 eth1 eth2"
> #config_bond0=( "null" ) # You may not want to assign an IP the the bond
>
> # If any of the slaves require extra configuration - for example wireless
> or
> # ppp devices - we need to depend function on the bonded interfaces
> #RC_NEED_bond0="net.eth0 net.eth1"
>
>
>
> #-----------------------------------------------------------------------------
> # Classical IP over ATM
> # For CLIP support emerge net-dialup/linux-atm
>
> # Ensure that you have /etc/atmsigd.conf setup correctly
> # Now setup each clip interface like so
> #clip_atm0=( "peer_ip [if.]vpi.vci [opts]" ... )
> #  where "peer_ip" is the IP address of a PVC peer (in case of an ATM
> connection
> #  with your ISP, your only peer is usually the ISP gateway closest to
> you),
> #  "if" is the number of the ATM interface which will carry the PVC,
> "vpi.vci"
> #  is the ATM VC address, and "opts" may optionally specify VC
> parameters like
> #  qos, pcr, and the like (see "atmarp -s" for further reference).
> Please also
> #  note quoting: it is meant to distinguish the VCs you want to create.
> You may,
> #  in example, create an atm0 interface to more peers, like this:
> #clip_atm0=( "1.1.1.254 0.8.35" "1.1.1.253 1.8.35" )
>
> #  By default, the PVC will use the LLC/SNAP encapsulation. If you
> rather need a
> #  null encapsulation (aka "VC mode"), please add the keyword "null" to
> opts.
>
>
>
> #-----------------------------------------------------------------------------
> # PPP
> # For PPP support, emerge net-dialup/ppp
> # PPP is used for most dialup connections, including ADSL.
> # The older ADSL module is documented below, but you are encouraged to try
> # this module first.
> #
> # You need to create the PPP net script yourself. Make it like so
> #ln -s net.lo /etc/init.d/net.ppp0
> #
> # We have to instruct ppp0 to actually use ppp
> #config_ppp0=( "ppp" )
> #
> # Each PPP interface requires an interface to use as a "Link"
> #link_ppp0="/dev/ttyS0"                 # Most PPP links will use a serial
> port
> #link_ppp0="eth0"                       # PPPoE requires an ethernet
> interface
> #link_ppp0="[itf.]vpi.vci"              # PPPoA requires the ATM VC's
> address
> #link_ppp0="/dev/null"                  # ISDN links should have this
> #link_ppp0="pty 'your_link_command'"    # PPP links over ssh, rsh, etc
> #
> # Here you should specify what pppd plugins you want to use
> # Available plugins are: pppoe, pppoa, capi, dhcpc, minconn, radius,
> #                        radattr, radrealms and winbind
> #plugins_ppp0=(
> #       "pppoe"                         # Required plugin for PPPoE
> #       "pppoa vc-encaps"               # Required plugin for PPPoA with
> an option
> #       "capi"                          # Required plugin for ISDN
> #)
> #
> # PPP requires at least a username. You can optionally set a password
> here too
> # If you don't, then it will use the password specified in
> /etc/ppp/*-secrets
> # against the specified username
> #username_ppp0='user'
> #password_ppp0='password'
> # NOTE: You can set a blank password like so
> #password_ppp0=
> #
> # The PPP daemon has many options you can specify - although there are many
> # and may seem daunting, it is recommended that you read the pppd man page
> # before enabling any of them
> #pppd_ppp0=(
> #       "maxfail 0"     # WARNING: It's not recommended you use this
> #                       # if you don't specify maxfail then we assume 0
> #       "updetach"      # If not set, "/etc/init.d/net.ppp0 start" will
> return
> #                       # immediately,  without waiting the link to come up
> #                       # for the first time.
> #                       # Do not use it for dial-on-demand links!
> #       "debug"         # Enables syslog debugging
> #       "noauth"        # Do not require the peer to authenticate itself
> #       "defaultroute"  # Make this PPP interface the default route
> #       "usepeerdns"    # Use the DNS settings provided by PPP
> #
> # On demand options
> #       "demand"                # Enable dial on demand
> #       "idle 30"               # Link goes down after 30 seconds of
> inactivity
> #       "10.112.112.112:10.112.112.113" # Phony IP addresses
> #       "ipcp-accept-remote"    # Accept the peers idea of remote address
> #       "ipcp-accept-local"     # Accept the peers idea of local address
> #       "holdoff 3"     # Wait 3 seconds after link dies before re-starting
> #
> # Dead peer detection
> #       "lcp-echo-interval 15"  # Send a LCP echo every 15 seconds
> #       "lcp-echo-failure 3"    # Make peer dead after 3 consective
> #                               # echo-requests
> #
> # Compression options - use these to completely disable compression
> #       noaccomp noccp nobsdcomp nodeflate nopcomp novj novjccomp
> #
> # Dial-up settings
> #       "lock"                          # Lock serial port
> #       "115200"                        # Set the serial port baud rate
> #       "modem crtscts"                 # Enable hardware flow control
> #       "192.168.0.1:192.168.0.2"       # Local and remote IP addresses
> #)
> #
> # Dial-up PPP users need to specify at least one telephone number
> #phone_number_ppp0=( "12345689" ) # Maximum 2 phone numbers are supported
> # They will also need a chat script - here's a good one
> #chat_ppp0=(
> #       'ABORT' 'BUSY'
> #       'ABORT' 'ERROR'
> #       'ABORT' 'NO ANSWER'
> #       'ABORT' 'NO CARRIER'
> #       'ABORT' 'NO DIALTONE'
> #       'ABORT' 'Invalid Login'
> #       'ABORT' 'Login incorrect'
> #       'TIMEOUT' '5'
> #       '' 'ATZ'
> #       'OK' 'AT' # Put your modem initialization string here
> #       'OK' 'ATDT\T'
> #       'TIMEOUT' '60'
> #       'CONNECT' ''
> #       'TIMEOUT' '5'
> #       '~--' ''
> #)
>
> # If the link require extra configuration - for example wireless or
> # RFC 268 bridge - we need to depend on the bridge so they get
> # configured correctly.
> #RC_NEED_ppp0="net.nas0"
>
> #WARNING: if MTU of the PPP interface is less than 1500 and you use this
> #machine as a router, you should add the following rule to your firewall
> #
> #iptables -I FORWARD 1 -p tcp --tcp-flags SYN,RST SYN -j TCPMSS
> --clamp-mss-to-pmtu
>
>
> #-----------------------------------------------------------------------------
> # ADSL
> # For ADSL support, emerge net-dialup/rp-pppoe
> # WARNING: This ADSL module is being deprecated in favour of the PPP module
> # above.
> # You should make the following settings and also put your
> # username/password information in /etc/ppp/pap-secrets
>
> # Configure the interface to use ADSL
> #config_eth0=( "adsl" )
>
> # You probably won't need to edit /etc/ppp/pppoe.conf if you set this
> #adsl_user_eth0="my-adsl-username"
>
>
> #-----------------------------------------------------------------------------
> # ISDN
> # For ISDN support, emerge net-dialup/isdn4k-utils
> # You should make the following settings and also put your
> # username/password information in /etc/ppp/pap-secrets
>
> # Configure the interface to use ISDN
> #config_ippp0=( "dhcp" )
> # It's important to specify dhcp if you need it!
> #config_ippp0=( "192.168.0.1/24" )
> # Otherwise, you can use a static IP
>
> # NOTE: The interface name must be either ippp or isdn followed by a number
>
> # You may need this option to set the default route
> #ipppd_eth0="defaultroute"
>
>
> #-----------------------------------------------------------------------------
> # MAC changer
> # To set a specific MAC address
> #mac_eth0="00:11:22:33:44:55"
>
> # For changing MAC addresses using the below, emerge
> net-analyzer/macchanger
> # - to randomize the last 3 bytes only
> #mac_eth0="random-ending"
> # - to randomize between the same physical type of connection (e.g. fibre,
> # copper, wireless) , all vendors
> #mac_eth0="random-samekind"
> # - to randomize between any physical type of connection (e.g. fibre,
> copper,
> # wireless) , all vendors
> #mac_eth0="random-anykind"
> # - full randomization - WARNING: some MAC addresses generated by this
> may NOT
> # act as expected
> #mac_eth0="random-full"
> # custom - passes all parameters directly to net-analyzer/macchanger
> #mac_eth0="some custom set of parameters"
>
> # You can also set other options based on the MAC address of your
> network card
> # Handy if you use different docking stations with laptops
> #config_001122334455=( "dhcp" )
>
>
> #-----------------------------------------------------------------------------
> # TUN/TAP
> # For TUN/TAP support emerge net-misc/openvpn or
> sys-apps/usermode-utilities
> #
> # You must specify if we're a tun or tap device. Then you can give it any
> # name you like - such as vpn
> #tuntap_vpn="tun"
> #config_vpn=( "192.168.0.1/24")
>
> # Or stick wit the generic names - like tap0
> #tuntap_tap0="tap"
> #config_tap0=( "192.168.0.1/24")
>
> # For passing custom options to tunctl use something like the following.
>  This
> # example sets the owner to adm
> #tunctl_tun1="-u adm"
> # When using openvpn, there are no options
>
>
> #-----------------------------------------------------------------------------
> # Bridging (802.1d)
> # For bridging support emerge net-misc/bridge-utils
>
> # To add ports to bridge br0
> #bridge_br0="eth0 eth1"
> # or dynamically add them when the interface comes up
> #bridge_add_eth0="br0"
> #bridge_add_eth1="br0"
>
> # You need to configure the ports to null values so dhcp does not get
> started
> #config_eth0=( "null" )
> #config_eth1=( "null" )
>
> # Finally give the bridge an address - dhcp or a static IP
> #config_br0=( "dhcp" ) # may not work when adding ports dynamically
> #config_br0=( "192.168.0.1/24" )
>
> # If any of the ports require extra configuration - for example wireless or
> # ppp devices - we need to depend on them like so.
> #RC_NEED_br0="net.eth0 net.eth1"
>
> # Below is an example of configuring the bridge
> # Consult "man brctl" for more details
> #brctl_br0=( "setfd 0" "sethello 0" "stp off" )
>
>
> #-----------------------------------------------------------------------------
> # RFC 2684 Bridge Support
> # For RFC 2684 bridge support emerge net-misc/br2684ctl
>
> # Interface names have to be of the form nas0, nas1, nas2, etc.
> # You have to specify a VPI and VCI for the interface like so
> #br2684ctl_nas0="-a 0.38" # UK VPI and VCI
>
> # You may want to configure the encapsulation method as well by adding
> the -e
> # option to the command above (may need to be before the -a command)
> # -e 0 # LLC (default)
> # -e 1 # VC mux
>
> # Then you can configure the interface as normal
> #config_nas0=( "192.168.0.1/24" )
>
>
> #-----------------------------------------------------------------------------
> # Tunnelling
> # WARNING: For tunnelling it is highly recommended that you
> # emerge sys-apps/iproute2
> #
> # For GRE tunnels
> #iptunnel_vpn0="mode gre remote 207.170.82.1 key 0xffffffff ttl 255"
>
> # For IPIP tunnels
> #iptunnel_vpn0="mode ipip remote 207.170.82.2 ttl 255"
>
> # To configure the interface
> #config_vpn0=( "192.168.0.2 pointopoint 192.168.1.2" )  # ifconfig style
> #config_vpn0=( "192.168.0.2 peer 192.168.1.1" )         # iproute2 style
>
> # 6to4 Tunnels allow IPv6 to work over IPv4 addresses, provided you
> # have a non-private address configured on an interface.
> # link_6to4="eth0"              # Interface to base it's addresses on
> # config_6to4=( "ip6to4" )
> # You may want to depend on eth0 like so
> #RC_NEED_6to4="net.eth0"
> # To ensure that eth0 is configured before 6to4. Of course, the tunnel
> could be
> # any name and this also works for any configured interface.
> # NOTE: If you're not using iproute2 then your 6to4 tunnel has to be called
> # sit0 - otherwise use a different name like 6to4 in the example above.
>
>
>
> #-----------------------------------------------------------------------------
> # System
> # For configuring system specifics such as domain, dns, ntp and nis servers
> # It's rare that you would need todo this, but you can anyway.
> # This is most benefit to wireless users who don't use DHCP so they can
> change
> # their configs based on ESSID. See wireless.example for more details
>
> # To use dns settings such as these, dns_servers_eth0 must be set!
> # If you omit the _eth0 suffix, then it applies to all interfaces unless
> # overridden by the interface suffix.
> #dns_domain_eth0="your.domain"
> #dns_servers_eth0="192.168.0.2 192.168.0.3"
> #dns_search_eth0="this.domain that.domain"
> #dns_options_eth0=( "timeout 1" "rotate" )
> #dns_sortlist_eth0="130.155.160.0/255.255.240.0 130.155.0.0"
> # See the man page for resolv.conf for details about the options and
> sortlist
> # directives
>
> #ntp_servers_eth0="192.168.0.2 192.168.0.3"
>
> #nis_domain_eth0="domain"
> #nis_servers_eth0="192.168.0.2 192.168.0.3"
>
> # NOTE: Setting any of these will stamp on the files in question. So if you
> # don't specify dns_servers but you do specify dns_domain then no
> nameservers
> # will be listed in /etc/resolv.conf even if there were any there to start
> # with.
> # If this is an issue for you then maybe you should look into a resolv.conf
> # manager like resolvconf-gentoo to manage this file for you. All packages
> # that baselayout supports use resolvconf-gentoo if installed.
>
>
> #-----------------------------------------------------------------------------
> # Cable in/out detection
> # Sometimes the cable is in, others it's out. Obviously you don't want to
> # restart net.eth0 every time when you plug it in either.
> #
> # netplug is a package that detects this and requires no extra
> configuration
> # on your part.
> # emerge sys-apps/netplug
> # or
> # emerge sys-apps/ifplugd
> # and you're done :)
>
> # By default we don't wait for netplug/ifplugd to configure the interface.
> # If you would like it to wait so that other services now that network is
> up
> # then you can specify a timeout here.
> #plug_timeout="10"
> # A value of 0 means wait forever.
>
> # If you don't want to use netplug on a specific interface but you have it
> # installed, you can disable it for that interface via the modules
> statement
> #modules_eth0=( "!netplug" )
> # You can do the same for ifplugd
> #
> # You can disable them both with the generic plug
> #modules_eth0=( "!plug" )
>
> # To use specific ifplugd options, fex specifying wireless mode
> #ifplugd_eth0="--api-mode=wlan"
> # man ifplugd for more options
>
>
> ##############################################################################
> # ADVANCED CONFIGURATION
> #
> # Four functions can be defined which will be called surrounding the
> # start/stop operations.  The functions are called with the interface
> # name first so that one function can control multiple adapters. An
> extra two
> # functions can be defined when an interface fails to start or stop.
> #
> # The return values for the preup and predown functions should be 0
> # (success) to indicate that configuration or deconfiguration of the
> # interface can continue.  If preup returns a non-zero value, then
> # interface configuration will be aborted.  If predown returns a
> # non-zero value, then the interface will not be allowed to continue
> # deconfiguration.
> #
> # The return values for the postup, postdown, failup and faildown
> functions are
> # ignored since there's nothing to do if they indicate failure.
> #
> # ${IFACE} is set to the interface being brought up/down
> # ${IFVAR} is ${IFACE} converted to variable name bash allows
>
> #preup() {
> #       # Test for link on the interface prior to bringing it up.  This
> #       # only works on some network adapters and requires the mii-diag
> #       # package to be installed.
> #       if mii-tool "${IFACE}" 2> /dev/null | grep -q 'no link'; then
> #               ewarn "No link on ${IFACE}, aborting configuration"
> #               return 1
> #       fi
> #
> #       # Test for link on the interface prior to bringing it up.  This
> #       # only works on some network adapters and requires the ethtool
> #       # package to be installed.
> #       if ethtool "${IFACE}" | grep -q 'Link detected: no'; then
> #               ewarn "No link on ${IFACE}, aborting configuration"
> #               return 1
> #       fi
> #
> #
> #       # Remember to return 0 on success
> #       return 0
> #}
>
> #predown() {
> #       # The default in the script is to test for NFS root and disallow
> #       # downing interfaces in that case.  Note that if you specify a
> #       # predown() function you will override that logic.  Here it is, in
> #       # case you still want it...
> #       if is_net_fs /; then
> #               eerror "root filesystem is network mounted -- can't stop
> ${IFACE}"
> #               return 1
> #       fi
> #
> #       # Remember to return 0 on success
> #       return 0
> #}
>
> #postup() {
> #       # This function could be used, for example, to register with a
> #       # dynamic DNS service.  Another possibility would be to
> #       # send/receive mail once the interface is brought up.
>
> #       # Here is an example that allows the use of iproute rules
> #       # which have been configured using the rules_eth0 variable.
> #       #rules_eth0=(
> #       #       "from 24.80.102.112/32 to 192.168.1.0/24 table localnet
> priority 100"
> #       #       "from 216.113.223.51/32 to 192.168.1.0/24 table localnet
> priority 100"
> #       #)
> #       local x="rules_${IFVAR}[@]"
> #       local -a rules=( "${!x}" )
> #       if [[ -n ${rules} ]] ; then
> #               einfo "Adding IP policy routing rules"
> #               eindent
> #               # Ensure that the kernel supports policy routing
> #               if ! ip rule list | grep -q "^" ; then
> #                       eerror "You need to enable IP Policy Routing
> (CONFIG_IP_MULTIPLE_TABLES)"
> #                       eerror "in your kernel to use ip rules"
> #               else
> #                       for x in "${rules[@]}" ; do
> #                               ebegin "${x}"
> #                               ip rule add ${x}
> #                               eend $?
> #                       done
> #               fi
> #               eoutdent
> #               # Flush the cache
> #               ip route flush cache dev "${IFACE}"
> #       fi
>
> #}
>
> #postdown() {
> #       # Enable Wake-On-LAN for every interface except for lo
> #       # Probably a good idea to set RC_DOWN_INTERFACE="no" in
> /etc/conf.d/rc
> #       # as well ;)
> #       [[ ${IFACE} != "lo" ]] && ethtool -s "${IFACE}" wol g
>
> #       Automatically erase any ip rules created in the example postup
> above
> #       if interface_exists "${IFACE}" ; then
> #               # Remove any rules for this interface
> #               local rule
> #               ip rule list | grep " iif ${IFACE}[ ]*" | {
> #                       while read rule ; do
> #                               rule="${rule#*:}"
> #                               ip rule del ${rule}
> #                       done
> #               }
> #               # Flush the route cache
> #               ip route flush cache dev "${IFACE}"
> #       fi
>
> #       # Return 0 always
> #       return 0
> #}
>
> #failup() {
> #       # This function is mostly here for completeness... I haven't
> #       # thought of anything nifty to do with it yet ;-)
> #}
>
> #faildown() {
> #       # This function is mostly here for completeness... I haven't
> #       # thought of anything nifty to do with it yet ;-)
> #}
>
>
> ##############################################################################
> # FORCING MODULES
> # The Big Fat Warning :- If you use module forcing do not complain to us or
> # file bugs about it not working!
> #
> # Loading modules is a slow affair - we have to check each one for the
> following
> # 1) Code sanity
> # 2) Has the required package been emerged?
> # 3) Has it modified anything?
> # 4) Have all the dependant modules been loaded?
>
> # Then we have to strip out the conflicting modules based on user
> preference
> # and default configuration and sort them into the correct order.
> # Finally we check the end result for dependencies.
>
> # This, of course, takes valuable CPU time so we provide module forcing as
> a
> # means to speed things up. We still do *some* checking but not much.
>
> # It is essential that you force modules in the correct order and supply
> all
> # the modules you need. You must always supply an interface module - we
> # supply ifconfig or iproute2.
>
> # The Big Fat Warning :- If you use module forcing do not complain to us or
> # file bugs about it not working!
>
> # Now that we've warned you twice, here's how to do it
> #modules_force=( "ifconfig" )
> #modules_force=( "iproute2" "dhcpcd" )
>
> # We can also apply this to a specific interface
> #modules_force_eth1=( "iproute2" )
>
> # The below will not work
> #modules_force=( "dhcpcd" )
> # No interface (ifconfig/iproute2)
> #modules_force=( "ifconfig" "essidnet" "iwconfig" )
> # Although it will not crash, essidnet will not work as it has to come
> after
> # iwconfig
> #modules_force=( "iproute2" "ifconfig" )
> # The interface will be setup twice which will cause problems
>
>