rede wireless e cabeada no notebook

alexsp
(usa Arch Linux)

Enviado em 03/09/2008 - 18:48h

quero ter os 2 configurados no meu notebook
por exemplo
tiro o cabo e automaticamente estou navegando na rede wireless e vice versa
sao 2 gateways
rede cabeada
192.168.1.7
255.255.255.0
gw 192.168.1.1

rede wireless
10.1.1.5
255.255.255.0
gw 10.1.1.1

_____________________________
configurei assim meu inet1.conf
____________________________

# /etc/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:
GATEWAY="192.168.1.1"
IPADDR[0]="192.168.1.7"
NETMASK[0]="255.255.255.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]=""

# 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 info. (You may not need all of these for your wireless network)
GATEWAY="10.1.1.1"
IFNAME[4]="wlan0"
IPADDR[4]="10.1.1.5"
NETMASK[4]="255.255.255.0"
#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]=nettux
#WLAN_MODE[4]=Managed
#WLAN_RATE[4]="54M auto"
#WLAN_CHANNEL[4]="auto"
#WLAN_KEY[4]="D5AD1F04ACF048EC2D0B1C80C7"
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=bad348910"
#WLAN_WPA[4]="wpa_supplicant"
#WLAN_WPADRIVER[4]="ndiswrapper"

## Some examples of additional network parameters that you can use.
## Config information for wlan0:
#IFNAME[4]="wlan0" # Use a different interface name nstead of
# the default 'eth4'
#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_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
#WLAN_ESSID[4]=DARKSTAR # Here, you can override _any_ parameter
# defined in rc.wireless.conf, by prepending
# 'WLAN_' to the parameter's name. Useful for
# those 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).

esta acontecento q quando estou navegando na rede wireless e desligo ela pra navegar pela rede c
abeada, a rede cabeada tenta sair pelo gateway da rede wireless

gesousa
(usa Ubuntu)

Enviado em 03/09/2008 - 19:42h

o que vc quer fazer é a redundancia das duas conexões:

Vários artigos aqui da vol já abordam este tema:
http://www.vivaolinux.com.br/artigo/Conexoes-redundantes-a-Internet-utilizando-Linux/?pagina=1
http://www.vivaolinux.com.br/artigo/Gerenciamento-de-conexoes?pagina=1

no seu caso olha a parte de roteamento para resolver seu problema, as conexoes deve está com a mesma prioridade no roteamento.

outro detalhe é quando vc desligar uma das redes ele usara a outra, vas se vc conectar ela de volta o kernel não descobrirá até vc reiniciar o roteamento ou pingar a interface que estava desligada para ataiva-la.