Recently I purchased a RED20 to connect our branch office to HQ. The HQ has a Sophos XG firewall (XG310) which is all up to date.
When I try to connect the RED20 from the brach office to HQ no connection is being made.
What happens is this:
when booting the RED20 the system light starts blinking green and after a few seconds it's steady green and the router light starts blinking green.
After 70 seconds the router light dies and the system light turns red. This sequence keeps repeating itself.
The RED20 is connected directly to router and it should get an IP address from it.
On the XG I added a RED interface but it doesn't show any signs of connectivity with the RED20 (offline)
Does somebody have any clue why this isn't working?
Thank you for contacting the Sophos Community.
Usually, that combination of lights might mean that the Default Gateway is unreachable.
If possible as a test I would recommend you to remove the Router where the RED is connecting and connect the RED directly to the internet line.
Or if the router in front of the RED allows assigning a Static IP to the RED, try setting a static IP to the RED.
You can also confirm if you see traffic arriving at the XG, by using the Public IP of the remote site as a host in the tcpdump.
tcpdump -eni any host 184.108.40.206
Thanks for your reply.
Unfortunately it isn't possible to connect the RED directly to the internet. But in the router I see the RED gets an IP-address assigned to it (DHCP client list).
If I replace the RED with a laptop it gets also an IP-address, gateway-address and dns-server-addresses assigned to it.
Tommorrow I will be on the remote location again and give the tcpdump a try.
You also mentioned assigning a static IP-address to the RED. Can you tell me how that's be done?
Thank you for the follow-up.
To set the IP to the RED you do it from the XG, however, if the device is behind a NAT device, the RED will need an IP from that device to be able to go out the internet to reach the provisioning server.
Once it connects the RED will pull down the configuration and create the tunnel with the XG.
For what you mentioned, most likely the RED is getting the IP, make sure also port port 3400 is open on the router in front of the RED and by your ISP.
You can test by running the following command from a computer behind your current NAT device
telnet red.astaro.com 3400
You should see something like this:
# telnet red.astaro.com 3400Trying 220.127.116.11...Connected to red.astaro.com.Escape character is '^]'.
when testing red.astaro.com on 3400 is successful from an other device, it may be this bug if you're on a lower version
fixed in 18 MR5 and 18.5 GA
It looks like there is nothing wrong with the connection to red.astaro.com
When I try to telnet, as you suggested, the connection is established.
Do you have any other suggestion?
Hi, I've checked the update status of the XG and it is fully updated.
It seems like there is something blocking the access to red.astaro.com on port 3400
with windows 10 a nice tool to test with is the powershell command tnc
two examples for red.astaro.com on tcp:3400
PS > tnc red.astaro.com -port 3400WARNUNG: TCP connect to (18.104.22.168 : 3400) failedComputerName : red.astaro.comRemoteAddress : 22.214.171.124RemotePort : 3400InterfaceAlias : EthernetSourceAddress : 172.16.xxx.xxxPingSucceeded : TruePingReplyDetails (RTT) : 162 msTcpTestSucceeded : FalsePS > tnc red.astaro.com -port 3400ComputerName : red.astaro.comRemoteAddress : 126.96.36.199RemotePort : 3400InterfaceAlias : WLANSourceAddress : 192.168.xxx.xxxTcpTestSucceeded : True
You need to check if there is some upsetream firewall blocking this port. As it is not widely used, there may be some 443 and basic web stuff enabled on your router or it's upstream firewall.
Or your device is not masqued outside to the internet on the WAN router.
Thanks for your reply, that is a great way of checking.
It's seems the connection from my network to red.astaro.com:3400 is okay. I don't see anything else in the router that might block outgoing traffic.
Do you have any other suggestions?
I just checked the documentation:
SD-RED 20 & SD-RED 60 uses TCP 3400 + UDP 3410
You cannot check UDP with tnc by the way.
Is this the first RED connecting to your XG?
"RED is connecting to red.astaro.com to get the config via port 3400. Then will connect to the XG hostname via 3400 and 3410."
But from your description the RED internet LED will not light up, correct? So it cannot access Sophos Cloud.
Yes, you're absolutely right. This is our first RED device.
Also the Internet light does not light up. It reaches the third stage of the booting codes (Device is connecting to default gateway/router) and after that the system light turns red (DHCP or static address settings failed, defaulte gateway not reachable)
If possible, I would move the RED to a different location and test from there.
Also if your NAT device allows some type of diagnostics tools, or TCPdump, I would see if it sees any traffic coming from the RED device.
I have moved the RED to a different location but the results are the same. My NAT device is unfortunately a very basic device with almost no diagnostic tools on board.
I've send you two zip-files (through private message). One is the tcpdump file, made from de XG console. The other one is a putty log from the RED20.
Perhaps you'll find some clues in it.
This would'nt be the first RED that has been shipped with faulty firmware unable to connect.
It is always connecting to Sophos Servers first to look for new configurations you made for it before connecting to your XG firewall.
So if connecting to Sophos = Internet is not working, you may have a bricked box there.
Don't know if you can re-image a RED or if this needs to be done by RMA. Perhaps emmosophos can write a line about that?
Yeah, I agree, that could be the case.
It should all be straight forward.
If nothing else will do, I'm gonna give the USB-stick option a try.
Thanks for your replies, I really appreciate it.
Thank you for the PM, I have requested some more information from you.
For the RED devices, it needs to be RMA.
Thanks for the soultion.
A DNAT rule was misconfigured.
The traffic was hitting NAT ID rule number 32, uponc checking your NAT rule it seems your rule has the Service as ANY, which is causing this issue
DNAT rule was narrowed down to the port specific being used to access the WRDSGW server.
Basically what is happening is that the XG is caching all the traffic in any incoming port and passing it down to the WRDSGW server.