It wouldn't accept within the range so I thought that was the right thing to do - was it? 250, and then made the MAC address of the console assign a static of. Wasn't quite sure if it was the right thing, but I lowered the general IP range of the router from ending. So far, I have the console DHCP reserved by it's mac address. I'll try the first process you describe tonight, and report back. Opportunity - I don't think so - thank you Digitap for taking the time to address an old concern for a new naive user. Thanks for giving me the opportunity to help!Īnd thank you both of you - unsurprisingly, a very helpful and proactive community - and you two have been superb. Give that a go and report back your results or report back if you have any other questions. You could go back and add other steps to further secure your network once you know how to set things up. What I'd recommend at this point is to just get it working. It's up to you how much you want to do here. Regarding the virtual WLAN, you could create a virtual WLAN to isolate this type of traffic and further secure your network. Running the Public Server Wizard will ensure there are the appropriate firewall rules and NAT policies created. Then you run the public server wizard selecting that address object and the "Any" service. Create a destination address object for the xbox MAC. To modify the original steps: Anything WLAN > WAN will be allowed. You could also do a DHCP reservation on the SW to assign the same IP to the xbox. If the xbox has a static IP then you can use that. The probability of getting the same MAC is possible but very unlikely. If something happened and another device got the same IP as the rules and policies, then that device would be opened to the WAN. So, using a specific MAC address is a little more secure. I just ran the wizard and see the "Any" option is now available.Īdditionally, I was having them use MAC address as opening the WAN > WLAN in this manner on the Sonicwall is not considered secure. So, you had to go back and modify the NAT policies and Firewall rules to Any. I had instructed parmor to chose a bogus service as in any service because (I think this was true then) the "Any" service was not available when running the Public Server Wizard. What the entry you linked to above and in the email was referencing was "opening" the WAN to WLAN to "simulate" uPnP on the SW appliance. Here is the official SW dope on the matter. SW appliances do not support uPnP which is what allows the XBox to communicate effectively through the firewall to the Internet. What you are trying to get the SW appliance to do is support uPnP which is a common feature of many other SOHO type firewalls.
0 Comments
Leave a Reply. |