lug-bg: iproute2 - problem (?) pri routiraneto prez 2 ISP
- Subject: lug-bg: iproute2 - problem (?) pri routiraneto prez 2 ISP
- From: vlk@xxxxxxxxxxxxxxxxx (Vesselin Kolev)
- Date: Wed, 21 Aug 2002 11:56:22 +0300
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Zdraveite,
Az ne sym mnogo navytre v iproute2 i Advanced routing i zatova
izlagam problema (ako izobshto tova e problem) s molbata niakoi ot
horata, koito imat poveche znaniq po temata (kato Boyan Krosnov)
da vzeme otnoshenie po vyprosa.
Niama da zavoaliram vsichko zad VPN adresni prostranstva, napravo
izlagam problema v terminite na realni IP adresi.
Imam router, koito ednovremenno e svyrzan s dva dostavchika. Syotvetnite
gateway-hostove na dostavchicite sa slednite
1. 193.68.0.195 - vliza v systava na mrezhata 193.68.0.192/28. Moiat
router ima IP adres ot systava na tazi mrezha 193.68.0.202, definiran
vyrhu interface eth0.
2. 62.44.96.65 - vliza v systava na mrezhata 62.44.96.64/26. Moiata
router ima IP adres ot systava na tazi mrezha 62.44.96.71, definiran
vyrhu interface eth1.
Sumarno (svyrzanost kym dostavchicite):
eth0 (193.68.0.202) -> 193.68.0.195 | 193.68.0.192/28
eth1 (62.44.96.71) -> 62.44.96.65 | 62.44.96.64/26
Na routera ima oshte 3 interface-a. Te sa za mrezhite, paketite ot koito
routera nasochva. Eto danni za tiah i dostypnostta im prez syotvetnite
interface-i.
eth2 (62.44.103.1) -> 62.44.103.0/30
eth2:0 (193.68.191.193) -> 193.68.191.192/28
eth3 (VPN) (sluzhi za kontrol na routerite)
eth4 (62.44.103.5) -> 62.44.103.4/30
Osobenostite na cialata shema na routirane e slednata:
Mrezhite 62.44.103.0/30 i 62.44.103.4/30 se routirat prez ediniata dostavchik,
a imenno prez routera 62.44.96.65. Mrezhata 193.68.191.192/28 se routira
193.68.0.195. Za celta sa izgradeni dve razlichni routing tablici, ednata s
ime UniNet, a drugata s ime DigSys. Eto sydyrzhanieto na tezi tablici:
Tablica UniNet:
62.44.103.4/30 dev eth4 scope link
62.44.103.0/30 dev eth2 scope link
62.44.96.64/26 dev eth1 scope link
default via 62.44.96.65 dev eth1
Tablica DigSys
193.68.0.192/28 dev eth0 scope link
193.68.191.192/28 dev eth2 scope link
default via 193.68.0.195 dev eth0
Samia router ima slednata tablica (routing table main):
62.44.103.4/30 dev eth4 proto kernel scope link src 62.44.103.5
62.44.103.0/30 dev eth2 proto kernel scope link src 62.44.103.2
193.68.0.192/28 dev eth0 proto kernel scope link src 193.68.0.202
193.68.191.192/28 dev eth2 proto kernel scope link src 193.68.191.193
62.44.96.64/26 dev eth1 proto kernel scope link src 62.44.96.71
192.168.100.0/24 dev eth3 proto kernel scope link src 192.168.100.90
127.0.0.0/8 dev lo scope link
default via 193.68.0.195 dev eth0
Pravilata, koito sa podchineni na tezi tablici sa slednite:
ip rule add from 0/0 dev eth1 table UniNet
ip rule add from 0/0 dev eth0 table DigSys
ip rule from 62.44.103.0/30 dev eth2 table UniNet
ip rule from 62.44.103.4/30 dev eth4 table UniNet
ip rule from 193.68.191.192/28 dev eth2 table DigSys
Tazi shema na routirane raboti prekrasno. Ima samo edin problem, ako
izobshto mozhe da se nareche problem. Ako se napravi distancionen
traceroute se poluchava slednoto (ne puskam celia spisyk s hostove,
prez koito se preminava, a samo interesnia moment):
Traceroute to 62.44.103.1:
...
22 loz-gw.uni-sofia.bg (62.44.96.3) 534.521 ms 613.037 ms 541.223 ms
23 lcpe.pip.digsys.bg (193.68.0.202) 779.612 ms 824.712 ms 781.022 ms
24 ns.lcpe.uni-sofia.bg (62.44.103.1) 565.015 ms 534.457 ms 577.443 ms
Traceroute to 193.68.191.194
18 Sofia5.BG.EU.net (193.68.0.172) 749.456 ms 732.140 ms 732.835 ms
19 lcpe.pip.digsys.bg (193.68.0.202) 741.160 ms 736.437 ms 730.540 ms
20 digsys-to-lcpe.lan.lcpe.pip.digsys.bg (193.68.191.194) 739.872 ms
733.989 ms 737.243 ms
Tova, koeto se zabeliazva, che i pri dvate pytia, koito sa pokazani
se vizhda vynshnia interface lcpe.pip.digsys.bg (193.68.0.202), koito e
router za ednata linia, no ne i za drugata. Pi pyrvia sluchai (t.e. pri
traceroute do 62.44.103.1) bi triabvalo vsichko da izglezhda taka:
22 loz-gw.uni-sofia.bg (62.44.96.3) 534.521 ms 613.037 ms 541.223 ms
23 62.44.96.71 (62.44.96.71) 779.612 ms 824.712 ms 781.022 ms
24 ns.lcpe.uni-sofia.bg (62.44.103.1) 565.015 ms 534.457 ms 577.443 ms
NO NE E:))
Ako mahna default routinga na table main, routiraneto si prodylzhava normalno,
no ako se napravi distancionen traceroute se poluchavat slednite rezultati:
Traceroute to 62.44.103.1
22 loz-gw.uni-sofia.bg (62.44.96.3) 534.521 ms 613.037 ms 541.223 ms
23 * * *
24 ns.lcpe.uni-sofia.bg (62.44.103.1) 565.015 ms 534.457 ms 577.443 ms
Traceroute to 193.68.191.194
18 Sofia5.BG.EU.net (193.68.0.172) 749.456 ms 732.140 ms 732.835 ms
19 * * *
20 digsys-to-lcpe.lan.lcpe.pip.digsys.bg (193.68.191.194) 739.872 ms
733.989 ms 737.243 ms
Ta vyprosa e kak da nakaram pri traceroute do daden host ot ednata ot
trite mrezhi, zakacheni kym routera, da se vizhda syotvetnia interface na
routera.
Pozdravi
Vesselin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9Y1W++48lZPXaa+MRAoMvAJ9FBM2Nqa46Da0hHQfOThSpkS1JWQCg8wvS
U3372WzqcUZ5HnJkaTBBMY0=
=zXHQ
-----END PGP SIGNATURE-----
============================================================================
A mail-list of Linux Users Group - Bulgaria (bulgarian linuxers).
http://www.linux-bulgaria.org - Hosted by Internet Group Ltd. - Stara Zagora
To unsubscribe: http://www.linux-bulgaria.org/public/mail_list.html
============================================================================
|