You can either run offline with the -o switch or by adding <offline>true<offline> to your settings.xml.
It's worth pointing out though that Maven may fail the build when running offline if it decides it needs to check for dependency or plugin updates. If you set your repositories with <updatePolicy>never</updatePolicy> you can avoid this, but you'll need to force updates periodically (with -U and/or -cpu).
If you are using a repository manager, you can set your repository to be a mirror of the external repositories. This still involves a network connection, but only your internal network (or if the repository manager is on your local machine, no connection at all).
For example this config redirects all calls to central to my local Nexus server running on my development box:
<mirrors>
<mirror>
<id>central-proxy</id>
<mirrorOf>central</mirrorOf>
<url>http://localhost/nexus/content/groups/public</url>
</mirror>
</mirrors>