Configurar 2 placas de red a 2 redes distintas
Estimados:
Vuelvo al ataque con un problema que es evidente no puedo resolver por
mí mismo.
Paso a explicar.
Tengo una computadora como terminal, con dos placas de red conectada a
dos redes distintas.
No es mi intención convertirla a un router, si no poder acceder a las
dos redes.
eth0 está conectada a una red empresarial 10.0.0.0/24, a un servidor
MS-Win2003 que hace las veces de router. No tengo forma de tocar dicho
aparato, por lo que lo debo tomar como está.
eth3 está conectada a una switch/router con salida a internet
192.168.0.0/24.
-------------------------------------------------------------------
Mi configuración de /etc/network/interfaces es:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
# RED INTERNA
allow-hotplug eth0
auto eth0
iface eth0 inet dhcp
post-up ip route add 10.0.0.0/24 via 10.111.1.254
(esto es porque la porquería del enrutador MSWin2003 sólo distribuye el
tráfico hacia 10.111.1.0/24)
# INTERNET
allow-hotplug eth3
auto eth3
iface eth3 inet dhcp
-------------------------------------------------------------------
Levanto la eth0 de la red interna sola sin problemas:
term91:~# ifup eth0
Internet Systems Consortium DHCP Client V3.1.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth0/00:13:8f:8f:fe:6e
Sending on LPF/eth0/00:13:8f:8f:fe:6e
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 10.111.1.201
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.111.1.201
bound to 10.111.1.137 -- renewal in 286489 seconds.
if-up.d/mountnfs[eth0]: waiting for interface lo before doing NFS mounts
if-up.d/mountnfs[eth0]: waiting for interface eth3 before doing NFS mounts
-------------------------------------------------------------------
/etc/resolvconf/run/resolv.conf queda configurado así:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.111.1.201
nameserver 10.115.1.201
search red.interna
-------------------------------------------------------------------
Hago un ping a mi servidor zonal, otra máquina también con MSWin2003,
sin inconvenientes:
term91:~# ping server1
PING server1 (10.115.1.201) 56(84) bytes of data.
64 bytes from server1.red.interna (10.115.1.201): icmp_seq=1 ttl=126
time=5.50 ms
64 bytes from server1.red.interna (10.115.1.201): icmp_seq=2 ttl=127
time=0.557 ms
64 bytes from server1.red.interna (10.115.1.201): icmp_seq=3 ttl=127
time=0.385 ms
......
--- server1 ping statistics ---
65 packets transmitted, 65 received, 0% packet loss, time 68659ms
rtt min/avg/max/mdev = 0.382/0.525/5.505/0.639 ms
-------------------------------------------------------------------
Bajo eth0 sin problemas:
term91:~# ifdown eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 11906
....
-------------------------------------------------------------------
Levanto eth3 sola, que es la conexión a internet, sin problemas:
term91:~# ifup eth3
Internet Systems Consortium DHCP Client V3.1.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth3/00:0e:e8:e3:ac:50
Sending on LPF/eth3/00:0e:e8:e3:ac:50
Sending on Socket/fallback
DHCPDISCOVER on eth3 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth3 to 255.255.255.255 port 67 interval 15
DHCPOFFER from 192.168.1.1
DHCPREQUEST on eth3 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.164 -- renewal in 107614 seconds.
if-up.d/mountnfs[eth3]: waiting for interface lo before doing NFS mounts
if-up.d/mountnfs[eth3]: waiting for interface eth0 before doing NFS mounts
-------------------------------------------------------------------
/etc/resolvconf/run/resolv.conf queda de las siguiente manera:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 200.51.212.7
nameserver 200.51.211.7
-------------------------------------------------------------------
Y hago un ping a google:
term91:~# ping www.google.com
PING www.l.google.com (64.233.169.104) 56(84) bytes of data.
64 bytes from yo-in-f104.google.com (64.233.169.104): icmp_seq=1 ttl=235
time=196 ms
64 bytes from yo-in-f104.google.com (64.233.169.104): icmp_seq=2 ttl=236
time=267 ms
64 bytes from yo-in-f104.google.com (64.233.169.104): icmp_seq=3 ttl=235
time=353 ms
--- www.l.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 196.310/272.259/353.040/64.078 ms
-------------------------------------------------------------------
Bajo eth3 sin problemas:
term91:~# ifdown eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 11906
....
-------------------------------------------------------------------
Y acá es donde se pudre todo, cuando pretendo levantar ambas interfaces
de red.
Las levanta a ambas, pero no tengo acceso a amabas en forma simultánea.
term91:~# ifup -a
Internet Systems Consortium DHCP Client V3.1.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth0/00:13:8f:8f:fe:6e
Sending on LPF/eth0/00:13:8f:8f:fe:6e
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPOFFER from 10.111.1.201
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.111.1.201
bound to 10.111.1.137 -- renewal in 325747 seconds.
if-up.d/mountnfs[eth0]: waiting for interface eth3 before doing NFS mounts
Internet Systems Consortium DHCP Client V3.1.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth3/00:0e:e8:e3:ac:50
Sending on LPF/eth3/00:0e:e8:e3:ac:50
Sending on Socket/fallback
DHCPDISCOVER on eth3 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth3 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth3 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 192.168.1.1
DHCPREQUEST on eth3 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.164 -- renewal in 114373 seconds.
-------------------------------------------------------------------
/etc/resolvconf/run/resolv.conf queda de las siguiente manera:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.111.1.201
nameserver 10.115.1.201
nameserver 200.51.212.7
search red.interna
-------------------------------------------------------------------
Si hago un ping a google, la cosa sale mal, es decir, no lo encuentra:
term91:~# ping www.google.com
ping: unknown host www.google.com
Mientras que no hay problemas con la red interna:
term91:~# ping server1
PING server1 (10.115.1.201) 56(84) bytes of data.
64 bytes from server1.red.interna (10.115.1.201): icmp_seq=1 ttl=126
time=6.07 ms
64 bytes from server1.red.interna (10.115.1.201): icmp_seq=2 ttl=126
time=1.65 ms
--- server1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1003ms
rtt min/avg/max/mdev = 1.656/3.866/6.077/2.211 ms
-------------------------------------------------------------------
A cuál red accedo, es ALEATORIO, algunas veces accedo a internet y no a
la red interna, otras es al revés como en este caso.
Como más datos, dejo:
term91:~# ip route sh
10.0.0.0/24 via 10.111.1.254 dev eth0
192.168.1.0/24 dev eth3 proto kernel scope link src 192.168.1.164
10.111.1.0/24 dev eth0 proto kernel scope link src 10.111.1.137
default via 192.168.1.1 dev eth3
default via 10.111.1.254 dev eth0
-------------------------------------------------------------------
Ya me volví loco y leí todo lo legible.
Casi todo es sobre enrutamientos de distintas redes, y por más que he
hecho lo que dice, termino siempre mal.
Jugando con route, lo más que he llegado es a que la red que no tiene
acceso, pueda resolver la dirección de destino, pero no puedo
conectarme. Es decir, si hago un ping, determina la dirección destino,
pero pierde todos los paquetes.
Si alguien tiene alguna idea, lo agradecería mucho.
Javier
--
GNU/Linux - Usuario Registrado # 389414
http://i18n.counter.li.org
Reply to: