mrshahin

Newbie ✭
Default Avatar

Join the Conversation

To sign in, use your existing MySonicWall account. To create a free MySonicWall account click "Register".

mrshahin Newbie ✭

Badges (7)

2 Year Anniversary3 Year Anniversary4 Year Anniversary1 Year AnniversaryName Dropper10 CommentsFirst Comment

Comments

  • @MasterRoshi sorry change it to what? :)
  • @MasterRoshi Thank you for the update, you are right, the traffic is sending down the tunnel, the site 2 site from our Sonicwall to Aws is created from our public ip 194.XX.XX.5 ( WAN ip) and the A record of the Website is 194.XX.XX.66 Can you tel me how to source NAT the traffic ? Thank you
  • UPDATE, We did create the rule from the wizard and when put the web server on LAN, we can access the website, but when put the same webserver in the VPN zone cannot access the website from internet and get message that connection refused. we can access the website on the aws from the LAN What do we need to access the web…
  • @MasterRoshi Thank you for the reply, I did correct my access rule and setup the NAT policy as you suggested, as if web server is on LAN, but still I can not open the website from WAN and get the error that This Site cannot be reached. I also correct the destination as you suggested but still the same issue. This is my…
  • Hi @shiprasahu93 Thank you for the reply as always, Both servers have the same subnet and gw and both are in the same VPC and we are planing to put a firewall in front of this VPC 255.255.240.0 172.31.16.1 Thanks
    in subnets Comment by mrshahin July 2021
  • Hi @TKWITS thank you for your reply, You are right, I mean Packet monitor :) I have create a monitor filter and want to know all incoming ports from 2 IP's, should we use 1024-65353 for the source ports or we should just leave it empty? Thanks
    in filter Comment by mrshahin July 2021
  • Hi @shiprasahu93 Thank you for your reply, are these steps the correct one ? I have an extra public IP in the same range as the IP that we use for our wan! Thanks
  • My problem has been resolved, it was a misconfiguration on my part, correct the issue and everything works,
  • Hello @shiprasahu93 Thank you for the reply, I have already setup the 2 routes in the NSA 220, is this what you mean? Thanks
  • Hi @preston Thank you very much, I followed your document and now the tunnel has been active and I can ping and rdp to my EC2 in aws. Thank you and really appreciate your help. Shahin
  • Hi @preston Thank you for your reply, I did just create 2 Firewall access rules, one from LAN to aws and other one from aws to lan and after that create a Route as my last screenshot, but my route is just gray!! Any idea why the this route is grayout?
  • @preston Thanks again for the update, Do we need to create both VPNs? I mean we are going to first run some tests and later we will create the second vpn as well.3 Thanks
  • Hi @preston, Thank you for your reply, We have already setup a VPN with proper Public IP of aws as type Tunnel Interface. you are right my Shared Secrets start wit a dot (.) that was a bit strange to me but anyway I did try with both dot and without dot These are what I setup: If I understand you correctly no need to…
  • Hi @TKWITS Thank you for you update, We did follow the document that we have downloaded from aws side and configure a single tunnel, but still no connection to aws. I think it dont works becuse the document says config(SerialNumber)# tunnel-interface vpn T1 (add-interface[T1])# asymmetric-route (add-interface[T1])# policy…
  • Hi @shiprasahu93 Thanks for your reply, This document mention vpn connection between 2 Sonicwall, can we also use it to setup site 2 site connection to aws cloud services? Thanks