Author Topic: LAN Server with no public IP access  (Read 1814 times)

nah0y

  • Sr. Member
  • ****
  • Thank You
  • -Given: 1
  • -Receive: 2
  • Posts: 430
  • \o/
    • View Profile
LAN Server with no public IP access
« on: May 11, 2014, 10:16:43 AM »
Hello,

I just saw that "- FIX: Non-windows platforms should now be able to properly join LAN servers on LANs that have no public IP access." on the release notes for 1.7.0.
Can you explain what it is?

I'm making a LAN game and don't really understand what was the issue before.

Thanks.

nah0y

  • Sr. Member
  • ****
  • Thank You
  • -Given: 1
  • -Receive: 2
  • Posts: 430
  • \o/
    • View Profile
Re: LAN Server with no public IP access
« Reply #1 on: May 11, 2014, 10:20:07 AM »
Also if you can explain these two:

- FIX: Added an extra step before enabling UDP traffic to avoid cases where it gets enabled erroneously.
- FIX: TNet.Tools.localAddress will now use GetHostAddresses instead of GetHostEntry.

Thanks.

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: LAN Server with no public IP access
« Reply #2 on: May 11, 2014, 02:01:03 PM »
170 was quite a while back... I honestly don't remember. You'd need to check git history.

UDP traffic is now not allowed until several packets have gone through. Before packet arrival was only checked in one direction. Now it's in both.

And I think after our long Skype talk you now know the localAddresses changes yourself. :P