beef-dead-beef Packets are sent to test if the WAN tunnel has built up correctly. So in my opinion it is just necessary to broadcast them on the WAN port of a RED. We had an issue with these packets on the LAN ports on a RED which we have fixed through an workaround (we blocked beef-dead-beef on a switch).

The RED has two WAN ports. I'd like to be able to use one for a private WAN service and one for a cheap Internet service and have the RED both split tunnel the traffic to the links and use the Internet link as a tunnel failover.

I really want to see more supported devices on the RED 10, if even extend the current support on the RED to what is available on the the UTM.

Would like the ability to use a DNS Group over DNS Host or Availability group. The reason is some companies will have separate teams managing the network and windows\dns. It would be upto the DNS Admins to keep the DNS entries up to date and not the network team managing an availability group

RED should be able to do DSL/VDSL (PPPOE), as this way it can be used with an ISP which is very common worldwide in requiring authentication against their modem.

Would be great to be able to use 1 RED device (RED10, RED50) with more than one UTM at a time to be able to connect to 2 Office/DataCenter with only 1 RED device..

The ability to either view a log directly on a RED device that is not connecting or insert a USB drive into the RED and the RED will load a diagnostic file onto the USB for viewing.

We are frequently frustrated by RED devices that just "don't work" for one reason or another. With no ability to see at which point the device is failing we are just shooting in the dark to find a solution to get the RED connected.

3G/UMTS devices supported by Sophos RED10 / RED 50 currently here in the Philippines the models of USB Sticks are the following below

Huawei E359 USB Modem – Globe Tattoo Stick

Huawei E355 USB Modem – Globe Tattoo Stick

Huawei E153 USB Modem – Smartbro Stick

ZTE MF180 – Smartbro Stick

this is a request to have these hw supported for RED

It would be nice if there is a possibility that you can upload a predefinied csv-file with all the configuration-data for a mass red deployment.

Example:

Branch-Office Name; RED-ID; IP-Addr; Subnet; DNS, DHCP-Start, DHCP-End,Tunnel-Mode.

Allow the admin to see the last contact of the RED with the provisioning server to make sure it downloaded its config and when

It would be very helpful if you could swap the broadbands at the remote RED site to make one (or the other) the default main broadband. This would be handy if one line is having problems such as rate limited but is in the main port.

We have limits on our broadband at most sites and have previously managed this with an alternative product no problem so we were surprised Sophos do not offer this feature.

You have done a great job with adding Mac filter that you can simpley push out to the RED. Now can we add one (1) service group to push out so that the remote office that runds RED with Split mode can have som security and should be independed of a nother vendor for that. Also with that NAT out.

Currently firmware updates run automatically after appliance updates: For bigger installations I would appreciate to have control over the RED update process. After a pilot update of a few devices RED firmware should be rolled out in clusters to reduce the risk of a full field failure (e.g. due to network overload caused by parallel update of 100 devices).

If Static WAN IP fails, dhcp should be tried after a given amount of time. Would alow a offline RED to be reconfigured by using a separate network.

Enable the USB port on a RED device to support eg.USB Hard Drives and USB printers so that customers can benefit from the USB ability by having a local file shares or printers connected to the branch office.

Customer would like support for the product above or 4G/LTE on RED devices. They want it so that when used for HA in RED, when the main internet connection goes offline, it will fail over to the Sierra 310U.

Add the ability to use 2 3G/UMTS on the RED50 with different mobile operators for fail-over.

RED device in the form of a PCI-Express card.
Would be very useful to install in to servers.

I suggest to put following IP information the reverse ip information also.

It will help us to idenfity fastly what is the telecom operator that the RED use to connect to ASG.

May be will be like this.

SV REDXX (reds1) [ID REDid] online from 201.75.79.148 - 201.75.79.148.dyn.opp.net

SV REDYY (reds2) [ID REDid] online from 205.215.12.89 - 205.215.12.89.ip.opp2.com

etc...