You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
I am using the resolver to get incoming traffic on ipv4 and outgoing traffic on ipv6. This works nice, however I do have a need to rotate outgoing IPv6 traffic, it appears that if I do set the preferred outgoing IP address on server by deprecating the IPs I do not want to use as source this works for ping and traceroute, but not for SNIPROXY, sniproxy will keep using the same source IPv6 IP that was set as primary when it was started, restarting SNIPROXY will fix this behaviour, but given I need to rotate every 1 min this is not an option, is there anyway around this ?
Regards
The text was updated successfully, but these errors were encountered:
Are you specifying the source address in the configuration file? If so sniproxy will bind to that address before establishing the outgoing connection. If not, it should use the the default source IP allocated by the kernel. As far as I know on Linux, this should be the non-deprecated IPv6 address of the appropriate address scope on the interface nearest the route to the destination host. IPv6 source address selection logic is specified here: https://tools.ietf.org/html/rfc6724#section-5, without more specifics I can't look into this any further.
Hi
I am using the resolver to get incoming traffic on ipv4 and outgoing traffic on ipv6. This works nice, however I do have a need to rotate outgoing IPv6 traffic, it appears that if I do set the preferred outgoing IP address on server by deprecating the IPs I do not want to use as source this works for ping and traceroute, but not for SNIPROXY, sniproxy will keep using the same source IPv6 IP that was set as primary when it was started, restarting SNIPROXY will fix this behaviour, but given I need to rotate every 1 min this is not an option, is there anyway around this ?
Regards
The text was updated successfully, but these errors were encountered: