@wrcombs said in Subnetting:

@scottalanmiller said in Subnetting:

@wrcombs said in Subnetting:

but when the questions are "you need 4 networks which subnet mask would you use on this ip: 10.1.1.25"

That's gibberish. There's no way to know based on what is stated.

I probably missed the actual question.. but questions similar to that confuse me.

It's all math and high school style word problems. It's all about "to meet the requirements", what options would you choose so that the sizes are correct.

Example: I have an IPv4 network, and you have an IPv4 network, and we want to talk to each other. But there's no IPv4 network between us. We need to tunnel our networks somehow through whatever is between us so that we can network to each other. That in between network could be anything, NetBEUI, IPX/SPX, IPv6, whatever. As long as we tunnel through it, our IPv4 networks can see each other (but not the network inbetween).

@WrCombs said in Just for Fun - Network + Journey:

@pmoncho said in Just for Fun - Network + Journey:

@WrCombs said in Just for Fun - Network + Journey:

@pmoncho said in Just for Fun - Network + Journey:

@WrCombs said in Just for Fun - Network + Journey:

@scottalanmiller said in Just for Fun - Network + Journey:

What is the best way to secure the most vulnerable attack vector for a network?

Choices:

A] Remove unneeded services running on the servers
B] Provide end-user awareness training for office staff
C] Update all antivirus definitions on workstations and servers
D] Use biometrics and SSO for authentication

Hey First Question - Thanks Scott

My first instinct D]Use biometrics and SSO for Authentication

The key words in the question is "most vulnerable attack vector" so IMHO, D] would incorrect.

Well People would be the most vulnerable

so B?

Correct, B. @scottalanmiller will have to confirm though.

I thought that too, but then I thought that was too easy and that he probably was meaning something else .

The test SHOULD be too easy. If you really know the material, and are paying attention to the reading (because the questions are designed to not let you skim them), it should feel pretty obvious a lot of the time.

@manxam said in Collision Domain - In POS:

@scottalanmiller said in Collision Domain - In POS:

@manxam said in Collision Domain - In POS:

I can't recall ever seeing a switch "back in the day" that didn't have ASICs. There are a few newer switches that do, in fact, use CPU rather than ASICs, but they're built using MUCH faster CPUs than what are included in most -- if not all -- routers.

Early days, the ASICs didn't even exist yet. It wasn't a choice, it was all that there was to use software. Then the ASICs came along and obviously dominated. But yes, it always requires throwing more hardware at it.

How far back are we going here? My first experience with a switch was with Alantec/FORE ATMs (circa early 91/2). These had a RISC SCP processor to run the OS/management functions and custom ASICs for switching. After that, in the more mainstream, came Kalpana and then Cisco. To the best of my knowledge, there were no switches available prior to thicknet (first commercial ethernet).

I'd love more information if you have it available. I love the history of tech.

Not that far back, still 90s, but a lot of switches were all software in the middling to later 90s as the ASICs weren't broadly available.

But even the very, very first ASICs were / are always based on working software prototypes.

I've never seen a thicknet switch, what a freaking mess that must be.

I used to manage a Full Tolerance Infrastructure.

2 Devices of Everything (Routers, Firewalls, Edge Switches, Core Switches, Access Switches, etc)
2 Internet Providers
2 Private Circuits

Network Documentation is very very important, for Network Admins is a must, because for example a new team member joins, this information will be useful to acknowledge the network infrastructure.

I have experienced that T3 (DS3) collapses (saturates) once you reach 40 Mbps, even rate is up to 44 Mbps.