From: Julian Rodriguez (jumaroyu@gmail.com)
Date: Sat Aug 11 2007 - 09:22:55 ART
Although I am following that order of operations I did it again, the result
was exactly the same, I know I am not putting a space at the end of the
keychain name when configuring under the interface, nor the password under
the key chain creation.
Could anyone please try this one and shoot their results, I am going to
blame the rack rentals equipment and go on if I see a positive result from
any of you.
On 8/10/07, Serhat Aslan <serhatworks@gmail.com> wrote:
>
> Hi Julian
> for the AUTH : MD5 digest from 192.10.1.8 (?) -> !! I havent'recognized
> it was coming from a port :))
>
>
> I lived the same problem as yours. If i were you, I would clean the
> authentications from interface so I could be sure whether it is a network
> problem or not :). After that I would apply the keys as copy paste style or
> following "order of operations -at the end";
>
>
> ok.
> more deeply :)
>
> a) character formats representing. (brian wrote comment this issue)
> a-1) unknown chracters as representing as spaces or default character
> format.
> a-2) just only space :)
> when you use different OS (*nix to windows) you would face this problem
> at the text processsing :),
>
> b) for the authentication option: When you create the RIP-key chain
> after setting the config, system don't use this passwords(AFAIK, this is an
> best practice for setting up the passwords for routing protocols, I haven't
> test them exactly).
>
> order of operations :
> RIP: create key chain, 2. under-interface type, at the end key chain
> applying to interface.
>
> summary:
> 1.erase all the auth.config
> 2.check the rip routing
> 3. Reload the BB2 (to be sure the exact config, or copy start to run)
> 3.shut the sw2 interface
> 3.copy paste bb2 key-chain config
> 4.then apply it to interface.
> 5.check the last situation.
> 6.drop me an email the result :)
>
> ------------------
>
> Serhat Aslan
>
>
> On 8/11/07, Julian Rodriguez <jumaroyu@gmail.com> wrote:
> >
> > I really don't think it's an authentication issue, if you check at the
> > 179 after the IP address of SW2 on BB2's log kinds of make you think of a
> > BGP authentication issue, which is okay in this case because I am not
> > configuring BGP between the devices.
> >
> > I just don't have a clue why IE's answer is just what I did but I still
> > can't see those three routes without the network statements, isn't RIP
> > supposed to learn routes that I define by the network statement only, which
> > makes it differnet from EIGRP and OSPF where you have just to enable by
> > interface?
> >
> >
> > On 8/10/07, Serhat Aslan <serhatworks@gmail.com > wrote:
> > >
> > >
> > > Hi Julian,
> > >
> > > When I struggle on this problem, if I am sure the authentication
> > > config. I use one of the two way.
> > >
> > > way-1
> > > shut interface, delete key-chain config then copy-paste the BB2 key
> > > chain config to SW2.
> > > way-2
> > > don't enable the authentication before creating the key-chain on the
> > > routers/switches.
> > >
> > > No MD5 digest from 192.10.1.8 (?) {it looks like way-2}
> > >
> > > -------------
> > >
> > > Serhat Aslan
> > >
> > > On 8/10/07, Julian Rodriguez < jumaroyu@gmail.com> wrote:
> > >
> > > > This one has been killing me for the past couple of days, I am
> > > > working on
> > > > IEWB Core Lab 1 Task 4.5, following are the configs on both BB2 and
> > > > SW2,
> > > > which are supposed to use md5 to exchange RIP. I verified the
> > > > solution
> > > > because I couldn't find out what the problem was, can't see the RIP
> > > > routes
> > > > on SW2 anyways, but to my surprise my config was exactly what the
> > > > solution
> > > > stated. Any clues? I really don't see a way to put the routes into
> > > > SW2
> > > > routing table without changing the current config.
> > > >
> > > > BB2:
> > > >
> > > > interface FastEthernet0/0
> > > > description Ethernet to SW2 Fa0/24
> > > > ip address 192.10.1.254 255.255.255.0
> > > > ip rip authentication mode md5
> > > > ip rip authentication key-chain RIP
> > > > duplex auto
> > > > speed auto
> > > > ipv6 address 2001:192:10:1::254/64
> > > > ipv6 rip RIPng enable
> > > > ipv6 ospf 1 area 0
> > > >
> > > >
> > > > key chain RIP
> > > > key 1
> > > > key-string CISCO
> > > >
> > > > SW2:
> > > >
> > > > interface Vlan82
> > > > ip address 192.10.1.8 255.255.255.0
> > > > ip rip authentication mode md5
> > > > ip rip authentication key-chain RIP
> > > >
> > > > interface FastEthernet0/24
> > > > switchport access vlan 82
> > > >
> > > > key chain RIP
> > > > key 1
> > > > key-string CISCO
> > > >
> > > >
> > > > Troubleshooting OUPUTS:
> > > >
> > > >
> > > > Rack1SW2#ping 192.10.1.254
> > > >
> > > > Type escape sequence to abort.
> > > > Sending 5, 100-byte ICMP Echos to 192.10.1.254 , timeout is 2
> > > > seconds:
> > > > !!!!!
> > > > Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/8 ms
> > > >
> > > > Rack1SW2#
> > > >
> > > > Rack1SW2#
> > > > 01:19:04: RIP: sending v2 update to 224.0.0.9 via Vlan82 (
> > > > 192.10.1.8)
> > > > 01:19:04: RIP: build update entries - suppressing null update
> > > > Rack1SW2#
> > > > 01:19:32: RIP: sending v2 update to 224.0.0.9 via Vlan82 (192.10.1.8
> > > > )
> > > > 01:19:32: RIP: build update entries - suppressing null update
> > > > Rack1SW2#
> > > > Mar 1 01:25:45.707: %TCP-6-BADAUTH: No MD5 digest from 192.10.1.8(179)
> > > > to
> > > > 192.10.1.254(14382) (RST)
> > > > Mar 1 01:25:49.707 : %TCP-6-BADAUTH: No MD5 digest from 192.10.1.8(179)
> > > > to
> > > > 192.10.1.254(14382) (RST)
> > > > Mar 1 01:25: 57.499: RIP: sending v2 update to 224.0.0.9 via
> > > > FastEthernet0/0 ( 192.10.1.254)
> > > > Mar 1 01:25:57.499: RIP: build update entries - suppressing null
> > > > update
> > > >
> > > >
> > > > _______________________________________________________________________
> > > > Subscription information may be found at:
> > > > http://www.groupstudy.com/list/CCIELab.html
> > > >
> > >
> > >
> >
> >
> > --
> > MCSE-MCSA 2K & 2K3: Security-Messaging
> > MCDST, MCDBA, MCT, CEH, CISSP
> > CCNA, CCSP, CNA 6, CCA, HP MASE
> > Server+, I-Net+, Security+, Network+, A+
>
>
>
-- MCSE-MCSA 2K & 2K3: Security-Messaging MCDST, MCDBA, MCT, CEH, CISSP CCNA, CCSP, CNA 6, CCA, HP MASE Server+, I-Net+, Security+, Network+, A+
This archive was generated by hypermail 2.1.4 : Sat Sep 01 2007 - 11:32:10 ART