On Mon, 11 Jul 2005, Claudiu Constantinescu wrote:
> 192.168.16.6 in B, netmask 255.255.255.252) cu comanda:
>
> A: ip addr add 192.168.16.5/30 peer 192.168.16.6 dev tun0
> B: ip addr add 192.168.16.6/30 peer 192.168.16.5 dev tun0
Asta e howto-ul ala de tunele gre si ipip de prin '97 adaptat de
la ifconfig la iproute? Crap! Daca tot ai /30 atunci ce cauti acolo cu
peer, adica point to point? Nu!
pe A:
ip tunn add capatA local 82.a.b.c remote 82.d.e.f mode gre ttl 64
ip add add 192.168.16.5/30 dev capatA
ip link set dev capatA up
i route add cutare1/masklencutare1 via 192.168.16.6 dev capatA onlink
pe B:
ip tunn add capatB local 82.d.e.f remote 82.a.b.c mode gre ttl 64
ip add add 192.168.16.6/30 dev capatB
ip link set dev capatB up
ip route add cutare2/masklencutare2 via 192.168.16.5 dev capatB onlink
> 1. Rutezi manual cele doua subneturi din spatele routerelor cand pica
> switch-ul (pe A rutezi prin 192.168.16.6 subnetul din spatele lui B,
> si invers)
> 2. Configurezi un protocol de rutare dinamica, sa o ia automat cand
> pica switch-ul.
Omul ale balarii pe acolo, e exclus tot ce inseamna routing in
acelasi caz. Doar bridging-ul il maipoate salva.
--
Any views or opinions presented within this e-mail are solely those of
the author and do not necessarily represent those of any company, unless
otherwise expressly stated.
---
Detalii despre listele noastre de mail: http://www.lug.ro/
