I configured it with dynamic tunnels with bgp (just because) and it came up. So I followed the rev b document 'configuring sonicos for amazon vpc' also. Before I start, let me just say that sonicwall documentation and support has gotten so much worse since the acquisition by Dell that I am moving away from sonicwall to almost any other solution (hi cisco + pan) when our support contract is up. ![]() I had this problem but after trial/error finally fixed it. We have a static route inside the VPC to tell it that the 10.25.0.0/16 traffic should go over the VPGW, and all the other routes for 10.30.0.0/16 are correctly forwarding to the OpenVPN instances. As I said, it works for the 10.100 network but not the 10.30 network through the same interface: Įdit #3: Traffic within the VPC is routing correctly, so if there's some magic incantation you need to do to let it route traffic from our office LAN I'd love to know what it is. What am I missing to allow it to forward traffic to 10.33.0.0 over the Office-AmazonVPC tunnel? According to everything I've read this should work but I appear to be missing something.Įdit #2: I followed this exact guide. Here's what I get when I SSH to 10.33: -58 packets captured. Here's what a packet capture for an SSH attempt to 10.100 shows: -File Index : 1. Traffic to 10.100 and 10.33 are routed the exact same way (over the VPN interfaces) but traffic to 10.100 gets forwarded while traffic to 10.33 doesn't. I've tried everything I can think of - there are no ACLs or Firewall rules blocking traffic. When I do a packet capture on the sonicwall, packets destined for 10.30.x.x show as "Consumed" or "dropped" with zero "forwarded." I don't understand what "consumed" is either, but that's a separate issue. I've set all the appropriate routing rules in the office firewall (SonicWall NSA2400, SonicOS 5.9) but as far as I can tell traffic isn't leaving the SonicWall. My problem is that I want to connect from the 10.25.0.0 network to 10.30.0.0 network THROUGH the 10.100 network. I have a separate VPC (legacy stuff) in 10.30.0.0/16, and I've setup openswan between 10.100.0.0 and 10.30.0.0 so they can speak to each other, and that works (I can ssh between the two networks). This connection works as expected - traffic to 10.100.0.0 connects fine. I have a VPC in Amazon that's 10.100.0.0/16, and I have a VPN established between the office and the VPC using Amazon's Virtual Private gateway. Yeah, that one is hard to find on the internet.ĭid you get any software with the device? It should be on the CD.My office network is 10.25.0.0/16. Regarding the "Network Discovery Utility". (This is explained on -6 of the manual Jim linked to.) In that case you need to set your computer to a static IP-address of 192.168.1.5 (subnet mask 255.255.255.0) for example and then type in the browser. If you can't find it, then the option Jim suggested is still valid but if you are on a different network-range (i.e. It will scan your network automatically with the correct ip-range giving you all the hostnames. From the hostname you should be able to recognize your NAS. ![]() After giving in the correct range of your network it will scan all devices and show you a list. If your NAS was assigned a (new) IP it should be in there.Īnother option is using a "Network Scanner" to find the IP. ![]() You can look into the web-interface of your router and look for the DHCP-client list. There are several options of finding your NAS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |