Project 1 : PFSense Routing
-
@WrCombs said in Project 1 : PFSense Routing:
get more confused and end up re watching the same videos over and over and still am confused.
This is tough to work with. Without knowing why you are getting more confused or what you are confused about. I mean we can tell that "what a switch is" is confusing. But what we can't tell is... why. Is it because the video is wrong? Or worded poorly?
What video are you using, for example. Is it something that we can review?
-
I also find that describing processes and addressing helps a lot. Imagine yourself as the packet flowing through the network and what info you have, what info you need, and how would you get it?
-
@scottalanmiller said in Project 1 : PFSense Routing:
@WrCombs said in Project 1 : PFSense Routing:
get more confused and end up re watching the same videos over and over and still am confused.
This is tough to work with. Without knowing why you are getting more confused or what you are confused about. I mean we can tell that "what a switch is" is confusing. But what we can't tell is... why. Is it because the video is wrong? Or worded poorly?
What video are you using, for example. Is it something that we can review?
I'm using the Professor Messer Videos Series.
-
@WrCombs said in Project 1 : PFSense Routing:
@scottalanmiller said in Project 1 : PFSense Routing:
@WrCombs said in Project 1 : PFSense Routing:
get more confused and end up re watching the same videos over and over and still am confused.
This is tough to work with. Without knowing why you are getting more confused or what you are confused about. I mean we can tell that "what a switch is" is confusing. But what we can't tell is... why. Is it because the video is wrong? Or worded poorly?
What video are you using, for example. Is it something that we can review?
I'm using the Professor Messer Videos Series.
network+ ?
-
@scottalanmiller said in Project 1 : PFSense Routing:
@WrCombs said in Project 1 : PFSense Routing:
@scottalanmiller said in Project 1 : PFSense Routing:
@WrCombs said in Project 1 : PFSense Routing:
get more confused and end up re watching the same videos over and over and still am confused.
This is tough to work with. Without knowing why you are getting more confused or what you are confused about. I mean we can tell that "what a switch is" is confusing. But what we can't tell is... why. Is it because the video is wrong? Or worded poorly?
What video are you using, for example. Is it something that we can review?
I'm using the Professor Messer Videos Series.
network+ ?
correct.
-
@WrCombs said in Project 1 : PFSense Routing:
@scottalanmiller said in Project 1 : PFSense Routing:
@WrCombs said in Project 1 : PFSense Routing:
@scottalanmiller said in Project 1 : PFSense Routing:
@WrCombs said in Project 1 : PFSense Routing:
get more confused and end up re watching the same videos over and over and still am confused.
This is tough to work with. Without knowing why you are getting more confused or what you are confused about. I mean we can tell that "what a switch is" is confusing. But what we can't tell is... why. Is it because the video is wrong? Or worded poorly?
What video are you using, for example. Is it something that we can review?
I'm using the Professor Messer Videos Series.
network+ ?
correct.
Watching the first video now.
-
I don't know if this would be useful to you, but I did most of my networking on Windows NT 4, Windows 98 and Linux. NT4 was way, way more "raw" than Windows 10 is, and Linux was the same as Linux today, essentially. I think attempting to learn networking using Windows of any sort made since the mid-1990s will sabotage any attempt to learn, as would using a Mac. They are full of abstractions and automations that make learning all but impossible because no one is certain what is happening under the hood.
This is where taking some old "throw away" devices, or getting some dirt cheap older Raspberry Pis (even v 1 or 2) can help a lot, easily. Use Linux, do all command line, keep it as simple and obvious as possible. Then you can really see what is happening rather than getting a modified view of what someone wanted to show you.
-
@WrCombs said in Project 1 : PFSense Routing:
@jmoore said in Project 1 : PFSense Routing:
@WrCombs As for learning routing basics, Scott is right here and this is stuff you rarely do. I have never done this at a business. I only did a little when studying for my network+ in an online lab. I have never had to do anything similar since. Its learning to troubleshoot the network to tell if your having a routing issue, switch issue, or user. 95% its the user lol. So yes good to learn but i would get the basics down real well first, as basic issues will be by far what you troubleshoot the most.
how do you guys suggest I learn the basics ?
Videos aren't helping, reading isn't helping.. I'm kind of out of ideas.
Its books for me too. Think I also used a website because the books are generally pretty lite. Let me see if I can find it.
-
So far, found this one to be good and clear...
https://mangolassi.it/topic/19635/network-switching-overview-comptia-network-n10-007-prof-messer
It's rather a good explanation of what a switch does.
-
So let's talk about that video. Just this one, focused on switching. It's very technical, but it does a good job IMHO of explaining the role of a switch and how it works.
-
@WrCombs I would learn by using Linux. The reason why is that Windows hides a lot of processes in the background. They get abstracted away. You wont understand them if you don't see them and have to interact with them. If you learn it the Linux way, Windows becomes mostly trivial.
-
@jmoore said in Project 1 : PFSense Routing:
@WrCombs I would learn by using Linux. The reason why is that Windows hides a lot of processes in the background. They get abstracted away. You wont understand them if you don't see them and have to interact with them. If you learn it the Linux way, Windows becomes mostly trivial.
only way i would be able to do that at this point would be a linux VM..
which flavor should I choose? -
@WrCombs Here i found them.
https://www.tutorialspoint.com/data_communication_computer_network/index.htm
and
https://www.computernetworkingnotes.com/networking-tutorials/Do some hands on stuff like Scott mentioned and read these and you should have a decent grasp of things.
-
@WrCombs said in Project 1 : PFSense Routing:
@jmoore said in Project 1 : PFSense Routing:
@WrCombs I would learn by using Linux. The reason why is that Windows hides a lot of processes in the background. They get abstracted away. You wont understand them if you don't see them and have to interact with them. If you learn it the Linux way, Windows becomes mostly trivial.
only way i would be able to do that at this point would be a linux VM..
which flavor should I choose?It doesn't really matter and a vm is just fine. Whatever distro you are comfortable with. Fedora, Ubuntu, Mint, Opensuse.
-
@jmoore said in Project 1 : PFSense Routing:
@WrCombs said in Project 1 : PFSense Routing:
@jmoore said in Project 1 : PFSense Routing:
@WrCombs I would learn by using Linux. The reason why is that Windows hides a lot of processes in the background. They get abstracted away. You wont understand them if you don't see them and have to interact with them. If you learn it the Linux way, Windows becomes mostly trivial.
only way i would be able to do that at this point would be a linux VM..
which flavor should I choose?It doesn't really matter and a vm is just fine. Whatever distro you are comfortable with. Fedora, Ubuntu, Mint, Opensuse.
VMs will do the trick, but I have a feeling that the abstraction will make it so much harder. So many more moving parts, and so much harder when you can't put your hands on something. Physically having computers goes a long way. We were buying old computers for $20 back in the mid-1990s. They have to be all but free today.
-
@scottalanmiller said in Project 1 : PFSense Routing:
but I have a feeling that the abstraction will make it so much harder.
Make a tutorial on how to setup a private network in virtual box and then how to make that the only network on the VM's. That equates to the same thing.
-
@JaredBusch said in Project 1 : PFSense Routing:
@scottalanmiller said in Project 1 : PFSense Routing:
but I have a feeling that the abstraction will make it so much harder.
Make a tutorial on how to setup a private network in virtual box and then how to make that the only network on the VM's. That equates to the same thing.
From a purely "how human brains think", I don't think that it does. There is something really educational about touching wires and seeing where electrons have the opportunity to go that really helps you to understand flows.
-
I think lab exercises to learn something are pointless to a large degree.
I think it is better to make use of technology and by installing, setting up and using things, you will encounter problems that forces you to learn more about the subject and what you need in order to get the job done.
You will learn more that way and what you learn will have real world applications. But perhaps more importantly, you will be motivated to learn and get immediate gratification of having accomplished something meaningful when you succeed.
-
@WrCombs said in Project 1 : PFSense Routing:
@Pete-S said in Project 1 : PFSense Routing:
@scottalanmiller said in Project 1 : PFSense Routing:
@Pete-S said in Project 1 : PFSense Routing:
I have no idea what you want @WrCombs to accomplish. You should probably draw the network diagram.
I want there to need to be a non-default route
OK, one scenario I can think of is this:
You have an Edgerouter on your LAN, 192.168.1.0/24, that gives you internet access.
Now you want to add your server fleet (VM host) to the LAN and protect them behind a pfSense firewall/router.All your servers are located on the server LAN, 10.100.1.0/24.
-
How can you let the W10 client have access to the server LAN, for instance 10.100.1.2, by changing the Edgerouter config?
-
How can you access the server LAN from your W10 client directly (without sending that traffic over the Edgerouter)?
-
Wouldn't updating the Edgerouter Routing Table control that?
if not then I have No idea, This is a static routing environment so, My guess would be to change the routing table to show the next hop to 10.100.1.2 is to go through 192.168.1.123. -
Assuming the switch is a dumb switch and is not programmed, I have no idea. How would you ?
The whole reason behind doing this is to understand it, and the more I do it the more and more I get confused, for what ever reason I can't learn networking outside of the basics.
-
Yes, updating the routing table on the Edgerouter will accomplish that. But you would do it with the entire server subnet. So 10.100.1.0/24 would be routed to 192.168.1.123. So that means when a device what's to access some IP address in the 10.100.1.0/24 network it will send that traffic to 192.168.1.123.
-
You would route traffic directly from the W10 client to the pfSense router by changing the routing table on the W10 client. Do a
route printon the windows machine and you'll see what routes it have. The routing table is basically instructions on how to reach IPs that are outside the W10's own subnet. That's why you will find something like this:
IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.33 266That's the default route. And it points to the Edgerouter.
To tell the machine it needs traffic that belongs to the pfSense router (and not everything to the Edgerouter) you would add routes on the windows machine by running
route add.There are some other tricks that can be done to accomplish this in other ways as well. For instance it's possible to automatically push static routes to the W10 machine from the Edgerouter if you are using DHCP. So when the W10 machine gets it's IP and other network info as it is booting, it also get the static route to the pfSense router.
-
-
@Pete-S said in Project 1 : PFSense Routing:
I think lab exercises to learn something are pointless to a large degree.
I think it is better to make use of technology and by installing, setting up and using things, you will encounter problems that forces you to learn more about the subject and what you need in order to get the job done.
You will learn more that way and what you learn will have real world applications. But perhaps more importantly, you will be motivated to learn and get immediate gratification of having accomplished something meaningful when you succeed.
This is SO true. It's why I like building out your home as if it were a business. Something you use and rely on daily. Something other people (presumably) depend on, too.
Some things, like routing, will be much harder that way. But really, if you never learn static routing, you might never be affected by not knowing it.
