Ever since flashing the 2.1 leaks (V1 and then V2), I have not been able to connect to my university's WPA2-enterprise wireless network. After I enter my login info (the network uses PEAP with MSCHAPv2, so it doesn't need any certificates), the phone connects as expected and gets a valid IP address, verifiable with netcfg. Before any traffic is allowed to pass to the outside world, however, the device connecting has to go to an authentication page in a browser. When I attempt to go to that page, I get an error titled "Data Connectivity Problem" that states "A secure connection could not be established" which only presents an option to acknowledge the error. Since I can't load that authentication page, the network is entirely unusable. I did not encounter this problem with 1.5, but since I'm running the V2 leak, reverting is not an option. Has anyone else seen this type of behavior? I can't identify if the problem is in the actual link not being established properly (seems unlikely, as the phone is given an IP address, but perhaps the PEAP layer is having some sort of issue?) or if it has to do with the SSL certificates used for the network authentication page (they're signed, but I'm fairly certain that the name if the site they're signed for is not the name that they've given the new auth server). Any help or direction would be greatly appreciated!