This is probably a bad idea. If you don't have access to or control over your local firewall, there is most likely an organizational reason for that (security). Opening up your development webserver to the public Internet without asking permission from your IT department first is a good way to either get hacked or to at least make some enemies within your corporate security department.
If you have access to your firewall, why not just open it up yourself?
> If you have access to your firewall, why not just open it up yourself?
If I want to temporarily open up my dev server so I can demo something to a client, this is beneficial because 1) it's a single line in my local terminal, not 30 clicks in a crappy router web admin and 2) it disappears as soon as I close the tunnel, I don't have to remember to undo the firewall changes.
Maybe you are at an airport. Or an internet café. Or visiting a client and don't want to mess with his network. Many web developers are actually pretty mobile these days.
If you have access to your firewall, why not just open it up yourself?