Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 39 subscribers
  • Views 1741 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to setup wireless access to Sophos RED 50?

Sean O'Neill2

Hi, we're in the process of moving the company & I need to setup a temporary VPN at our new building. I brought over a Sophos RED 50 & connected it to the new Verizon Fios router in the server room. It got online, did its firmware updates, rebooted, and created a successful connection to the XG310 at our Main Office. Easy!

My issue now is that all of the wiring, to every office, was flat-out snipped (grrr) above the server room. So we'll need to go wireless (at least for now). --> How do you set up a wireless router on the RED 50 so that wireless clients can connect to the VPN?

I'm trying to set up a Netgear R6300 (I can try another wireless router), but it simply cannot connect to the local WAN1 IP of the RED 50 at 192.168.1.156.

How can I get a temporary wireless setup going?



This thread was automatically locked due to age.
Parents
  • 0

    Hello there,

    Thank you for contacting the Sophos Community.

    You need to connect your Wireless Router to one of the LAN interfaces of the RED device not the WAN interface of the RED.

    Depending on how you configured your RED and the network where the Wireless router is connected, it would depend on the IP and how the routing will work for the devices that connect to the Wireless device.

    Note that your Wireless Router would need to have a way of routing the traffic to the RED device.

    Regards,

     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
  • 0 in reply to emmosophos

    Hi Emmanuel,

    Thanks for the response. The wireless router is connected to LAN1, per the diagram I posted.
    (though, note the Verizon device is also a wireless router)

    The RED 50 is configured as Standard/Unified, as I want all traffic to be routed through the RED to our XG 310 fiewall.

  • 0 in reply to Sean O'Neill2

    Hello Sean,

    Thank you for the follow-up.

    Oh since you wrote this " but it simply can't connect to the local WAN1 IP of the RED 50" I thought it was the WAN1 to the LAN.

    Is your Wireless router getting an IP from the XG Device and is the traffic from the router wireless getting to the Sophos Firewall? If not, this is the first thing that should be troubleshot. 

    If your Wireless router is already getting an IP from the XG,  then you need to configure your Wireless Router, provide DHCP to the Wireless Devices, and MASQ/NAT that traffic as it’s sent down to the RED.

    Let's say your Router Wireless gets IP 192.168.1.254, then configure your Wireless Router so it provided either DHCP within that range, or a new range.

    If you go by the first option, watch out for duplicated DHCP entries, if  you go for the second option and let's say your wireless gives DHCP range 192.168.2.1/24, then you need to tell your Router using a Static route to send all the traffic to the IP of the RED device

    Regards,

     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
  • 0 in reply to emmosophos

    Emmanuel,

    Thanks for the tips. The router was not getting an IP from the RED. I tried setting one up manually, with a 192.168.1.x address, but that didn't work.

    What did work was going back to the XG 310 firewall, and looking under Network >> DHCP. The RED's DHCP was off by default (?), so I enabled it, set up a scope, and it was green lights from there on in.

    It'd be helpful if there were at least some visibility into DNS/DHCP settings on the RED itself (at a remote location, natch).

Reply
  • 0 in reply to emmosophos

    Emmanuel,

    Thanks for the tips. The router was not getting an IP from the RED. I tried setting one up manually, with a 192.168.1.x address, but that didn't work.

    What did work was going back to the XG 310 firewall, and looking under Network >> DHCP. The RED's DHCP was off by default (?), so I enabled it, set up a scope, and it was green lights from there on in.

    It'd be helpful if there were at least some visibility into DNS/DHCP settings on the RED itself (at a remote location, natch).

Children
No Data
Unfiltered HTML