arisuchan    [ tech / cult / art ]   [ λ / Δ ]   [ psy ]   [ ru ]   [ random ]   [ meta ]   [ all ]    info / stickers     temporarily disabledtemporarily disabled

/tech/ - technology

Name
Email
Subject
Comment

formatting options

File
Password (For file deletion.)

Help me fix this shit. https://archive.arisuchan.jp/q/res/2703.html#2703

Kalyx ######


File: 1498781730248.jpg (5.33 KB, 300x220, stuff.jpg)

 No.749

Hello fellow Lains, I know a lot about computers and programming, but yet I lack knowledge in networking and how the Internet works. Do you know any good resources to learn these? I'm thinking about those protocols, netmasks, ports, nat etc.

 No.750

File: 1498790399240.jpg (108.48 KB, 736x522, servers.jpg)

Were to learn it? Do it.

Look how many devices you are surrounded by that use IP. There are so many ways you can get into it.

Try doing basics, changing IP's, running a network without DHCP, setup your own DHCP server!

Set up your own router, manager your own DNS with filtering, lots of things you can do!

But you can find all sorts of old books at used book stores, the basics are still the same old soykaf, or get in the tracker, there are heaps of PDF's that can get you started.

Try PFSense on a old Computer its a good router OS

 No.751

go for certificates

first learn basics and basics around mainstream systems
comptia a+

then go for networking
cisco ca

parallel to top learn a programming language. just pick one. easier to apply is better.
python/javascript/ruby

then go for a stack

then go for assembler

volume over quality. just spit code out like you go to the toilet
and apply code to the knowledge you gained in the certs.

voila you know a lot of stuff

 No.754

Two books get usually recommended, Computer Networking: A Top-Down Approach by Kurose & Ross, and Computer Networks by Tanenbaum & Wetherall. I can't comment on them as I've not read them.

What I would recommend is getting some high-level overview of the whole network stack, and then choosing a protocol or maybe application you are interested in, and studying how it works with Wireshark or similar tools. You could even read the specifications and confirm what you read using a network sniffer.

 No.764

>>754
Hosted the 6th edition by the author if you're curious.
http://www.bau.edu.jo/UserPortal/UserProfile/PostsAttach/10617_1870_1.pdf

 No.775

>>751
seems useless to me to learn Cisco specific things when you want to learn networking and first learning a higher language and then going to lower levels will confuse the fuck out of most people.
It's useless to learn Cisco things unless you are going to work with Cisco devices all day.

for networking : http://intronetworks.cs.luc.edu/current/html/ or some online courses or tanenbaum book but beware it's big.
for programming : https://functionalcs.github.io/curriculum/

 No.777

>>775
This,

CISCO is a hunk of soykaf, and the routers are full of hardware backdoors.

Don't bother with them, CISCO is truly top tier sewerage. Learn the concepts, then learn how to put them in IPTables or linux.

 No.779

>>775
thanks a lot for your answer.

this is breddy good stuff.
will implement it for sure into my learning program.

sure going from a higher level language to a lower level language is more orientated around the idea
to get things started and yourself motivated without
boring the soykaf out of yourself trying to implement some easy soykaf.

the idea is to start coding and while you do finding the middle ground between complexity and effectiveness.
most people wont get assembler but maybe will like to get stuck on c++ as its not as complicated but low-level enough for their requirements.

otherwise they still can fallback to whatever fits their needs as the syntax doesnt change much. just complexity of problem solving increases.

going from low to highlevel has most of the time the effect to not even try after being overhelmed by the amount of work it needs to draw a simple rectangle in assembler.

just my opinion



[Return] [Go to top] [ Catalog ] [Post a Reply]
Delete Post [ ]