ScreenOS Firewalls (NOT SRX)
Reply
Distinguished Expert
echidov
Posts: 858
Registered: ‎11-02-2009
0

Re: VPN up, can't ping gateway

Hi,

 

Have you correctly configured what is named Topology in the SchrewSoft VPN client? This is step 9 in the KB22074.

VPN monitoring with default settings will not work with SchrewSoft client. It will permanently drop and re-negotiate the SAs. You should select Trust interface as the source one for VPN monitoring. The Trust interface IP should belong to the topology (VPN Proxy ID) for this to work.

Kind regards,
Edouard
Contributor
Rneinas
Posts: 10
Registered: ‎03-16-2012
0

Re: VPN up, can't ping gateway

Thanks for the information Edouard, but if I follow step 9 in that bulletin, I don't get any security associations to establish.  If I require a Policy Generation, I'll get one to establish, but only for a couple of minutes.  I'll rebuild my VPN client to match the bulletin posted and retry.  Nikolay, I've got the logging turned on for the policies I have configured.  How do I check the logs and see what's going on with those?  Thanks for sticking with me on this.  I'm learning a lot.

Super Contributor
nikolay.semov
Posts: 171
Registered: ‎03-15-2012
0

Re: VPN up, can't ping gateway

The Web UI of the firewall has a great visual display. Login to the firewall with a web browser, navigate to Policies, find your policy and click on the little table-like icon. That will give you the log for that policy. You may want to also enable logging at the beginning of the session.

Recognized Expert
Sahota
Posts: 484
Registered: ‎03-15-2012
0

Re: VPN up, can't ping gateway

Hi,

 

From the trace-route, it looks that the VPN client is unable to push traffic through the tunnel.

Try looking at the configuration of client, if possible, provide screenshot of client configuration.

Also, for initial analysis, you can disable monitoring (to keep things simple)

 

 

Regards.

Hardeep

Distinguished Expert
echidov
Posts: 858
Registered: ‎11-02-2009
0

Re: VPN up, can't ping gateway

Hi,

 

The Proxy IDs are automatically derived from the VPN-policy if policy-based VPN is used. If the incoming VPN policy contains a single address object in its destination field, e.g. 192.168.1.0/24, and multiple protocols or "Any" the following Proxy ID will be used on the FW: Local IP 192.168.1.0/24 Remote IP 255.255.255.255/32 Protocol Any. If the destination field contains multiple address objects or a group of objects the Local IP will be 0.0.0.0/0. If you need an access to multiple LANs you should configure multiple VPN policies, one policy for each pair of Local IP-Remote IP. In this case I would recommend to use ScreenOS 6.3 and route-based VPN.

The Proxy ID (IDs) configured on the client should match those on the Firewall.

 

Kind regards,
Edouard
Contributor
Rneinas
Posts: 10
Registered: ‎03-16-2012
0

Re: VPN up, can't ping gateway

Thanks for all the comments, but it looks like I'm moving backwards in my configuration.  Is Policy based routing the way to go?  I guess at this point, I just want the tunnel to come up and be able to move around on the trust network.  I'm willing to try a different approach if need be.  A simple setup will work.  I can always add more security as I learn more about the device and policies.  I'm really just frustrated right now and will try anything to move forward again.  Thanks again.

 

Contributor
Rneinas
Posts: 10
Registered: ‎03-16-2012
0

Re: VPN up, can't ping gateway

I followed the instructions in KB22074 for the Shrew Soft VPN client.  Now, I can't even bring the tunnel up.  Before, I was able to bring the tunnel up, but the security assocations never established.  Here is a snapshot of the event log.  If anyone has ideas, let me know.  I'll be happy to share any configs or snapshots you think might help out.

Distinguished Expert
echidov
Posts: 858
Registered: ‎11-02-2009
0

Re: VPN up, can't ping gateway

Hi,

 

You should create an IP pool. An IP from this pool will be assigned to the client during the extended authentication (XAUTH). The pool can be mapped to the default XAUTH settings (VPNs -> AutoKeys Advanced -> XAuth settings), to the Gateway Configuration or to the user profile. The settings in the user profile override those in the GW configuration and the last override the default settings. The same rule holds true for the DNS and WINS server IPs which can be assigned the same way.

You can also assign static IPs to each user in the user profile. This is usually used if the access policies are very restrictive and each user should have has a specific set of access rights.

 

Kind regards,
Edouard
Distinguished Expert
echidov
Posts: 858
Registered: ‎11-02-2009
0

Re: VPN up, can't ping gateway

(continued) ... and route-based VPN is used.

Kind regards,
Edouard
Contributor
Rneinas
Posts: 10
Registered: ‎03-16-2012
0

Re: VPN up, can't ping gateway

Hi Edouard,

 

I've tried various ways of configuring this router.  I even started from scratch and rebuilt the whole thing.  I'm convinced I have some sort of problem with my policies and the configuration of the client.  How does DNS figure into this?  I haven't added anything as far as DNS entries into the VPN, just the DNS on the untrust interface (ethernet 0/0).  I still can't get a security association to come up using the knowledge base you suggested in previous posts with the Shrewsoft client.  That's my first problem and the one I need to concentrate on.  My knowledge of subnetting has hampered this process as I am just starting out, so here's what I can tell you.  The trust zone is set for 172.168.1.0/24.  The VPN IP pool starts at 172.168.3.10.  I know that the VPN needs to be on a different subnet than the trust zone or internal LAN.  Can you please give me an idea of how the policies need to be set up?  I don't need any special permissions or anything.  I just need the VPN connection to be able to access the 172.168.1.0/24.

 

Thanks again for your help,

Rick

Copyright© 1999-2013 Juniper Networks, Inc. All rights reserved.