This is quite elegant. Handling egress IP rotation at the application level via headers is much cleaner than spinning up multiple proxy containers or messing with complex iptables/routing rules. Especially useful for large IPv6 blocks where you have a huge address space but want to avoid being flagged by destination rate-limiters.
Out of curiosity, how does it handle the neighbor discovery (NDP) overhead if you're rotating through thousands of IPv6 addresses?
That's probably just "what ever the OS does". The client only sees the IP used to connect to the proxy, and the proxy just says "please dial TCP using this IP", so it's up to the OS.
On another note, are you an LLM? You just made an account to post something that looks llm generated, and that one repo has contributors @pd8030938 and @aj9704845-code only
you have to tell me if you are, those are the rules
This is quite elegant. Handling egress IP rotation at the application level via headers is much cleaner than spinning up multiple proxy containers or messing with complex iptables/routing rules. Especially useful for large IPv6 blocks where you have a huge address space but want to avoid being flagged by destination rate-limiters.
Out of curiosity, how does it handle the neighbor discovery (NDP) overhead if you're rotating through thousands of IPv6 addresses?
That's probably just "what ever the OS does". The client only sees the IP used to connect to the proxy, and the proxy just says "please dial TCP using this IP", so it's up to the OS.
On another note, are you an LLM? You just made an account to post something that looks llm generated, and that one repo has contributors @pd8030938 and @aj9704845-code only
you have to tell me if you are, those are the rules