Best lans books according to redditors

We found 75 Reddit comments discussing the best lans books. We ranked the 21 resulting products by number of redditors who mentioned them. Here are the top 20.

Next page

Top Reddit comments about LANs:

u/andralex · 197 pointsr/pics

My sister's. I kid you not. Fragment of the large painting is featured on a book of mine.

u/koeningyou666 · 73 pointsr/netsecstudents

In my opinion; every book in this bundle is a bag of shit.

Here's a list of reputable books, again in my opinion (All links are Non-Affiliate Links):

Web Hacking:

The Web Hackers Handbook (Link)

Infrastructure:

Network Security Assessment (Link)

Please Note: The examples in the book are dated (even though it's been updated to v3), but this book is the best for learning Infrastructure Testing Methodology.

General:

Hacking: The Art of Exploitation (Link)

Grey Hat Hacking (Link)

Linux:

Hacking Exposed: Linux (I don't have a link to a specific book as there are many editions / revisions for this book. Please read the reviews for the edition you want to purchase)

Metasploit:

I recommend the online course "Metaspliot Unleashed" (Link) as opposed to buying the book (Link).

Nmap:

The man pages. The book (Link) is a great reference and looks great on the bookshelf. The reality is, using Nmap is like baking a cake. There are too many variables involved in running the perfect portscan, every environment is different and as such will require tweaking to run efficiently.

Malware Analysis:

Practical Malware Analysis (Link)

The book is old, but the methodology is rock solid.

Programming / Scripting:

Python: Automate the Boring Stuff (Link)

Hope that helps.

u/DucBlangis · 20 pointsr/netsecstudents

Here is a "curriculum" of sorts I would suggest, as it's fairly close to how I learned:

  1. Programming. Definitely learn "C" first as all of the Exploitation and Assembly courses below assume you know C: The bible is pretty much Dennis Richie and Kernighan's "The C Programming Language", and here is the .pdf (this book is from 1988, I don't think anyone would mind). I actually prefer Kochan's book "Programming in C" which is very beginner freindly and was written in 2004 rather than 1988 making the language a little more "up to date" and accessible. There are plenty of "C Programming" tutorials on YouTube that you can use in conjunction with either of the aforementioned books as well. After learning C than you can try out some other languages. I personally suggest Python as it is very beginner friendly and is well documented. Ruby isn't a bad choice either.

  2. Architecture and Computer basics:
    Generally you'll probably want to look into IA-32 and the best starting point is the Intel Architecture manual itself, the .pdf can be found here (pdf link).
    Because of the depth of that .pdf I would suggest using it mainly as a reference guide while studying "Computer Systems: A Programmers Perspective" and "Secrets of Reverse Engineering".

  3. Operating Systems: Choose which you want to dig into: Linux or Windows, and put the effort into one of them, you can come back to the other later. I would probably suggest Linux unless you are planning on specializing in Malware Analysis, in which case I would suggest Windows. Linux: No Starch's "How Linux Works" is a great beginner resource as is their "Linux Command Line" book. I would also check out "Understanding the Linux Kernel" (that's a .pdf link). For Windows you can follow the Windows Programming wiki here or you can buy the book "Windows System Programming". The Windows Internals books are generally highly regarded, I didn't learn from them I use them more as a reference so I an't really speak to how well they would teach a "beginner".

  4. Assembly: You can't do much better than OpenSecurityTraining's "Introductory Intel x86: Architecture, Assembly, Applications, & Alliteration" class lectures from Xeno Kovah, found here. The book "Secrets of Reverse Engineering" has a very beginner friendly introduction to Assembly as does "Hacking: The Art of Exploitation".

  5. Exploitation: OpenSecurityTraining also has a great video series for Introduction to Exploits. "Hacking: The Art of Exploitation" is a really, really good book that is completely self-contained and will walk you through the basics of assembly. The author does introduce you to C and some basic principles of Linux but I would definitely suggest learning the basics of C and Linux command line first as his teaching style is pretty "hard and fast".

  6. Specialized fields such as Cryptology and Malware Analysis.


    Of course if you just want to do "pentesting/vuln assessment" in which you rely more on toolsets (for example, Nmap>Nessus>Metasploit) structured around a methodology/framework than you may want to look into one of the PACKT books on Kali or backtrack, get familiar with the tools you will use such as Nmap and Wireshark, and learn basic Networking (a simple CompTIA Networking+ book will be a good enough start). I personally did not go this route nor would I recommend it as it generally shys away from the foundations and seems to me to be settling for becoming comfortable with tools that abstract you from the real "meat" of exploitation and all the things that make NetSec great, fun and challenging in the first place. But everyone is different and it's really more of a personal choice. (By the way, I'm not suggesting this is "lame" or anything, it was just not for me.)

    *edited a name out





