Две сетевые карты, безмониторный стартап.

Russian forum

Moderator: posixru

Post Reply
User avatar
Parafoil
Posts: 125
Joined: 18. Nov 2010, 18:50
Location: Krasnodar | Russia
Contact:

Две сетевые карты, безмониторный стартап.

Post by Parafoil »

В общем, ситуация такая.
Стоят две сетевые карты:
[eth0]
[eth1]
eth0 - подключена к сетке домена с DHCP-сервером.
eth0 - статический IP предоставления услуг интернета.
Проблема в том, что обе сетевые карты возможно поднять через wicd или ifconfig, но после перезагрузки ifconfig сбрасывается, а wicd поднимает последний выбор.
Поковырял rc.inet1.conf - там можно поднять интерфейсы с динамическим IP используя dhcpcd. Но для статического eth1 - DNSы перебиваются этим же самым dhcpcd.

В общем вопрос один:
Как поднять две сетевухи, где eth0 раздается по dhcp, а eth1 назначается статически со своими DNSами?
User avatar
laprjns
Salix Warrior
Posts: 1105
Joined: 28. Aug 2009, 01:30
Location: Connecticut USA

Re: Две сетевые карты, безмониторный стартап.

Post by laprjns »

Maybe by editing /etc/rc.d/rc.inet1.conf (Может быть, путем редактирования / etc/rc.d/rc.inet1.conf)
tc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").

# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.

# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.

# =============================================================================

# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""

# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""

# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""

# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""

# Default gateway IP address:
GATEWAY=""

# Change this to "yes" for debugging output to stdout. Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="no"

## Example config information for wlan0. Uncomment the lines you need and fill
## in your data. (You may not need all of these for your wireless network)
#IFNAME[4]="wlan0"
#IPADDR[4]=""
#NETMASK[4]=""
#USE_DHCP[4]="yes"
#DHCP_HOSTNAME[4]="icculus-wireless"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
#WLAN_ESSID[4]=DARKSTAR
#WLAN_MODE[4]=Managed
#WLAN_RATE[4]="54M auto"
#WLAN_CHANNEL[4]="auto"
#WLAN_KEY[4]="D5A31F54ACF0487C2D0B1C10D2"
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
#WLAN_WPA[4]="wpa_supplicant"
#WLAN_WPADRIVER[4]="wext"
#WLAN_WPAWAIT[4]=30

## Some examples of additional network parameters that you can use.
## Config information for wlan0:
#IFNAME[4]="wlan0" # Use a different interface name instead of
# the default 'eth4'
#IFNAME[4]="eth0:1" # Set up an IP alias.
#HWADDR[4]="00:01:23:45:67:89" # Overrule the card's hardware MAC address
#MTU[4]="" # The default MTU is 1500, but you might need
# 1360 when you use NAT'ed IPSec traffic.
#DHCP_TIMEOUT[4]=15 # The default timeout for the DHCP client to
# wait for server resonse is 10 seconds, but
# you might want a shorter or longer wait.
#DHCP_KEEPRESOLV[4]="yes" # If you dont want /etc/resolv.conf overwritten
#DHCP_KEEPNTP[4]="yes" # If you don't want ntp.conf overwritten
#DHCP_KEEPGW[4]="yes" # If you don't want the DHCP server to change
# your default gateway
#DHCP_IPADDR[4]="" # Request a specific IP address from the DHCP
# server
#DHCP_DEBUG[4]="yes" # Make dhcpcd show verbose diagnostics
#DHCP_NOIPV4LL[4]="yes" # Do not assign an ipv4ll address when a DHCP
# server is not found (ipv4ll link-local
# adresses in the IP range 169.254.0.0/16 are
# also known as "zeroconf" addresses)
#WLAN_ESSID[4]=DARKSTAR # An example of how you can override _any_
# parameter defined in rc.wireless.conf, by
# prepending 'WLAN_' to the parameter's name.
# Useful with multiple wireless interfaces.
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=thekey"
# Some drivers require a private ioctl to be
# set through the iwpriv command. If more than
# one is required, you can place them in the
# IWPRIV parameter (separated with the pipe (|)
# character, see the example).
#WLAN_WPA[4]="wpa_supplicant" # Run wpa_supplicant for WPA support
#WLAN_WPADRIVER[4]="ndiswrapper"# Tell wpa_supplicant to specifically use the
# ndiswrapper driver (if you leave this empty
# the 'wext' driver is used by default)
#WLAN_WPAWAIT[4]=30 # In case it takes long for the WPA association
# to finish, you can increase the wait time
# (defaults to 10 seconds)
“Don’t you see that the whole aim of Newspeak is to narrow the range of thought?"
User avatar
Parafoil
Posts: 125
Joined: 18. Nov 2010, 18:50
Location: Krasnodar | Russia
Contact:

Re: Две сетевые карты, безмониторный стартап.

Post by Parafoil »

Нет, не пойдет.
Например, если eth0 имеет динамические характеристики, то eth1 чисто статические полностью.
dhcpcd добавляет DNS адреса в файл, удаляя при этом статические значения для eth1.
В итоге, оба интерфейса используют одни DNS адреса на двоих, выданные dhcpcd.
Так же не настраивается шлюз для eth1.
Post Reply