Section 3 – HDLC/PPP – 3 Points
How I hate thee!
Actually, this task was easy because you are authenticating on both sides of the link. You just have to watch out as one side uses clear-text password (PAP) and the other uses an MD5 hash (CHAP). The hardest part is figuring out which side to configure with which authentication.
3.2 Link Efficiency
“Configure r4 and r5 to maximize efficiency on this link by guessing character streams in frames sent over the link.”
I’m thinking that this describes compression. “guessing character streams” = predictor? YES!!!
lzs lzs compression type
mppc MPPC compression type
predictor predictor compression type
stac stac compression algorithm
r5#p 18.104.22.168 re 10 size 1500
Type escape sequence to abort.
Sending 10, 1500-byte ICMP Echos to 22.214.171.124, timeout is 2 seconds:
Success rate is 100 percent (10/10), round-trip min/avg/max = 20/21/24 ms
r5#sh compress detail
Software compression enabled
uncompressed bytes xmt/rcv 31472/31478
compressed bytes xmt/rcv 4251/4268
Compressed bytes sent: 4251 bytes 0 Kbits/sec ratio: 7.403
Compressed bytes recv: 4268 bytes 0 Kbits/sec ratio: 7.375
1 min avg ratio xmt/rcv 6.826/7.056
5 min avg ratio xmt/rcv 5.575/6.513
10 min avg ratio xmt/rcv 5.575/6.513
no bufs xmt 0 no bufs rcv 0
Compression Protocol used: Predictor 1
Decompression Protocol used: Predictor 1