These cannot be routed across the internet and should NOT be coming through the game client like this.
They are all aimed at my PS4 IP, and only kick in when I load a zone. Sitting idle outside the game, or while in orbit--the packets do not show in the log. But as soon as I load to tower or other zones/instances, they start showing up. Even without 3074 opened/forwarded (UPnP off, remove the manual rule)...
IT STILL HAPPENS
So it appears my game client is actually being told to reach out to these private addresses like 192.168.1.135 and 10.0.1.7 as if they are valid public IP addresses (SPI firewall), but they cannot be reached across the internet. It isn't just a handful of them either... some load-ins have logged a dozen or so just in the 192.168.0.0 /16 address space alone, not to mention some of the other reserved private blocks.
Has the appearance of someone spoofing headers somehow (or just misbehaving routers perhaps?).
Not a coder, so don't know if/how the client could detect/prevent them from getting in game while this is happening... But if there is a way, Bungie NEEDS to address it. Many of the routers people get for their homes are not really equipped to filter this kind of thing out.
-
Edited by ADarkUrge: 11/2/2019 2:41:11 AMWhen I look at this I can't help but think Bungie are being naughty
-
Seriously... when clamping down on them, it took like a dozen retries to matchup for Control just now. This is the kind of list I am seeing: udp 10.10.100.41:3074 192.168.254.11:3075 UNREPLIED udp 10.10.100.41:3074 99.234.192.247:3074 UNREPLIED udp 10.10.100.41:3074 192.168.0.21:3074 UNREPLIED udp 10.10.100.41:3074 192.168.200.6:3074 UNREPLIED udp 10.10.100.41:3074 192.168.0.36:3074 UNREPLIED udp 10.10.100.41:3074 192.168.0.3:3074 UNREPLIED udp 10.10.100.41:3074 192.168.1.4:3074 UNREPLIED udp 10.10.100.41:3074 192.168.254.10:3074 UNREPLIED udp 10.10.100.41:3074 192.168.1.251:3074 UNREPLIED udp 10.10.100.41:3074 192.168.1.8:3074 UNREPLIED udp 10.10.100.41:3074 192.168.1.69:3074 UNREPLIED