If you feel that your area of interest is in networking, then you can go for that. However, here's one very common pitfall among a lot of network engineers in the market. They tend to be so focused on networks and networks alone to the point that they're totally lost at anything else IT related outside of networks. For larger projects, this can make the network team a big pain to deal with, especially when it comes to troubleshooting of issues, and trying to pin down where exactly problems are at, when you get people with different backgrounds working together.

This is not to discourage you, but is to alert you to the common problems among a lot of people doing networking. The trick is to not allow yourself to run into the same problem, and you'll find that this will greatly increase your worth to any projects, and most importantly, future projects as well.

Networking is a subset of IT, not CS

I got no idea how the course in UM is structured, but things like media, HTML and so forth is classified under Multimedia, of which is another subset of IT.

The only network related thing that a CS course should contain are the lower levels of networking. Actually, its more towards Data Communications, instead of just being concentrated on just networking alone.

So in a way, I do find it a bit odd that there can be a Networking major, unless what they really mean is Data Communications, as Networking by itself should not be a CS major.

Well, there's the 7 OSI levels of networking, of which is part of Data Communications.