Skip main navigation (Press Enter).
Log in
Toggle navigation
Elevate
Communities
All Communities
My Communities
Answers
Innovation Circles
Training and Development
Browse
Discussion Posts
Popular Discussions
Events
Library Entries
TechPost
Ambassadors
MistFits
Blogs
Participate
Help/FAQs
Share your Expertise
Become A Member
Log in
Join Elevate
SRX
×
Community Home
Discussion
26.2K
Library
729
Blogs
0
Events
0
Members
1.3K
View Only
Back to Library
RE: SRX - Split Tunnel - Using Juniper Secure Connect
Recommend
12-03-2021 15:22
Portscanner
Statistics
0 Favorited
31 Views
1 Files
0 Shares
13 Downloads
Attachment(s)
SanitizedConfig.txt
27 KB
1 version
Uploaded - 12-03-2021
Download
Download Document
Please accept the terms of the copyright associated with this attachment before downloading it. Click the link below to read the terms.
Accept
Comments
Portscanner
12-08-2021 14:44
The traffic selector was the problem. I neded to add two traddic selector rules, one for the 172.18.0.0/22 network aone one for the 10.243.263.0/24 network, both w a remote ip of 0.0.0.0/0 so the users could access both internal letworks and the internet. Thank you!
LIQUN ZHANG
12-08-2021 12:24
One way I can think of is to use the traffic-selector configuration. Say you want the users to access 192.168.1.0/24 in your network, then you put this in the local source list. Then users can go to 8.8.8.8 or any other places (as long as not 192.168.1.0/24) directly from their devices. You can have multiple traffic-selectors to cover more local resources. Haven't tried it in the lab, though. Check out the user devices "route print" to see where the traffic goes.
Related Entries and Links
No Related Resource entered.
© 2025 Hewlett Packard Enterprise Development LP
Powered by Higher Logic