**Bringing this discussion back to the bug report page**
Paul, one step at a time... the way we can tell that Firefox isn't (explicitly) the culprit is because the ping tests failed while on the wireless.
Now that you have a working ethernet connection, I would like for you to run the following command: apport-collect -p network-manager 484856
Make sure you run this command while both the wireless and wired connections are established. This should gather usefull information for us to see.
**Bringing this discussion back to the bug report page**
Paul, one step at a time... the way we can tell that Firefox isn't (explicitly) the culprit is because the ping tests failed while on the wireless.
Now that you have a working ethernet connection, I would like for you to run the following command: apport-collect -p network-manager 484856
Make sure you run this command while both the wireless and wired connections are established. This should gather usefull information for us to see.