Clustered NodeJS + Socket.io + sticky session simulating multiple connections

I'm building a clustered NodeJS app with Socket.io and sticky session for Socket.io to work properly.

One thing I noticed is that the sticky session uses the IP for load balancing, thus the same IP always connects to the same process. This is a bit problematic, as I want to simulated a large amount of socket.io clients that send data at the same time, but all of them will connect to the same process and the whole cluster won't be tested properly.

While each cluster node is created to work independently, it would still be nice to test and see if all of the nodes work properly when the app is clustered.

Is there a workaround?