Znaci da sumiram ako sam dobro razumeo
Sto se tice router-id u IPv4 mogu da stavim isto kao u IPv6?
A sto se tice redistribute..
U sva 4 rutera koja imam da upisem kod konfiguracije ospf-a
Code:
router ospf 1
router-id x.x.x.x
redistribute bgp ID_AS metric-type 1 metric 100 subnets
Inace probao sam komandu
redistribute bgp ID_AS metric-type 1 metric 100 subnets i ne moze, moze samo posle
redistribute bgp ID_AS metric-type 1 subnets, ne moze metric..
redistribute bgp 64600 metric 100 metric-type 1 subnets moze, tako?
Prema linku
https://supportforums.cisco.co...uting-internal-bgp-routes-ospf
Tako su i uradili samo sto su u tom ruteru (recimo to je sad ovaj moj zuti) dodali i bgp redistribute-internal
Ja sam sve tako uradio, i jos na svaki ruter u tom AS kod OSPF dodao redistribute connected subnets da bi routeri oglasavali drugima mreze i nece da funkcionise.
I odradio sam posao sve duz jednog AS(odradio OSPFv2) i pokusao da pingujem jedan racunar sa drugim udaljeniji Pc10 sa PC12 i kaze da je unreachable, evo i slika i trace route od PC 10 do PC12
Code:
PC>tracert 37.233.104.10
Tracing route to 37.233.104.10 over a maximum of 30 hops:
1 109 ms 1 ms 29 ms 5.11.56.1
2 0 ms 46 ms 0 ms 213.108.31.17
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
Znaci da bukvalno staje do interfejsa gde treba da redistribute..Tu nesto ne valja, ali ne znam sta, kucao sam komande kao po linku.
Code:
router ospf 1
router-id 1.1.1.10
log-adjacency-changes
redistribute bgp 64600 metric 100 metric-type 1 subnets
network 213.108.31.0 0.0.0.3 area 0
network 213.108.31.4 0.0.0.3 area 0
!
router bgp 64600
bgp log-neighbor-changes
bgp redistribute-internal
no synchronization
neighbor 213.108.31.14 remote-as 65200
neighbor 81.161.114.0 remote-as 65500
network 5.11.56.0 mask 255.255.248.0
network 46.229.176.0 mask 255.255.240.0
network 37.233.96.0 mask 255.255.240.0
network 78.24.16.0 mask 255.255.248.0
network 213.108.31.0
!
Ali pinguje 213.108.31.1, a .2 ne, Zasto onda zastoj u 213.108.31.17, a ne u 213.108.31.1
Code:
PC>ping 213.108.31.1
Pinging 213.108.31.1 with 32 bytes of data:
Reply from 213.108.31.1: bytes=32 time=157ms TTL=254
Reply from 213.108.31.1: bytes=32 time=0ms TTL=254
Reply from 213.108.31.1: bytes=32 time=53ms TTL=254
Reply from 213.108.31.1: bytes=32 time=124ms TTL=254
Ping statistics for 213.108.31.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 157ms, Average = 83ms
PC>ping 213.108.31.2
Pinging 213.108.31.2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Verovatno je i problem, sto je next hop ka toj mrezi 0.0.0.0 i ka jos nekim mrezama
Code:
Network Next Hop Metric LocPrf Weight Path
*> 5.11.56.0/21 0.0.0.0 0 0 0 64600 i
*> 31.47.88.0/21 213.108.31.14 0 0 0 65200 i
*> 37.233.96.0/20 0.0.0.0 0 0 0 64600 i
*> 46.229.176.0/20 0.0.0.0 0 0 0 64600 i
*> 62.177.32.0/19 213.108.31.14 0 0 0 65200 i
*> 78.24.16.0/21 0.0.0.0 0 0 0 64600 i
*> 176.97.32.0/19 213.108.31.14 0 0 0 65200 i
*> 194.145.56.0/21 213.108.31.14 0 0 0 65200 i
*> 195.242.184.0/24 213.108.31.14 0 0 0 65200 i
*> 213.108.31.0/24 0.0.0.0 0 0 32768 i
[Ovu poruku je menjao tomislav91 dana 31.07.2014. u 09:11 GMT+1]
Re: IPv4 adresiranje
