Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

VPN Tunnel "Site to Site" in-lab


  • Please log in to reply
5 replies to this topic

#1 dausken

dausken

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:02:37 PM

Posted 16 May 2016 - 04:53 PM

Hey guys I hope everyone is doing great! I've seem to run into a snag and was hoping you guys may be able to help.

This is my first time doing this in a live environment so take it easy on meh.

 

So in my college course we're suppose to configure a VPN Tunnel "exciting!" :P

It seems like I have everything working and able to ping each router (Branch, ISP, Main Office). But for the life of me when I attempt to create the tunnel for the Main Office computer to connect and successfully ping the Branch laptop, I'm having no luck.

 

The routers are Cisco RV082 (Using GUI), and I'll explain what Ip's and Subnets I have.

Router and Windows Firewall disabled just for config purposes.

 

When I click "save" in the Gateway-to-Gateway configuration, it resets my LAN ip's to: 172.162.1.0 & 192.128.1.0 instead of what it's suppose to be: 172.162.1.3 & 192.128.1.101

 

Note this isn't connected to the internet, it's all in one room.

 

Here's my layout...

 

ISP:

  • WAN - 97.26.255.249 /30
  • WAN Gateway - 97.26.255.249
  • LAN Gateway - 74.36.221.221 /30

 

Main Office:

  • WAN - 97.26.255.250 /30
  • WAN Gateway - 97.26.255.49
  • LAN - 192.168.3.*** /24
  • LAN Gateway - 192.168.3.1

 

Branch Office:

  • WAN - 74.36.221.222 /30
  • WAN Gateway - 74.36.221.221
  • LAN - 172.162.1.*** /26
  • LAN Gateway - 172.162.1.1

A computer is connected to the Main Office, and a laptop to the Branch Office.

 

KjtuucH.png

 

sAEjWlj.png

 

 

 

It sucks I can't be there right now because I would have stayed all day and night if my college would let me, I'm just trying to get an idea of why it will not work. If I could get any help I would really appreciate it.


Edited by dausken, 16 May 2016 - 05:01 PM.


BC AdBot (Login to Remove)

 


#2 Sneakycyber

Sneakycyber

    Network Engineer


  • BC Advisor
  • 6,104 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Ohio
  • Local time:03:37 PM

Posted 16 May 2016 - 06:02 PM

With out seeing the configuration on each Router there is no way of knowing what you did wrong. 


Chad Mockensturm 

Systems and Network Engineer

Certified CompTia Network +, A +


#3 dausken

dausken
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:02:37 PM

Posted 16 May 2016 - 06:29 PM

With out seeing the configuration on each Router there is no way of knowing what you did wrong. 

 

Yeah I didn't think about pulling it before I left... Was hoping for any kind of input of what could be causing it. I thought the Gateway-to-Gateway configuration was right, but it kept resetting itself like I said.

I'll pull it tomorrow if I don't get it fixed first thing in the morning.



#4 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:12:37 PM

Posted 17 May 2016 - 10:21 AM

A site to site vpn doesn't care what the ISP is doing.  The isp(s) is not in the mix and are only providing the physical transport / static wan ip address at each end between the two wan links. 

 

ip addressing is wrong

  • WAN - 97.26.255.250 /30
  • WAN Gateway - 97.26.255.49

/30 results in a ip range of .248 to 251.  As you can see .49 doesn't fall into that range and as such is not a valid gateway

 

  • WAN - 74.36.221.222 /30
  • WAN Gateway - 74.36.221.221 this is correct since /30 results in a range of .220-223 which 221 is contained within.

Edited by Wand3r3r, 17 May 2016 - 10:22 AM.


#5 dausken

dausken
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:02:37 PM

Posted 17 May 2016 - 12:57 PM

Thanks for the replies. I got it to work... It was a single setting within the VPN tunnel configuration I didn't tick. After that everything worked fine.
Req/close



#6 Sneakycyber

Sneakycyber

    Network Engineer


  • BC Advisor
  • 6,104 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Ohio
  • Local time:03:37 PM

Posted 17 May 2016 - 06:31 PM

Can you post the setting you missed so others looking can see your solution. We keep threads open so other people can look at them  :thumbup2:


Chad Mockensturm 

Systems and Network Engineer

Certified CompTia Network +, A +





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users