Permanent Orange Sidewinder Error

[Elobilo]

Anyone else suddenly getting a permanent Orange Sidewinder error from about 23:00 CET last night (Saturday)?
On exiting a neutron star boosted jump from Eol Prou EA-Q d5-39 to Magellan on the way to Colonia, on exit I got an orange sidewinder error and thereafter every time I try to start the game in any mode, as well as when starting in Horizons/base and also via both Steam and the standalone client. I have restarted the client, validated/rechecked the files, both via steam and the standalone client, reinstalled graphics drivers, restarted both modem, router and PC several times (and connected separately using wired and wifi), connected the PC directly wired to the fiber modem, connected via a mobile hotspot to a 5G mobile data network and ALL result in the same error.

 

[Factabulous]

If you have one of these cards ...

Anyone with an RX 6000 series card able to get Odyssey to run with the 22.5.2 drivers?

I'm running into the same issue I had with the preview drivers; initial terrain generation takes forever (about five hours), the game loads to the main menu, then crashed back to the main menu with an Orange Sidewinder error upon entering any mode or playing any training mission. Horizons works...

forums.frontier.co.uk

 

[GJ51]

IPV6 ???

 

[Elobilo]

IPV6 ???

No, this is disabled both in game and on my router.

 

[Elobilo]

If you have one of these cards ...

Anyone with an RX 6000 series card able to get Odyssey to run with the 22.5.2 drivers?

I'm running into the same issue I had with the preview drivers; initial terrain generation takes forever (about five hours), the game loads to the main menu, then crashed back to the main menu with an Orange Sidewinder error upon entering any mode or playing any training mission. Horizons works...

forums.frontier.co.uk

I'm using a RTX 2060, so not this.

Interestingly though, when I play on my laptop, which I now do not have as it is away to be fixed, I use a Radeon RX 6900 XT as eGPU and have had no problems, especially during the time in the linked post.

 

[GJ51]

Starting to feel like it might be a firewall issue on the PC

What are your network settings options in the game? Do you have port forwarding set up? Anything showing up in the Connections Statistics?

 

[Elobilo]

Starting to feel like it might be a firewall issue on the PC

Starting to feel like it might be a firewall issue on the PC

What are your network settings options in the game? Do you have port forwarding set up? Anything showing up in the Connections Statistics?

I hadn't thought the firewall could be a problem, so I tried it after turning off the windows firewall each of private, public and domain and still got the same orange error.
Regarding the network, the desktop I play on has a reserved static IP address and in the router I specifically forward the ports to it. The point is, this configuration has not been changed for about 1.5 years with no problems above the normal and nothing was changed last night when the errors started. In the screenshot of my settings I tried with the port forwarding off as well. My internet latency is 12ms and 350Mbps up and down. I also tried it directly plugged into the fiber modem, by passing the router and on mobile 5G data hotspot.

 

[GJ51]

The only other issue I can think of would be anti-virus/malware or host file blocking the traffic.

When you load the launcher do you get the server status report showing the green "ok"?

At the Options menu are you getting a server ip address in the lower left corner for the ED server?

If you get an ip address then run a traceroute to the server

From a command prompt enter "tracert edipaddress" it should tell you if your getting to the server or not.

1. Open a Command Prompt. ...
2. In the Command Prompt window, type 'tracert' followed by the destination, either an IP Address or a Domain Name, and press Enter. ...
3. The command will return output indicating the hops discovered and time (in milliseconds) for each hop.

It should return something like this:

Tracing route to ec2-34-245-10-105.eu-west-1.compute.amazonaws.com [34.245.10.105]
over a maximum of 30 hops:

1 2 ms 1 ms 5 ms ec2-34-245-10-105.eu-west-1.compute.amazonaws.com [34.245.10.105]

Trace complete.

 

[GJ51]

Another difference I just spotted between your setup and mine is that you have upnp on and your router is set to full cone.

I's try switching to symmetric and if need be turn off upnp if you have a port forward rule setup in the router and a firewall entry for ED on the PC

HTH

 

[Caydran]

The only two things I see here are:
1) UPNP = ON, might want to consider turning this off.
2) ROUTER = FULL CONE. With port forward on, mine says "Port-Restricted" as it is port forwarding. Can you change this?

I use a 1GB Fiber and set the router to ask for DHCP on the internet provider.

 

[Elobilo]

