Omada block games

Omada block games

Omada block games
Omada block games
2022-10-17 22:38:21 - last edited 2022-10-18 20:13:04
Hardware Version: V5
Firmware Version: 5.5.6

Good day all,

 

After the update i can't connect to any Satisfactory dedicated servers anymore after the update. 

A friend of my can connect to the server but i can't, even if i start a server localy a can't connect so somthing is blocking those ports or somthing. 

 

The game says game ongoing and the ping is showing up but i can't connect. 

When i directly connect to my ISP i can connect so there must be a wrong setting in Omada. 

Has somebody a solution? 

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:Omada block games -Solution
2022-10-18 20:12:47 - last edited 2022-10-18 20:13:04

I found the issue in my network! 

 

On my switch i  turned in mirroring for my computer. 

In the past i had some issue with my network and i had to use Wireshark. 

After changed it back to switching i can connect to the server!

 

Thnx for your help all! 

 

Recommended Solution
  2  
  2  
#7
Options
6 Reply
Re:Omada block games
2022-10-18 11:05:14

  @Aviator14 

 

Do you know the port number of this game server?

If you know it, try port forwarding on the controller to test.

  0  
  0  
#2
Options
Re:Omada block games
2022-10-18 16:07:34
Easiest way to tackle this issue is to enable uPNP (Services / uPNP) on the network you setup for gaming.
  0  
  0  
#3
Options
Re:Omada block games
2022-10-18 19:28:30

@Virgo 

 

Yes i have opened all the ports but it no progress. 

 

@TandS 

 

uPNP is enabled for all the networks. 

When i open a hotspot on my phone i can connect with the server 

  0  
  0  
#4
Options
Re:Omada block games
2022-10-18 19:37:17

This are the logs from the game. 

 

