Seems like a simple problem:
Hmm...keeping two repos in sync with each other is non-trivial, I think. It would involve basically turning SVN into Mercurial or Git.
Simplicity is usually the best way, and it sounds like you already have a simple solution: Use the SVN Repository outside the firewall.
You've already said machines inside the firewall can reach it, and obviously machines outside can reach it... so that's everyone, so what justification do you have for a second SVN repository inside the firewall? If it's just as a back-up, then just back-up the one on the outside.
Let me know if I'm missing part of your requirements.
Another thought... if you have both internal and external SVN instances... what is to stop them both giving out the same changelist ID at the same time, for different purposes? If you're seeking a de-centralised solution you should look towards GIT rather than SVN.