9/3/2023 0 Comments Sonicwall nsa 2600If you have a server on 3.3.3.4/29 which means it has a Public WAN IP and you want to put it behind the Firewall then you want to configure an interface (say X2) in Transparent / 元 Splice mode and connect it there. Transparent mode is like the device having a Public IP and "sharing" the WAN subnet BUT is still fully protected by the firewall and security services (IPS/Gateway AV, etc) with no NAT to get in the way. What you want to do is configure an interface in Transparent mode (which is called Splice 元 Subnet in newer SonicOS releases). ![]() BUt less so for VoIP protocols that are not. This is OK for services that are NAT friendly, like HTTP. The SonicWALL KB you linked to is part of the first case: providing external access using (say 3.3.3.3) to some internal IP (say 10.100.0.3) on a LAN (or DMZ) interface. ![]() If your SonicWALL X1 interface is configured to use 3.3.3.3 then you can use the other available IPs to provide NAT to internal IPs (on your X0 interface, or another interface) OR you can provide Transparent IPs to another interface where devices on that Transparent interface will have PUBLIC IPs (like 3.3.3.4). If you have a WAN subnet of, for example, 3.3.3.3/29 then you have a range of WAN IPs from, say, 3.3.3.2 - 3.3.3.6 (let's assume 3.3.3.1 is your default gateway/ISP router).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |