We were using the mobile wifi network for the Android and B2G phones which allowed them to connect to the test server running on the office network. It appears that has gone away. There is a perfy network that was previously used for testing and there is a new ateam network. Neither of these have access to the office network, so we'll have to get the test server onto one of these networks and then configure the phones to use it as well. We'll probably also have to change the mozbench framework to be able to specify which interface on which to listen.

I spent a few hours on this today and worked with wlach in Toronto to get the phones on the "ateam" wireless network. Unfortunately this network while allowing internet connectivity, does not allow access from the phones back to the test host machine, even if the host is placed on the same wireless network. The next option will be to try the 'perfy' network and see how that goes. In the meantime, I'll commit the code that allows the test server to listen on different hosts.

Another option would be to remove the three mozbench test machines from the Toronto office network and put them on a network where the phones could reach them without security concerns. The two phones and three computers need to be able to communicate with each other, they need to be able to reach the internet and I need to be able to SSH into them from the Toronto VPN, but we don't need any other connectivity. :justdave, not sure if you're the person to ask how feasible this would be, but maybe you can point me in the right direction :) Thanks!

I see no hostnames or IP addresses in this bug. Need more info to tell you what happened. :-) Was this the eideticker server? If so, it moved inside the ateam vlan (for exactly that reason). If this is a different server used for a similar purpose, then yes, it should do the same.

Had a successful B2G build this morning so it looks like moving to the ateam vlan has fixed things here.