At the moment rather one acting is PC one can ping wrote a five.
Acting is PC.
All 10 of these debugs
Let's have a look at some show commands.
So first command on Rodda to show interface tunnel Zira tunnel zero is up up.
The hardware type is tunnel.
The IP address on the interface is tendered 1 to 3 to 1 slash 30 the encapsulation type is tunnel the
tunnel source is forward wondered wondered one tunnel destination is forward one to two to two.
The protocol and transport is GRV over IP version 4.
Notice the MT you has been reduced for this interface because of the headers used in GRB the MT you
force serial to slash zero or maximum transmission unit for interface to slash is zero.
Is 5300 bytes but the MTUC for the GOP tunnel is 15:14.
So 1 4 5 0 minus 1 5 1 4 gives us 36 bytes because of the additional headers used in Jari.
The empty view is reduced.
In other words only small packets can be transmitted across the serial link because of the additional
headers added by Jeery originally we only have a single IP header.
But now we have an additional IP header called the delivery header as well as the GOP header and we
can see that by doing a shock capture
it's going to capture traffic on cereal to slice one on Rodda three
will send a ping from Rotto one acting as PC one two out of five acting as PC to
the ping.
I remember originally we would only have a single IP version 4 header with the payload.
But now we have both the GOP header as well as the out of header or delivery header.
So the original packet over here as received by Rodda to
doesn't include the GOP headers.
So when we do that ping again
this is the first Itam interface on brought it to.
We can see the ping message with the standard IP version for header and Ethernet header but when that
goes across the serial interface no to a Cisco deal see we see the original header and payload.
So there's the ping but notice once again the additional header.
So we've got the delivery had a as well as the GOP header.
So additional headers have been added when compared to the original packet because of that the empty
view is reduced.
You can only send a maximum packet size of 15 14 bytes because of the additional headers.
So once again on serial to slash zero the empty use 5400 bytes.
But on the tunnel interface it's 15 14 bytes because of the additional headers.
You can also see something for mation by using the command show IP interface tunnel's 0 scrolling up
just the command tunnel interface 00 is up up IP addresses tendered one to three to one slushed the
broadcast is this him to use 14 seventy six bytes once again.
Multicast reserved groups joined includes 3:58 0 0 10 which if you remember is the multicast group for
your job.
Your job is able to form a neighbor relationship across the tunnel interface in a very similar way to
how you would format across a serial interface.
Because this is a point to point link logically directly from one router to the other so as an example
show IP choppy neighbor wrote it to has a neighbor relationship with Rob.
For on this IP address and not on this IP address because the neighbor relationship is formed across
the tunnel.
Show IP GOP typology.
We have learnt a route 10 1 2 0 0 via 10 1 3 2 through tunnels 0.
And once again no one is able to ping Route 5.
Acting as a PC when we do a trace to 10 1 to 2.
Notice the trace goes to Rodda to then to route a for through the tunnel and then to roll a 5 route
3 is not seen at all in the trace because logically routed to is directly connected to a fault in the
same way.
Wrote a 5 when tracing to 10 one on one.
Since the traffic to rot for then logically to rockety and then to run a one.