Mircea MITU wrote:
On Wed, 2008-01-09 at 18:05 +0200, Mircea MITU wrote:
Salutam,
se da una bucata linux cu 2 interfete:
- eth_extern cu IP a.b.c.d
- eth_intern cu IP 1.1.1.1
Cratita face nat pt lanul 1.1.1.0/24
Problema: de pe statia 1.2.3.4 din lan se da un ping pe a.b.c.d.
Pachetele ajung in eth_extern (a.b.c.d), reply-ul porneste din
eth_extern dar nu ajunge in eth_intern (si ca atare nici in 1.2.3.4
din
lan).
Sunt convins ca imi scapa ceva elementar si prea evident pt a-mi sari
in
ochi, dar nu-mi dau seama ce.
Orice alte operatii functioneaza as expected.
Am gasit rezolvarea, nu imi e insa f clar care era pb.
Folosesc un setup cu doi provideri facut dupa
http://lartc.org/howto/lartc.rpdb.multiple-links.html
Dupa ce:
1. am eliminat
ip route add default via $P1 table T1
ip route add default via $P2 table T2
ip route add $P0_NET dev $IF0 table T1
ip route add $P2_NET dev $IF2 table T1
ip route add 127.0.0.0/8 dev lo table T1
ip route add $P0_NET dev $IF0 table T2
ip route add $P1_NET dev $IF1 table T2
ip route add 127.0.0.0/8 dev lo table T2
2. am trecut de la folosirea isp-ilor pt fail-over la load-balancing intre ei:
ip route add default scope global nexthop via $P2 dev $IF2 weight x nexthop via
$P1 dev $IF1 weight y
a mers
as zice ca aveai o regula care facea pachetele catre reteaua interna sa
fie aruncate spre exterior. sau nu aveai una care sa le forteze spre
intern. sau altfel spus a[vea]i nevoie de ceva de genu:
ip rule add from $IP_uri__de_pe_interfete_EXTERNE to $LOCALNET table
main
--
"A computer will not make a good manager out of a bad manager.
It makes a good manager better faster and a bad manager worse faster."
Ed Esber, president, Ashton-Tate, 1986
_______________________________________________
RLUG mailing list
[email protected]
http://lists.lug.ro/mailman/listinfo/rlug
