I'm looking for a good Networking TUT / PDF if anyone can help, what ports or commonly used for what, so I can get me head round it better, I know how to set up a static IP and can plod on with basic tasks but I would like a more in depth knowledge of it all.

Example

Say I had 16 desktop computers attached to one 50mb internet connection how could I stop one from eating the bandwith from the other ones if someone started downloading at max speeds.

Would you have to limit each computers bandwith to 2mb, would you have to assign them all different ports if they were using p2p software upload and download.

Or could all 16 be using the same port.

Im just wanting a good book or tutorial so I can understand it all better is there any courses at college etc that concentrate on networking alone I would really like to get into it and have full knowledge of whats what, instead of watching people do it on utube etc and just copying going through the motions ha ha

Not actually done it myself (current router not supported), but check if you can install DD-WRT on your router so that you can play with the QoS and Tc Command settings.

In your scenario the bandwidth would be shared roughly equally. With QoS the bandwidth for a particular service would be limited i.e. 50% for download, 50% for everything else.

Are these too basic?

Professor Messer's Free CompTIA Network+ Certification Training Course | Professor Messer - CompTIA A+, CompTIA Network+, Certification Training (Videos)

IP Tutorial - Computer Networking Tutorial Course Outline (Text)

Originally Posted by Jooooles

I'm looking for a good Networking TUT / PDF if anyone can help, what ports or commonly used for what, so I can get me head round it better, I know how to set up a static IP and can plod on with basic tasks but I would like a more in depth knowledge of it all.

Example

Say I had 16 desktop computers attached to one 50mb internet connection how could I stop one from eating the bandwith from the other ones if someone started downloading at max speeds.

Would you have to limit each computers bandwith to 2mb, would you have to assign them all different ports if they were using p2p software upload and download.

Or could all 16 be using the same port.

Im just wanting a good book or tutorial so I can understand it all better is there any courses at college etc that concentrate on networking alone I would really like to get into it and have full knowledge of whats what, instead of watching people do it on utube etc and just copying going through the motions ha ha

When you say port do you mean port or physical connection on the switch or port as in TCP port - the port number of the TCP connection type (HTTP, P2P, FTP etc).

Networking is great especially when you start to look into port mirroring and network forensics, wont go into detail here as it may be a sensitive subject to discuss.

I sat the cisco ccna mate although with my experience i dont recommend it but that was mostly down to my college kruger also sat it and hes carried it on download some cisco ccna stuff mate off news groups usually some good test apps ill try digging out some old college stuff if you get into it.

to limit each pc bandwidth you will need a good home router usually in cases like this toy routers go out the window and the heavy metal oversized stuff comes in

cisco_router.jpg

i have one of these types i bought cheap off ebay to practice on, ive since put a full wired gigabyte network through out my flat going to my router and 2 switches i hate wifi lol but ive never looked into throttling the like of qos on home routers is more for things like ps3, qos = quality of service i cant remember exactly but it basically checks the data gets back and forward ok video stream from the web etc and it basically makes sure there is always bandwidth for the client using qos your only hope really is if you can get ddwrt on mate

Heres a link to a list of port numbers mate its a pdf so you will be able to download/save it List_of_Common_TCPIP_port_numbers.pdf

you can set up a Smoothwall Express Open Source Firewall Project on an old pc this is firewall and router has loads of settings bandwidth restrictions for ip add and or apps is available also internet availability matrix.


Express Feature List
Hardware support:

* Any Pentium class CPU and above – with a recommended minimum of 128MB RAM
* 64bit build for Core 2 systems
Firewalling:

* Supports LAN, DMZ, and Wireless networks, plus Extrnal.
* External connectivity via: Static Ethernet, DHCP Ethernet, PPPoE, PPPoA using various USB and PCI DSL modems.
* Portforwards, DMZ pin-holes
* Outbound filtering
* Timed access
* Simple to use Quality-of-Service (QoS)
* Traffic stats, including per interface and per IP totals for weeks and months
* IDS via automatically updated Snort rules
* UPnP support
* List of bad IP addresses to block
Proxies:

* Web proxy for accelerated browsing
* POP3 email proxy with Anti-Virus
* IM proxy with realtime log viewing
UI:

* Responsive web interface using AJAX techniques to provide realtime information
* Realtime traffic graphs
* All rules have an optional Comment field for ease of use
* Log viewers for all major sub-systems and firewall activity
Maintenance:

* Backup config
* Easy single-click application of all pending updates
* Shutdown and Reboot from UI


I have it running on an old compaq deskpro en 700 with onboard netcard to my modem and then two network cards one to a switch for wired network on 192.168.0.x and the other to a wireless router on 192.168.1.x for all our wireless devices.

it is linux but in all honesty you dont need any linux knowledge to setup and use, setup is via dos/novell type screens and once setup you can setup bios to not stop on keyboard error and remove keyboard and monitor as anything you do is via secure web browser also has linux AV client running to get any virus's in pop3 email (very useful)

Wow! Overload...!

Looks like no-one understands TCP/IP and ports then lol

TCP/IP is NOT a protocol - it's a suite of protocols. TCP is one such and UDP is another. TCP is 'connection oriented' i.e. it checks delivery has occurred - UDP is 'connectionless' i.e. it doesn't. TCP uses UDP as the delivery protocol. Both TCP and UDP have 65,535 associated ports.

Services such as web servers listen on ports i.e. web servers listen on port 80, they expect clients to connect TO port 80, clients do NOT usually connect FROM port 80. Clients connect FROM a randomly selected port based on what ports are available on the local machine.

Ports are assigned based on the service connecting i.e. a firewall running NAT allocates connection ports, the connected service replies to the connecting port. This is how a web page returns to the connecting computer behind a firewall - the firewall allocates a port for the client, the web server replies to the connecting port, the firewall refers the connection back to the client - simples

@Him Her its not that folk dont know what tcp/ip is or what ports are, (if you care to search in the pc section you will find there are many who do).

The op asked with the first line of his post about this and then gave an example of something totally different.

Most like me assumed he wanted an answer to his example and not really how he phrased that first line. I find the best way to learn is to get some kit in front of you and have a play normally better than a book....most people have an old pc in a cupboard or loft and setting up a hardware firewall is a good way to learn.

@Hatab - guess I was just trying to nail down what the question is. My first post suggested some free on-line tutorials and while I agree that playing with kit helps you to set up a given scenario it doesn't tell you WHY/HOW it works

I haven't found anything that explains ports very well so I'd appreciate a link to any posts on here...