Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalWhat'sWhat is the reason that you cannot set the tunnel's other side as destination address? It'sIs this because itsit is virtual only?
192.168.1.0/30 is the subnet I'm using and this is my configuration:
tunnel1 ip add 192.168.1.1 255.255.255.252 tunnel source (doesn't matter) tunnel dest 192.168.1.2 tunnel1 ip add 192.168.1.1 255.255.255.252 tunnel source (doesn't matter) tunnel dest 192.168.1.2 -> whyWhy is this invalid?
What's the reason that you cannot set the tunnel's other side as destination address? It's because its virtual only?
192.168.1.0/30 is the subnet
tunnel1 ip add 192.168.1.1 255.255.255.252 tunnel source (doesn't matter) tunnel dest 192.168.1.2 -> why is this invalid?
What is the reason that you cannot set the tunnel's other side as destination address? Is this because it is virtual only?
192.168.1.0/30 is the subnet I'm using and this is my configuration:
tunnel1 ip add 192.168.1.1 255.255.255.252 tunnel source (doesn't matter) tunnel dest 192.168.1.2 tunnel dest 192.168.1.2 -> Why is this invalid?
What's the reason that you cannot set the tunnel's other side as destination address? It's because its virtual only?
192.168.1.0/30 is the subnet
tunnel1 ip add 192.168.1.1 255.255.255.252 tunnel source (doesn't matter) tunnel dest 192.168.1.2 -> why is this invalid?