I don't use explicit antivirus program, just windows defender, but again nothing changed - no updates or anything.

The Launcher always has shown a green OK status

In the options menu of the game, I have always quickly connected to the server, after 1 to 2 seconds (see pic below)
Wired connection to router:
\>tracert 34.242.123.57
Tracing route to ec2-34-242-123-57.eu-west-1.compute.amazonaws.com [34.242.123.57]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 <1 ms 5 ms 1 ms ti0016a400-gw.ti.telenor.net [88.91.161.1]
3 10 ms 5 ms 4 ms ti0030c400-ae1-0.ti.telenor.net [146.172.101.53]
4 5 ms 4 ms 5 ms ti0001c360-ae1-0.ti.telenor.net [146.172.14.129]
5 16 ms 29 ms 9 ms ti0001b400-ae1-0.ti.telenor.net [146.172.105.66]
6 4 ms 4 ms 5 ms 148.122.8.154
7 * * * Request timed out.
...
30 * * * Request timed out.
Trace complete.

ping timed out.

Mobile network via WIFI:
different IP: 34.254.10.150

\>tracert 34.254.10.150
Tracing route to ec2-34-254-10-150.eu-west-1.compute.amazonaws.com [34.254.10.150]
over a maximum of 30 hops:
1 10 ms 6 ms 8 ms 192.168.97.254
2 * * * Request timed out.
...
25 * * * Request timed out.
26 * ^C

\>ping 34.254.10.150
Pinging 34.254.10.150 with 32 bytes of data:
Reply from 34.254.10.150: bytes=32 time=147ms TTL=235
...
Reply from 34.254.10.150: bytes=32 time=72ms TTL=235

Ping statistics for 34.254.10.150:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 147ms, Average = 87ms

When I went back to the wire connection, I got the same IP as before.

Sadly these timed out for trace route but from the admittedly little I understand, the ICMP packets used can be blocked by intermediate servers. Interesting that the ping while connected to the router timed out, but from the mobile connection, it worked, but none of the traceroute did.

Your interest and help in this is greatly appreciated.

 

[Caydran]

Somewhat confused here?

In order to better understand your problem, you are using "mobile WiFi" when getting the timeouts and orange sidewinder errors?

WiFi networks are notorious for bad connections while gaming.

Are you playing on the "wired" connection and get orange sidewinder errors?

You don't have VPN in the way, do you?

 

[Elobilo]

The only two things I see here are:
1) UPNP = ON, might want to consider turning this off.
2) ROUTER = FULL CONE. With port forward on, mine says "Port-Restricted" as it is port forwarding. Can you change this?

I use a 1GB Fiber and set the router to ask for DHCP on the internet provider.

The router is set to DHCP for the IP from the internet provider. It is the internal desktop PC I play Elite on has a static IP, which is defined in the router as well.
When I configured the NAT routing in the router instead of uPNP, about 1.5 years ago, I did think UPNP should be off, but if worked as is and I though "if it ain't broke..."
I had turned it off earlier to check with no success, but I have though now turned it off again (and will leave it off) to see if I can change the FULL CONE setting, which I can't and it stays as such even after restarting. I still get the orange error with UPNP set to off.

 

[Elobilo]

Somewhat confused here?

In order to better understand your problem, you are using "mobile WiFi" when getting the timeouts and orange sidewinder errors?

WiFi networks are notorious for bad connections while gaming.

Are you playing on the "wired" connection and get orange sidewinder errors?

You don't have VPN in the way, do you?

I was only using the mobile wifi hotspot as a test, to see if it gives the same error and it does.
I always use the wired connection to my router when I play and I get the orange error on this as well as the tests on the wifi (Though not optimal, I have managed to play via my mobile hotspot before when my main internet was down).
No, I am not using a VPN.
This error happened suddenly mid in game, after several hours of problem free playing.

 

[GJ51]

You're clearly getting lost somewhere in the pathway to the server for an unknown reason. I hit 34.242.123.57 in one hop from my location with no problem.

 

[GJ51]

Stay with the wired connection until it gets sorted out as it reduces other issues common on wireless.

Research your router settings and determine how to switch from full cone to symmetric.

If you post your router model I'll be happy to review the docs.

ALSO - from the command prompt

do an ipconfig /flushdns to flush your dns cache

Then do another tracert on the wired connection

 

[Caydran]

