Neighbor dla RIP
Neighbor dla RIP
przegladam materialy do BSCI i mam:
polecenie "neighbor" w konfiguracji RIPv1 oraz RIPv2 powoduje wysylanie uaktualnien za pomoca unicastow"
w labie sie to nie potwiedza
pytanie brzmi:
Do czego sluzy to polecenie w teorii i praktyce
polecenie "neighbor" w konfiguracji RIPv1 oraz RIPv2 powoduje wysylanie uaktualnien za pomoca unicastow"
w labie sie to nie potwiedza
pytanie brzmi:
Do czego sluzy to polecenie w teorii i praktyce
passive + neighbour daje to o czym mowisz :
R6#
*Mar 16 03:38:19.241: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6#
*Mar 16 03:38:48.377: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6#
*Mar 16 03:39:17.321: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6#
*Mar 16 03:39:43.081: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6#
*Mar 16 03:39:50.993: RIP: received v1 request from 192.168.1.5 on FastEthernet0/0
*Mar 16 03:39:50.993: RIP: sending v1 update to 192.168.1.5 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6#
*Mar 16 03:40:12.565: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6(config)#router rip
*Mar 16 03:40:38.293: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6(config-router)#passive-interface fa0/0
R6(config-router)#neig 192.168.1.5
*Mar 16 03:41:07.173: RIP: sending v1 update to 192.168.1.5 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6#
*Mar 16 03:41:34.397: RIP: sending v1 update to 192.168.1.5 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6#
*Mar 16 03:42:01.877: RIP: sending v1 update to 192.168.1.5 via FastEthernet0/0 (192.168.1.1) - suppressing null update
HTH
R6#
*Mar 16 03:38:19.241: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6#
*Mar 16 03:38:48.377: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6#
*Mar 16 03:39:17.321: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6#
*Mar 16 03:39:43.081: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6#
*Mar 16 03:39:50.993: RIP: received v1 request from 192.168.1.5 on FastEthernet0/0
*Mar 16 03:39:50.993: RIP: sending v1 update to 192.168.1.5 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6#
*Mar 16 03:40:12.565: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6(config)#router rip
*Mar 16 03:40:38.293: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6(config-router)#passive-interface fa0/0
R6(config-router)#neig 192.168.1.5
*Mar 16 03:41:07.173: RIP: sending v1 update to 192.168.1.5 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6#
*Mar 16 03:41:34.397: RIP: sending v1 update to 192.168.1.5 via FastEthernet0/0 (192.168.1.1) - suppressing null update
R6#
*Mar 16 03:42:01.877: RIP: sending v1 update to 192.168.1.5 via FastEthernet0/0 (192.168.1.1) - suppressing null update
HTH
A CCIE does not necessarily make someone a good engineer. NOT having a CCIE does not necessarily make someone a bad engineer (or not as good). All we can do is strive to make ourselves individually better! (SM)
ok to zadanie z cylku przygotowujemy sie do CCIE
Juz wiemy jak spowodowac zeby nie broadcastowac updatu do wszystkich
a jak zrobic zeby przyjmowac tylko od jednej maszyny w segmencie eth?
Podpowiedz.. (RIP ma jakis tam dystans admin.)
Pozdrawiam
G.
a jak zrobic zeby przyjmowac tylko od jednej maszyny w segmencie eth?
Podpowiedz.. (RIP ma jakis tam dystans admin.)
Pozdrawiam
G.
bez acl :)
to moze byc niezle cwiczenie dla osob przygotowujacych sie do labu ccie sec.
To jednak toMike pisze:sprawdzilem - to jednak nie to
inne pomysly
Quotation from Cisco.com:
This command permits the point-to-point (nonbroadcast) exchange of routing information. When it is used in combination with the passive-interface router configuration command, routing information can be exchanged between a subset of routers and access servers on a LAN.
Multiple neighbor commands can be used to specify additional neighbors or peers.
Examples
In the following example, RIP updates are sent to all interfaces on network 10.108.0.0 except interface Ethernet 1. However, in this case a neighbor router configuration command is included. This command permits the sending of routing updates to specific neighbors. One copy of the routing update is generated per neighbor.
router rip
network 10.108.0.0
passive-interface ethernet 1
neighbor 10.108.20.4
Re: bez acl :)
i nie tylko, w labach do r/s to na porzadku dziennymto moze byc niezle cwiczenie dla osob przygotowujacych sie do labu ccie sec.
A CCIE does not necessarily make someone a good engineer. NOT having a CCIE does not necessarily make someone a bad engineer (or not as good). All we can do is strive to make ourselves individually better! (SM)
Odnosnie wyboru z ktorego routerka chcemy brac prefiksy w RIP, to rzeczywiscie sprawa jest na tyle skomplikowana, na ile skomplikowana jest manipulacja dystansem, i przygotowujac sie do labika sec oczywiscie przerobilem ten routingowy stuff
Wszystko, jak zwykle, zalezy jak dokladnie brzmi task lub jakie mamy potrzeby w srodowisku rzeczywistym...
Wszystko, jak zwykle, zalezy jak dokladnie brzmi task lub jakie mamy potrzeby w srodowisku rzeczywistym...