I´m wondering about the contents of the tcp stack, and what hardware specific data gets sent out with each tcp package (other then MAC address).
The thing is; I have an account at an satellite ISP that´s limited to 150mb of download quota per month...but i´m able to reset that quota when i log-in (via a HTTPS web page) with another cpu on the local network (all LAN cpu´s go through a single NAT gateway). So, even though the login request always comes from the same ip address, the quota gets reset if the request comes from a different cpu each time. (same thing happens if new OS is installed)
I´ve tried spoofing the mac adress of the machines while logging in, but without success.
: I am therefore wondering if the ISP´s quota tracking software is tracking some element of the tcp stack that is machine/os specific, rather then the given ip address of the gateway machine.
Anyone have any ideas ?
The thing is; I have an account at an satellite ISP that´s limited to 150mb of download quota per month...but i´m able to reset that quota when i log-in (via a HTTPS web page) with another cpu on the local network (all LAN cpu´s go through a single NAT gateway). So, even though the login request always comes from the same ip address, the quota gets reset if the request comes from a different cpu each time. (same thing happens if new OS is installed)
I´ve tried spoofing the mac adress of the machines while logging in, but without success.
: I am therefore wondering if the ISP´s quota tracking software is tracking some element of the tcp stack that is machine/os specific, rather then the given ip address of the gateway machine.
Anyone have any ideas ?