You know the drill. Do the lab, come here to check your answer. This one is on configuring a point-to-point GRE tunnel, using a hostname for the tunnel destination, and with OSPF interface thrown in for some quick review.
This latest lab requires you to configure a point-to-point GRE tunnel, but with no encryption config. Unless this is your first Config Lab, you know the drill. If not: take 5-10 minutes now, read the lab, and type your answer
To create a point-to-point GRE tunnel, you just need a few commands. The tricky part is to figure out what parameters to plug into the commands, particularly for the source and destination of each end of the tunnel. Check out
GRE tunnels, without the encryption, can be a breeze to configure and verify – you just need to practice the variations. Today’s post does just that, with a lab topology that looks like two enterprise routers connected to the Internet,
Configuring a static GRE tunnel, before adding the IPsec encryption, takes just a few commands. Have you mastered those commands yet? If not, check out the lab exercise first, and then come back here for the answer and some comments.
#GRE – that is, Generic Route Encapsulation – gives us a way to encapsulate IP packets inside another IP packet. Why? Often times, the reason is to create an Internet VPN, forwarding encrypted IP packets inside IP packets that can