u/curtisb · 19 pointsr/programming


> Alexandrescu didn't create the D language...

I don't think that's what the original commenter (or perhaps the source they were quoting) was saying. Rather, they were saying that Alexandrescu was the author of the book the The D Programming Language.

u/gored_matador · 15 pointsr/networking

> It's not something you can pick up from a book

It's totally something you can pick up from a book. It's not magic.

Practical Packet Analysis

u/pat_trick · 12 pointsr/learnprogramming

If you want to pick up some Cryptography, The Code Book is a great intro.

Pragmatic Thinking and Learning is good for learning to learn.

The Pragmatic Programmer is good for project code planning and learning how to write code in a well thought out way.

Ethernet: The Definitive Guide is a good read if you want to get up to snuff on your networking, though it can be a bit dry at times.

u/moch__ · 10 pointsr/networking

Vendor neutral and probably the best/most frequently recommended book:

MPLS-Enabled Applications: Emerging Developments and New Technologies

Very good Cisco-centric MPLS book:

MPLS Fundamentals

The gold standard, or so I hear, for L2VPN (I believe it's Alcatel/Juniper heavy):

Designing and Implementing IP/MPLS-Based Ethernet Layer 2 VPN Services: An Advanced Guide for VPLS and VLL

u/dallbee · 8 pointsr/d_language

Really happy to see interest in D. I think it's an excellent programming language to start with, and there's a few more resources than you might think.

Great introduction to programming in general
http://ddili.org/ders/d.en/index.html

A more advanced overview of D
http://www.amazon.com/D-Programming-Language-Andrei-Alexandrescu/dp/0321635361

Make sure to check out Rosetta Code for tons examples:
http://rosettacode.org/wiki/Category:D

Web programming is a good way to start out
http://vibed.org/

For an example web project, used in production:
https://github.com/rejectedsoftware/vibenews

Most of these links can of course be found at:
http://wiki.dlang.org/Books

Make sure you check out the new API documentation:
http://dlang.org/library/index.html

And don't miss out on all of the great projects in D:
http://wiki.dlang.org/Open_Source_Projects
http://code.dlang.org/

If you have any questions, you can always post on the forums, but I've found that an even better way to get feedback is through the #D channel on irc.freenode.net.

Feel free to message me directly with questions too! I'm relatively new to the language myself, but I have a solid background in other languages and I'm transitioning to D as my go-to language.

u/nascent · 7 pointsr/programming

> Definitely want to try using it once Alexandrescu's book comes out and 2.0 becomes stable.

u/MirageRealms · 7 pointsr/libgdx

I'm the developer of Mirage Realms (www.miragerealms.com) which is an MMORPG written using LibGDX and I also had absolutely no idea wtf I was doing when I started.

I looked into Kryonet as another user has suggested but in the end found I wanted to know a lot more about networking so ended up just writing my own stack. The book that helped me was Java Network Programming https://www.amazon.co.uk/Network-Programming-Elliotte-Rusty-Harold/dp/1449357679 which I mainly used as a reference for TCP sockets and streams - if that's what you need.

The first steps are really figuring out if you are going TCP or UDP, and if you are going to have a hard split between client / server or not. An example of a hard client / server would be world of warcraft or counterstrike. An example of a soft server would be something like quake 2 where the host client is effectively the server.

There is also platform to consider, if you are going for a networked game on mobile phones you are going to have lag and are going to have to figure out ways of working around it via either interpolation or some other means. It's not all packet loss and internet speeds either, the radios in phones suck and you have some random milliseconds of delay just getting the incoming data from the radio depending on how it is currently power cycling, so if its really time critical you can forget the overheads of reflectively looking up packet handlers and such.

If you are just on the PC, life is easy and you can take serious liberties given how fast peoples machines and internet connections generally are these days.

TLDR;

Sounds dumb but figure out what you want before starting anything in terms of a basic architecture and network requirements. Learn the trade-offs between TCP and UDP. You can then focus your time on finding tutorials that fit those requirements i.e. googling "thread per connection TCP server socket" will give you much more to work with than googling "how to make a multiplayer game"!

Liam

u/jeremiahs_bullfrog · 5 pointsr/d_language

There's Andrei Alexandrescu's book, The Day Programming Language, which has been well received. Andrei is one of the language designers and joined Walter Bright pretty early in the process of designing D2, the current version of D.

I haven't read it (I prefer online documentation and forums), and I'm unfamiliar with the book you mentioned (I'm mostly familiar with K&R's C).

Anyway, hope this helps!

u/Majestic-Falcon · 5 pointsr/mikrotik
u/km_irl · 5 pointsr/networking

Other books I can recommend from O'Reilly are JunOS Enterprise Routing, JunOS Enterprise Switching, and Juniper SRX Series. I bought them all as epubs when O'Reilly was still selling them directly and I have found them very useful for my day to day work with Juniper gear.

u/zhaopuming · 5 pointsr/programming

Andrei's book on D: "The D Programming Language" would be another great read whether you are looking into the D language or not, it is a great read for general programming design IMHO :-)

u/kWV0XhdO · 5 pointsr/networking

I've provided two citations in this thread. Mind sharing the document you're talking about?

edit: one more, section 2.1.1

If the port on which the frame is received is the same port where the target destination resides,
the bridge can simply discard the frame because it can be assumed that the target will have
received the frame through the normal LAN delivery mechanisms.

edit 2: If you still have doubts, take a look at the 2 switch topology I supplied elsewhere in this thread. I think we can all agree that the lower switch will flood a C1 -> C2 frame to the upper switch after C2's link drops.

At this point, the lower switch will know to reach "C1" via C1's access port. The upper switch will know to reach C1 via the lower switch. Reachability to C1 is correct throughout the topology.

If the upper switch forwards the frame back toward the lower switch (because that's where C2 is) the lower switch CAM table will get corrupted: The lower switch will re-learn C1 via the upper switch. Obviously wrong.

u/bretbrown · 5 pointsr/programming

I found The D Programming Language to be very enjoyable, and it is basically the D bible right now.

The main D website is now dlang.org. Most (all?) of the links on the sidebar are up-to-date in my experience. Check out the Articles section of the sidebar especially. The library reference is autogenerated from the release source code, so it's up-to-date.

If you want help from actual people, there is a lot of action on D.learn on forum.dlang.org.

There's also /r/d_language. It doesn't seem as active as the D forums, but the D creators and many of the principle developers are redditors.

And of course, you can filter on D at Stack Overflow. Again, I've seen D developers on there answering questions, so don't be afraid to ask questions.

u/sciencewarrior · 4 pointsr/awwnime
u/JavaAndMIPS · 3 pointsr/javahelp

Make a personal project. I made a game editor.



Read more books.

Java Swing:

https://www.amazon.com/Java-Swing-Second-James-Elliott/dp/0596004087

Java I/O:

https://www.amazon.com/dp/0596527500/

Java Generics and Collections:

https://www.amazon.com/Java-Generics-Collections-Development-Process/dp/0596527756/

Java Concurrency:

https://www.amazon.com/Java-Threads-Understanding-Concurrent-Programming/dp/0596007825/

Java Network Programming:

https://www.amazon.com/Network-Programming-Elliotte-Rusty-Harold/dp/1449357679/

Java Web Services:

https://www.amazon.com/dp/1449365116/

Java Database Programming:

https://www.amazon.com/dp/1565926161/

Java Performance:

https://www.amazon.com/dp/1449358454/

Intro to Design Patterns w/ Java:

https://www.amazon.com/Head-First-Design-Patterns-Brain-Friendly-ebook/dp/B00AA36RZY/

Design Patterns (not Java and very dry, but much more in depth):

https://en.wikipedia.org/wiki/Design_Patterns

If you read every O'Reilly book on Java and do two or three big projects (or ten small ones) with what you learn in each book, you will learn how to do anything with Java. Java can do anything any other language can, but it takes longer to get there. Once you get there - once you build it - it will run forever, provided it's built well.



Online resources.

http://www.tutorialspoint.com/swing/

https://www.javatpoint.com/java-swing

The javax.swing class:

https://docs.oracle.com/javase/7/docs/api/javax/swing/package-summary.html

The Java API specification:

https://docs.oracle.com/javase/7/docs/api/

Never took one of these, defer to someone else's advice:

https://www.udemy.com/java-swing-complete/

It takes a while to figure out how to effectively use google. Look up my posting history to see how to format posts. You may need to make a test class to simplify things or provide a simple (and obviously safe) thing that people can execute and debug, if they decide to help you.

You will spend a lot of time on the Java API spec, so make sure that you know how to read a method header and signature. You'll get used to it after a few weeks.

*

General advice.**

Debugging is the single most important thing you do. If you can't see what's going wrong, you won't fix it except via trial and error (which is frustrating and takes forever). Any time something goes wrong, either walk through it with a debugger or get print statements working. Getting print statements working is often a job in itself.

I spend more time debugging than I do programming, because when things are going right it's a breeze but when they aren't it takes ages.

Take up some other hobby that keeps you active.

When you're frustrated and nothing is working, do something else. Go for a walk, garden for a bit, cook something. Make sure you have a notepad or note-taking program on your phone so you can stop and take notes when the solution comes to you.

If nothing else is working, just screw around with things and make print statements to see what they do. That's how I learned everything.

Try to break everything.

Don't be afraid of embarassing yourself.

u/blizz017 · 3 pointsr/AskNetsec
u/blacksheep322 · 3 pointsr/Network

Start with reading the IEEE 802 standard. Then 802.1X. Then move into 802.11.

Matthew Gast authored a couple books, 802.11 Wireless Networks: The Definitive Guide (https://www.amazon.com/dp/0596100523/) another for 802.11ac (https://www.amazon.com/dp/1449343147). Start with the beginning and step though the 802.11 standard and groups.

While you could “just Google it”, you won’t learn the why and the what - just the how. If you really want to learn it, Gast’s books are really good at walking through history and standards (which they should, he sits on the IEEE 802.11 committee).

u/dalgeek · 3 pointsr/Cisco

Cisco Wireless LAN Controller Configuration Guide, Release 7.0 - it's only a 28MB PDF ;)

I found this on Amazon which may be more digestable: Controller-Based Wireless LAN Fundamentals

I normally refer to the configuration guide as needed, I learned most of my wireless stuff the hard way.

EDIT: If you do find books on the subject, make sure you check the versions covered. There are significant differences between 4, 5, 6, and 7, to the point where some major features are completely missing or moved. Also, if you're using anything below 7 then you're going to have a bad time.

u/apt_snake_oil · 3 pointsr/singapore

I think very poorly of the cyber security courses offered (except NUS) in Singapore, as the things they teach are not aligned with the industry practices - either outdated or just not practical enough.

Having said that, if you have the time, I would suggest taking the SIT degree instead of the diplomas (waste of time IMO) and hopefully it provides you the fundamentals (programming, network and system administration) and be exposed to some other topics in cybersecurity.

If you are doing a career switch, I suppose you want to get up to speed fast by focusing on the need to have knowledge as a baseline. I would suggest taking the time to go through these stuff in details, setup your labs and practice the stuff

  1. https://www.cybrary.it/course/comptia-network-plus/
  2. https://www.amazon.com/Kali-Linux-Revealed-Penetration-Distribution/dp/0997615605
  3. https://www.amazon.com/Network-Security-Assessment-Know-Your/dp/149191095X
  4. https://www.amazon.com/Web-Application-Hackers-Handbook-Exploiting/dp/1118026470

    Other wise, there are hands on courses and industry certifications that you can take online at your own pace and employers look out for such as:

  5. https://www.elearnsecurity.com/training_paths/ (eLearnSecurity is good because they have a progression path from student onwards )
  6. https://www.offensive-security.com/information-security-certifications/oscp-offensive-security-certified-professional/ (I don't encourage going for this as a starter unless you already have some fundamental knowledge and skillets for system administrations but this is highly recognised in the industry)
  7. You can also go for SANS or what not, I think it's just too expensive for my liking.

    There is no one path to becoming a good pentester. However from my observations, folks who tend to be more in demands (with or without certifications/formal educations) are those who can display the ability to learn stuff on their own. This is an industry of skills and continuous learning. For employers that pay top dollar and provide time for training, learning and research, they are looking for folks who can display those stuff through actions.

    ​

    Source: Pentester
u/ArkionA · 3 pointsr/ITCareerQuestions

Absolutely love being a pentester and the cyber security industry. If you are willing to put in the time and study it can be very rewarding. CEH is a good step in the right direction and should open doors for you.
For entry level positions, pentesting is usually split into two areas, web application and internal/external infrastructure. It's good to have knowledge of both but it's worth choosing which area interests you the most. Personally, I specialise in web applications & API and there is a lot of online resources to help you. (As you have mentioned owasp top 10, I'll assume web apps is your interest)


The best way to learn a vulnerability and get a good understanding is to create vulnerable web pages (this also gives you something to take into an interview). I would suggest doing some basic LAMP stack (Linux, Apache, Mysql, PHP) - Don't let this put you off as it's actually pretty simple. If you can make a few vulnerable pages to display vulnerabilities, you will fly through entry level interviews.


it's really simple to do.. Here is a form that is vulnerable to cross-site scripting. (a few lines of php with some html)
---

<form method="POST" action="">

<p> <input type="text" name="xss"/></p>

<input type="submit">

<?php
$value = $_POST['xss'];
echo $value;
?>

Reading Material:

https://www.amazon.co.uk/Web-Application-Hackers-Handbook-Exploiting/dp/1118026470

https://www.amazon.co.uk/Network-Security-Assessment-Know-Your/dp/149191095X


Practical learning
DVWA (Damn Vulnerable Web App) - Purposely vulnerable web pages to practice exploiting.
http://www.dvwa.co.uk/


Once you have a bit of experience have a look at hackthebox

https://www.hackthebox.eu/

u/acehreli · 3 pointsr/programming

Andrei's book is just great, covering language design considerations as well:

http://www.amazon.com/D-Programming-Language-Andrei-Alexandrescu/dp/0321635361

Also, I don't know about good :) but I am translating my Turkish book on D into English, which is geared towards the novice programmer:

http://ddili.org/ders/d.en/index.html

u/ahdguy · 2 pointsr/networking

Read (and try to understand):
[Ethernet fundamentals!]
(http://www.amazon.com/gp/product/1565926609/ref=oh_details_o08_s00_i00?ie=UTF8&psc=1)
[Internetworking with TCP/IP!]
(http://www.amazon.com/gp/product/0131876716/ref=oh_details_o06_s00_i00?ie=UTF8&psc=1)

Both are good books and essential reading for anyone working in networks (if you want to be any good at it)...

u/[deleted] · 2 pointsr/learnprogramming

Do you know any other languages? I'm familiar mainly with C and C++ and after looking at some D it doesn't seem too far off....

Anyways, this book will serve you well
The D Programming Language

or try this:
http://www.learn-programming.za.net/programming_d_01_getting_started.html

If anyone else comes in here, what are your views on D? is it worth learning? I just don't see how it's that much different from C and C++.

u/UndeadBelaLugosi · 2 pointsr/sysadmin

I'm glad you found your answer. For complete (very) documentation on Nagios I suggest this book. It's what got me really started.

u/ZMeson · 2 pointsr/programming

> As for D, it does not even exist in real world.

It does. It just needs some good tools support.

For reference Python first appeared in 1991, but didn't really gain wide acceptance until well after 2000. Ruby first appeared in 1995, but didn't gain wide acceptance until RoR was open sourced in 2004.

D was first designed in 1999. It's starting to gain more and more acceptance -- Andrei Alexandrescu is writing a book on it. This is about the time languages really start gaining traction. We'll see what happens in the next few years.

u/Rigermerl · 2 pointsr/rmit

When I did Network Programming last year I found most of the work and assessed material matched closely to what's in this book:https://www.amazon.com/Network-Programming-Elliotte-Rusty-Harold/dp/1449357679

Java Network Programming: author = Rusty Harold.
The tutorials were pretty much all lifted directly from this book.

Just following that will probably be enough to get you through.

Had a good lecturer when I did it though.

u/eco_was_taken · 2 pointsr/SaltLakeCity

Umm, I think Python is a good language to start with. It's forgiving and low on boilerplate code. I haven't read it but Learn Python the Hard Way by Zed Shaw is supposed to be decent (and it's free online). I didn't like Learning Python published by O'Reilly. I'd just read reviews on Amazon if Learn Python the Hard Way isn't working for you. Whichever you end up with, I recommend typing all examples from the book into the computer by hand. Something about doing this really helps make things stick in your head. You'll also make the occasional typo and have to debug your program which is something we programmers spend more time doing than any of us care to admit.

I think it is important to try to think of something you want to make and have it in mind while you are learning the language. It can be any software but I recommend a video game. They are really good for this because you can just think up a simple concept or implement your own version of an existing game. Having a goal makes it so you are constantly solving the problems you will encounter while trying to reach that goal which is the most important part of programming (more so than learning the syntax of the language). This is actually the highest rated Python book on Amazon and is all about gamedev with Python.

After you've learned Python to the point where you are comfortable (no need to master it), learn other languages to grow as a programmer. Once you've gotten a couple languages under your belt it's actually really easy to learn even more languages (unless it's a very odd language like Haskell, Lisp, or Brainfuck). The problem solving skills you've acquired often work in any language and you learn some new techniques as you learn new languages.

u/d4rch0n · 2 pointsr/compsci

If you're looking for an intro that will get you doing hands-on stuff quickly, I definitely recommend "Practical Packet Analysis: Using Wireshark...". Only if you want something that's far from textbook-y and will give you some insight into doing casual sysadmin type stuff. Also, "Nmap Network Scanning" will get you doing some hands-on fun activities as well. Just pay attention to local laws before doing anything that might raise red flags.

u/occasionallylost · 2 pointsr/wisp

Udemy course
CWNA
802.11ac
802.11n
802.11 SG
I personally met GT at a Ruckus conference and the dude is sharp. Don't pay the full price (retailmenot) if you enroll. Lots of good info there. You could prob skip the AC guide since that's a little to new for it to be relevant just yet. But def look at the 802.11n literature. This will put you eons ahead of most people.

u/the_omega99 · 2 pointsr/learnprogramming

D is starting to become more popular. It's graced the frontpage of /r/programming a bit recently. One recommended resource is the book written by one of the language's developers: The D Programming Language.

u/Lourido · 2 pointsr/networking

"Practical Packet Analysis" is by far my favorite Wireshark book.

edit: I should probably mention the book was published in 2011, so some of the information is regarding older technology, but the book is still fantastic.

u/jabbalaci · 1 pointr/Python

If you are interested in C++ but afraid of it, consider the D language. Unfortunately it arrived too late so it's not well-known.

u/jacques_chester · 1 pointr/programming

Non-affiliate link to book.

edit: I regret that this comment lead to an off-topic sprawl.

u/clvx · 1 pointr/sysadmin

Nagios is really easy to manage.. however, if you find yourself struggling with it, you should read at least the official documentation[1], or any of these books[2,3].. in fact, I encourage to read the books.

[1] http://nagios.sourceforge.net/docs/nagioscore/4/en/toc.html
[2] http://www.amazon.com/Nagios-Network-Monitoring-Wolfgang-Barth/dp/1593271794
[3] http://www.amazon.com/Building-Monitoring-Infrastructure-Nagios-Josephsen/dp/0132236931

u/SuperDefcon5 · 1 pointr/raspberry_pi

Here is a really good book for Wireshark: https://www.amazon.com/dp/1593272669/_encoding=UTF8?coliid=I11HBIRF55QCWX&colid=1QE51EOZ8AY1G

/r/Wireshark has some helpful posts either on the side or if you sort by top/all.

Wireshark can be intimidating at first with all the I information you get but if you follow some guides you will do good.

u/Zolomon · 1 pointr/gamedev

Java Network Programming (http://www.amazon.com/Network-Programming-Elliotte-Rusty-Harold/dp/1449357679/) is actually a very good book that introduces network programming in the Java language. Don't mind that it is focused on Java, the concepts it walks through can be found in almost any programming language (same shit, different name).

It talks about writing multithreaded applications, using UDP, TCP, etc. However, if you wonder how to incorporate physics simulations I would suggest you google for Gaffer On Games for his networking guide.

u/SilentLennie · 1 pointr/homelab

For you Dutch people, some people in the Netherlands have that as a association:

https://coloclue.net/

https://soleus.nu/

And a lot more fun if you can actually connect to Internet exchanges like AMS-IX: https://ams-ix.net/ (lots of others you can do peering with)

See:

https://lg.coloclue.net/birdseye/app/routeservers/2

On the topic of BGP, I would start with this book:

https://www.amazon.com/exec/obidos/ASIN/0596002548/ref=nosim/muada-20

u/3legcat · 1 pointr/gifs

This book might be an interesting resource:
[Wi-Fi Toys: 15 Cool Wireless Projects for Home, Office, and Entertainment (ExtremeTech)] (http://www.amazon.com/Wi-Fi-Toys-Wireless-Entertainment-ExtremeTech/dp/0764558943/ref=sr_1_1?s=books&ie=UTF8&qid=undefined&sr=1-1&keywords=wifi+toys).


There's information on making antennas for wifi, using solar power to power up wifi points etc. Worth a look if any one is serious.

u/gravitized · 1 pointr/HowToHack

I just ordered Practical Packet Analysis in order to become proficient with wireshark, I was wondering what basic (laymen) material you would recommend I read in order to understand different forms of attacks such as injecting cookies.

So much of the material easily available is very dry, and boring. (I do not find the material boring, it's more of a presentation bias[?])

u/jonconley · 1 pointr/sysadmin

TIL ZenOSS was a nicely packaged Cacti/Nagios. I've always gone with Nagios/Cacti combos I set up myself... before Zabbix. Still nice to know going forward. Thanks!

I also was given this book: Nagios: System and Network Monitoring and while we didn't go the Nagios route, it was very beneficial too.

u/kardos · 1 pointr/shittyaskscience
u/FeepingCreature · 1 pointr/programming

If you already have a basic idea of how the machine works, I really have to recommend D as a powerful and, above all, sensible high-level language that isn't bound to a single platform the way C# is. You can do (almost) everything you can in C++, and more (the almost is multiple inheritance and binding to C++ libraries, but there are ways around both). If you're curious, check out Andrei's book or ask for more info in our IRC channel (irc://irc.freenode.net/#d).

u/captain_chao · 1 pointr/openbsd

I would recommend The Book of PF: 3rd Edition. Also, even though this page isnt updated any longer it is helpful: http://www.bsdnow.tv/tutorials/openbsd-router

Here is my /etc/pf.conf file with some minor alterations:


ext_if="bge0"
int_if="bge1"
dmz_if="bge2"
int_net="10.10.199.0/24"
dmz_net="172.30.67.0/24"
broken="224.0.0.22 127.0.0.0/8 192.168.0.0/16 172.16.0.0/12 \
10.0.0.0/8 169.254.0.0/16 192.0.2.0/24 \
198.51.100.0/24, 203.0.113.0/24, \
169.254.0.0/16 0.0.0.0/8 240.0.0.0/4 255.255.255.255/32"
set optimization aggressive
set block-policy return
set skip on { lo }
queue main on $ext_if bandwidth 10M
queue defq parent main bandwidth 2500K default
queue web parent main bandwidth 7100K
queue icmp parent main bandwidth 400K
antispoof for { $ext_if, $int_if, $dmz_if }
match in all scrub (no-df random-id max-mss 1440)
match out on $ext_if set prio (5, 6)
match out on $ext_if proto tcp to port { www, https } \
set queue web
match out on $ext_if proto icmp queue icmp
match out on $ext_if from !($ext_if:network) to any nat-to ($ext_if:0)
block in log on $ext_if
pass out
block in quick on $ext_if from { $broken no-route urpf-failed } to any
block out quick on $ext_if from any to { no-route $broken }
pass on { $int_if, $dmz_if }
pass in quick on { $int_if, $dmz_if } inet proto tcp to port ftp \
divert-to 127.0.0.1 port 8021
block proto tcp from any to any port 1688
block log from $dmz_net to $int_net

u/honcas · 1 pointr/AskNetsec

I really like the book Practical Packet Analysis

But just to get you started, try capturing traffic and then going to a website (non-ssl) like reddit.com. After loading the first page, stop the capture and take a look at it. You can search for strings you would expect in the capture, like "reddit.com" or "GET". You can start looking at the payload portion of the packets and go up to see all the layers.

u/buriedfire · 1 pointr/AskNetsec

I think the most highly recommended book on it is Snort 2.0 -

http://www.amazon.com/Snort-Intrusion-Detection-Brian-Caswell/dp/1931836744

and of course the manual on Snort's website. Realistically, it's a sizeable sector of the netsec industry, basically half of the job of a netsec analyst outside regular corporate office tasks - checking the alerts of the ids sensor for false positives and tuning the rules to better fit the environment, and then investigating the alerts that aren't false positives.

u/chasingpackets · 1 pointr/Cisco

Here's a good crash course https://www.amazon.com/dp/B00Y8292MI

u/TheAntiRudin · -8 pointsr/programming

Oh yeah, like this book totally brought me back to GW-BASIC (from Perl)!