[2022.10.18-19.34.52:829][386]LogScript: Warning: UAkGameplayStatics::PostEventAttached: No Event specified!
[2022.10.18-19.35.06:153][923]LogTaskGraph: Warning: Task graph took  22.86ms for RT to recieve broadcast.
[2022.10.18-19.35.06:153][923]LogTaskGraph: Warning: Task graph took  22.99ms for RT to recieve broadcast and do processing.
[2022.10.18-19.35.06:153][923]LogTaskGraph: Warning: Task graph took  22.91ms to wait for named thread broadcast.
[2022.10.18-19.35.06:153][923]LogTaskGraph: Warning: Task graph took  23.06ms to broadcast.
[2022.10.18-19.35.13:386][214]LogInit: WinSock: Socket queue. Rx: 32768 (config 32768) Tx: 32768 (config 32768)
[2022.10.18-19.35.13:386][214]LogNet: Created socket for bind address: :: on port 0
[2022.10.18-19.35.13:386][214]LogInit: WinSock: Socket queue. Rx: 32768 (config 32768) Tx: 32768 (config 32768)
[2022.10.18-19.35.13:386][214]LogNet: Created socket for bind address: 0.0.0.0 on port 0
[2022.10.18-19.35.13:386][214]PacketHandlerLog: Loaded PacketHandler component: DTLSHandlerComponent ()
[2022.10.18-19.35.13:387][214]PacketHandlerLog: Loaded PacketHandler component: Engine.EngineHandlerComponentFactory (StatelessConnectHandlerComponent)
[2022.10.18-19.35.13:387][214]LogNet: Game client on port 25940, rate 300000
[2022.10.18-19.35.13:387][214]LogDTLSHandler: Warning: Empty certificate identifier
[2022.10.18-19.35.14:843][261]LogDTLSHandler: Attempted to send packet during handshaking, dropping.
[2022.10.18-19.35.15:068][270]LogDTLSHandler: Attempted to send packet during handshaking, dropping.
[2022.10.18-19.35.15:292][279]LogDTLSHandler: Attempted to send packet during handshaking, dropping.
[2022.10.18-19.35.15:517][288]LogDTLSHandler: Attempted to send packet during handshaking, dropping.
[2022.10.18-19.35.15:718][296]LogDTLSHandler: Attempted to send packet during handshaking, dropping.
[2022.10.18-19.35.15:867][302]LogDTLSHandler: Attempted to send packet during handshaking, dropping.
[2022.10.18-19.35.16:068][310]LogDTLSHandler: Attempted to send packet during handshaking, dropping.
[2022.10.18-19.35.16:268][318]LogDTLSHandler: Attempted to send packet during handshaking, dropping.
[2022.10.18-19.35.16:469][326]LogDTLSHandler: Attempted to send packet during handshaking, dropping.
[2022.10.18-19.35.16:693][335]LogDTLSHandler: Attempted to send packet during handshaking, dropping.
[2022.10.18-19.35.16:868][342]LogDTLSHandler: Attempted to send packet during handshaking, dropping.
[2022.10.18-19.35.17:019][348]LogDTLSHandler: DTLSCertVerifyCallback: Verified
[2022.10.18-19.35.17:069][350]LogDTLSHandler: Attempted to send packet during handshaking, dropping.
[2022.10.18-19.35.17:120][352]LogDTLSHandler: UpdateHandshake:  Handshaking completed
[2022.10.18-19.35.17:921][384]LogBeacon: FGServerBeaconClient_2147480886[IpConnection_2147480883] Client received: BeaconWelcome
[2022.10.18-19.35.17:922][384]LogDTLSHandler: Error: SSL_read error: 2
[2022.10.18-19.35.17:922][384]LogSecurity: Warning: 134.255.222.124:25940: Malformed_Packet: Packet failed PacketHandler processing.
[2022.10.18-19.35.17:922][384]LogSecurity: Warning: 134.255.222.124:25940: Closed: Connection closed
[2022.10.18-19.35.17:922][384]LogNet: UNetConnection::Close: [UNetConnection] RemoteAddr: 134.255.222.124:25940, Name: IpConnection_2147480883, Driver: IpNetDriver_2147480884 IpNetDriver_2147480884, IsServer: NO, PC: NULL, Owner: NULL, UniqueId: STEAM:(STEAM)-=SSD=- AviatorNL [0x21D936A80E0], Channels: 2, Time: 2022.10.18-19.35.17
[2022.10.18-19.35.17:922][384]LogNet: UChannel::Close: Sending CloseBunch. ChIndex == 0. Name: [UChannel] ChIndex: 0, Closing: 0 [UNetConnection] RemoteAddr: 134.255.222.124:25940, Name: IpConnection_2147480883, Driver: IpNetDriver_2147480884 IpNetDriver_2147480884, IsServer: NO, PC: NULL, Owner: NULL, UniqueId: STEAM:(STEAM)-=SSD=- AviatorNL [0x21D936A80E0]
[2022.10.18-19.35.17:922][384]LogDTLSHandler: Error: SSL_read error: 2
[2022.10.18-19.35.17:922][384]LogSecurity: Warning: 134.255.222.124:25940: Malformed_Packet: Packet failed PacketHandler processing.
[2022.10.18-19.35.17:922][384]LogSecurity: Warning: 134.255.222.124:25940: Closed: Connection closed
[2022.10.18-19.35.17:922][384]LogNet: DestroyNamedNetDriver IpNetDriver_2147480884 [IpNetDriver_2147480884]
[2022.10.18-19.35.17:923][384]LogExit: IpNetDriver_2147480884 IpNetDriver_2147480884 shut down
 

  0  
  0  
#5
Options
Re:Omada block games
2022-10-18 20:03:45

I'm making a bit progression. 

 

What i have found out now is that when i connect to wifi i can connect to the server. 

So there is somthing between my NIC and Omada 

  0  
  0  
#6
Options
Re:Omada block games -Solution
2022-10-18 20:12:47 - last edited 2022-10-18 20:13:04

I found the issue in my network! 

 

On my switch i  turned in mirroring for my computer. 

In the past i had some issue with my network and i had to use Wireshark. 

After changed it back to switching i can connect to the server!

 

Thnx for your help all! 

 

Recommended Solution
  2  
  2  
#7
Options