my guess is ::0.0

when you do a md5load "svd.md5mesh" there is no target named svd instead replace svd with * , so it should look like this

md5load "svd.md5mesh"
md5skin * "sniper.png"
md5spec * 150
md5glare * 0.5 1

also you might want a mask ;p

md5skin * "sniper.png" "sniper_mask.png"

that way you can control your specing
also a normal map might be nice :P any way...

what your doing by adding svd in the first arg is basically telling cube to look at svd.md5mesh, and find a group called svd (which i assume there is not one. By putting * you are saying look at svd.md5mesh and apply this too the whole mesh. I suggest chopping up your model into multiple parts (head, torso, arms, legs) and using separate texture for each, for efficiency reasons, but its not a requirement (NOTE IF YOU DO THIS YOU WILL HAVE TO MD5LINK THEM TOGETHER)

chaseter

PS: im not a md5 expert, so if i messed up some lingo, or completely bull faced lied to you, im sorrie ;p but i have exported a few things using md5, so im guessing that im right ;)

first of all, use proper group and mesh names (as being logical and simple). Using a lot of tags and separate meshes also isn't advisable; rather use 1 mesh and a few groups instead (again, keep it simple). This saves a lot of typos also.

It's best to arrange commands logical also, like directory-based (as like md5dir and md5load) together, mesh-based commands (as like md5load and md5pitch together, animation-based commands (all md5anim) together and appearance-based commands (md5skin, md5alphatest and md5ambient) together. Do the same thing for the common commands (as like mdlscale and mdlyaw).
This makes it way easier to find any problem with your config-file.

Now more specific to your config-file;
- Why is md5pitch left blank? it's a command which needs a specified group, else you could better use mdlpitch if it needs to be a general pitch anyway.
- Is the folder called 3 actually in the hudguns folder which is directly in the models directory?
- Where is tag_weapon? As far as I know, Sauerbraten even needs it to load the model as a weapon which should appear into the hud. Some playermodels seems to carry it inside their own instead of the guns, but can't see that in your situation.
- Are there different meshes running (as why else have you used md5link 0 1 tag_bicep, yet you aren't loading any other mesh?)
- What are the priorities of the animations? If it would consist out of 2 animations on 2 meshes (like bobbing your arm while running and shooting or keeping your arm in a steady position while standing still and firing)?

Enough to do...

P.S. If you really can't sort it out, then I would advice to configure mapmodels first to get a feeling how the commands actually work.
Blender has some md5exporters which should work for their assigned version. The more you import/export between programs, the more chance there is to lose certain data.
"*" only works when the name of the group is identical to the name of the mesh (as far as I've noticed).