So, the way this works, and I assume you are familiar with DHCP on both the router and PC, on the router, you should have the router's address set to 192.168.x.1 depending on your chosen sub-net. It could be in the range of 192.168.0.1, or 192.168.1.1, but as long you give the router its own address, ending in 1. This will be your "Gateway" address.

Then set your router to give out DHCP addresses to clients starting with 192.168.x.2 and ending with 192.168.x.254, but not 255 as this is a broadcast address. If you want to restrict the numbers of DHCP addresses, you can limit this by choosing something less than 254, I use 192.168.x.25, so only twenty-four addresses are available.

Then, in the router, find the DHCP Server and "Reserve those addresses" used by your clients, setting one reservation for your PC, i.e. 192.168.x.3 along with it's MAC Address. Both the MAC and IP together will "Reserve" this address for your PC. Do this for each client which needs an address from your router, both wired and wireless.

Turn UPNP OFF as you do not need this at all. NAT and UPNP are two different things and NAT, if enabled on your router, will handle what you need automatically.

Then, on your PC, set the Windows Network to DHCP so it talks to router and asks for an address. It will get the DHCP Reserved address you set in the router.

Then set up a Port Forward rule in the router, telling it to forward your PC IP address, which is now DHCP Reserved, i.e. 192.168.x.3 to port 5100. It should come out to 192.168.x.3:5100 and set it to enabled.

Now, go to https://www.speedtest.net and run a speedtest to confirm all is working.

 

[Caydran]

Also, can you find "\Elite Dangerous\Products\elite-dangerous-odyssey-64\Logs" and look at your most current "netlog.2022.x.x.x.log" to see what type of network errors ED/O may be seeing?

Don't post your netlog here, as it contains sensitive information.

 

[Elobilo]

Stay with the wired connection until it gets sorted out as it reduces other issues common on wireless.

Research your router settings and determine how to switch from full cone to symmetric.

If you post your router model I'll be happy to review the docs.

ALSO - from the command prompt

do an ipconfig /flushdns to flush your dns cache

Then do another tracert on the wired connection

Stay with the wired connection until it gets sorted out as it reduces other issues common on wireless.

Research your router settings and determine how to switch from full cone to symmetric.

If you post your router model I'll be happy to review the docs.

ALSO - from the command prompt

do an ipconfig /flushdns to flush your dns cache

Then do another tracert on the wired connection

After I ran ipconfig I got the same.

\>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

\>tracert 34.242.123.57

Tracing route to ec2-34-242-123-57.eu-west-1.compute.amazonaws.com [34.242.123.57]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 2 ms 4 ms 2 ms ti0016a400-gw.ti.telenor.net [88.91.161.1]
3 4 ms 5 ms 4 ms ti0030c400-ae1-0.ti.telenor.net [146.172.101.53]
4 5 ms 49 ms 19 ms ti0001c360-ae1-0.ti.telenor.net [146.172.14.129]
5 4 ms 4 ms 4 ms ti0001b400-ae1-0.ti.telenor.net [146.172.105.66]
6 4 ms 5 ms 5 ms 148.122.8.154
7 * * * Request timed out.
...
30 * * * Request timed out.

Trace complete.

My router is a Netgear Nighthawk R9000, I have tried researching how to change this but didn't get very far. Pictures of the NAT config is below along with other setting, which might apply to this.

Below might be the config for strict in Elite, but changing it to open had no effect in Elite Network settings:

My Router is a Netgear R9000

 

[Caydran]

If all else fails and you just can't get it to work, this is a SHOTGUN method that fixed every thing for me when I constantly got ship colored errors. Turns out my router was in some unholy mode and would not cooperate, no matter what settings I changed. Sometimes, routers have a mind of their own.

1) Set your PC Windows Network to DHCP networking first. Reboot.
2) Reset your router to "Factory Defaults".
3) Reboot the router, then the PC.
4) Log back in to the router and set up DHCP reservations for all wired/wireless clients using the DHCP ADD Reservation button, if available.
5) Turn off UPNP.
6) Add a port forward for the PC's IP address to port 5100 and enable the rule.
7) Confirm all router settings and do not change anything unless you have a valid reason for doing so. Understand the need for the change.
8) Reboot the router and PC once more, to confirm the PC has the correct address, assigned by the router DHCP server.

As I said. This is a SHOTGUN approach.