Jump to content
Christmas Period - Codemasters Staff and Support Read more... ×

Martinta

Members
  • Content Count

    2
  • Joined

  • Last visited

Posts posted by Martinta


  1. @steviejay69 I don't agree on the falling short point.

    I'm testing a lot of hardware and devices of different quality (been making reviews for a hardware portal where we get all kind of stuff, of different quality), which specific devices where the reason for this particular change i can't remember, but this is consumer devices, not enterprise. Now you might say that my case is special because i spend time testing a lot of these things, but the things i test can be bought by a consumer - who could then make the same solution as i did. But then again, i don't see how this is relevant. If you have added a secondary IP address on your network card, you know you have done it but given this is not an issue in any other games i have played online, the other game developers must have taken that into account.

    So from my point of view the particular reason behind why there are two ip addresses are irrelevant to the issue.

    A solution to the problem is easier then you might think. If it's technically a problem to force use the same IP scope as the default gateway, it would be pretty easy to just verify in case of a connection error if there are two ip addresses on the card, and if so, throw a searchable error. 


  2. On 4/13/2020 at 2:51 PM, steviejay69 said:

    It's not usual that anyone else would have the same error. I find it strange that any device would be configured with a fixed IP that cannot be changed.

    But you could also solve the issue by using a second LAN card in a desktop. 

    Just disabling the second card when you want to play F1. But probably, work and play don't mix.

    For the record

    Dependent on your work it isen't that uncomon to have multiple IP adresses in different IP scopes on the same network card. Adding an extra card is unnessesary, adding extra cost and cabling, so yes, it would solve the issue, but if you can solve it with configuration there is no idea in adding extra hardware to equation

    I had this error on my normal private PC (which is uncomon since i usually keep it as default as possible), but was done in this case because of some devices i have been testing on my home network. They did not accept DHCP as default but came with a 192.168.100.1 address - which i'm sure you know is not the scope of most home routers - so this leads to two options.

    1) Attach them directly to your pc (which requires you to detach your setup from the current network), then change IP scope and connect to equipment
    2) Plug it into a random network switch on the same VLAN - add secondary IP address in correct scope and reconfigure the devices (and when done, remove secondary IP which i forgot)

    This is not ment to open up a discussion, but rather add that this is an error that should be accounted for in the game, i have not seen any other issues in other multiplayer games, and there should not be any in this one either. If multiple IP addresses are on a network card, go for the one in the same scope as the default gateway and ignore the other.

    @Redhunt You Sir, saved me a quite some time in troubleshooting, thanks 🙂

    • Like 1
×