Results 1 to 10 of 384

Thread: SS57 Enough is Enough

Threaded View

  1. #11

    Default

    Quote Originally Posted by wodyo View Post
    While your statement is correct, a friend in my alliance also could not login due to this same problem. He could tether to his smartphone's WiFi and gain access, and also was able to access the game from his workplace.
    Both of which would have different IP addresses...

    He could also login when he bypassed his router and plugged directly into his modem, thus eliminating the idea of an IP ban
    It is also possible that a different IP address was allocated by doing that, as it *IS* a different device connecting, and the previous device's DHCP lease had not expired.

    (Not to mention the countless times i had him unplug his modem & router for several minutes, which typically results in being issued a new IP address from the ISP).
    If an ISP has a DHCP lease renewal period of only a few minutes, that would be extremely bizzare. Depending on the size of the ISP, it could cause significant DHCP chatter on the network, degrading performance. Typically DHCP leases will be 24-72 hours, not minutes. The default for my Linksys WRT54GL router (802.11g wireless) is 24 hours. This means the computers local to my house attempt to renew their leases every 24 hours. I don't know what my internet provider's lease time is. I can attempt to find out, but I highly doubt it will be any less than 24 hours.

    When the device that has obtained a DHCP lease boots up, the device goes through what's called "Reallocation", where the device checks to see if the IP that it was leased is still available. If it is, then it will continue to use that IP. Some lease lengths are even longer than 24-72 hours, so it is unlikely that a unplug/replug of the same device would get a new IP unless the DHCP lease is very short, or you gave it a different MAC, thus forcing DHCP to consider it to be a different device, and thus allocating the "new device" a new IP address out of the DHCP address pool.

    I guided him through resetting his router, assuming it was just a configuration gone awry, but that was to-no-avail.

    I helped him find an setup a proxy server for his webbrowser, also to-no-avail.

    Finally, i saw the post about cloning the MAC address from his PC to his router, and that settled the issue.
    What is needed to be known is what was the IP before all that took place, and what is the IP after?

    If there is a TCP block of the range of, for example, and I mean EXAMPLE, as these addresses are not routed on the internet:

    TCP Block Range 192.168.1.0 - 192.168.1.255

    ...and your device had an IP before changing things around of...

    192.168.1.100

    ...but after changing things around, your device had the IP of 192.168.100.100, then regardless of what you think you may have done with the MAC address, the reason the new IP is not blocked is because it is no longer in the address range of the TCP block.

    The only truly possible way that MACs can matter is if IPv6 is involved. That seems unlikely, given that the bulk of the planet is still communicating over IPv4, but I suppose it might be possible. There are other more highly plausible explanations at the moment though.
    Last edited by neko_lord; 06-24-2011 at 08:57 PM.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •