cyberstudent with basic questions about interface configurations
-
And to be clear that requires a ppp server at the pfSense end which is not configured.
To use the serial console in pfSense you need to use a actual serial connection and then use a serial terminal program in the host to connect across it.
So for most users that means using a USB serial adapter of some sort since not too many people have a laptop with a real serial port these days!
Some appliances, like the ones we sell, have a USB serial console where the USB/serial interface is on-board. That means you can connect to it with a standard USB cable.
Steve
-
oh ok good to know...
1.)only as a last resort totally makes sense for the serial cable question.2.)as for the setup on for the LAN's
cable Modem provides public ip address to pfsense on WAN
LAN interface in set to 192.168.40.15/24
OPT1 interface is set to 192.168.50.20/32
LAN goes into a switch for 3 workstations receiving addresses from pfsense 192.168.40.20, 192.168.40.21, 192.168.40.22Now i know OPT1 192.168.50.20/32 is a sub-net cause of the /32 right?
if i just use a another regular switch on OPT1 Sub-net by default is the OPT1 sub-net a separate isolated network?
The goal is to have two isolated networks that cannot communicate with each other and am confused on the difference between subnetting and VLANS other than VLANS happen at the switch (layer 2) level.i learned VLANS accomplish segmenting networks... just confused if having a separate subnet (like the /32 sub-net), does it also isolate the networks. I have read a ton on it but cannot grasp the difference just yet in terms a 5 year old can understand.
3.) okay so i can afford the appliance just yet ;(
If number 2 is still confusing ill post up pictures of the configuration for you guys. And thanks for the help on the basics...
My firewall class starts in 2 weeks for the summer semester but im taking the COMPTIA NETWORK+ again, (almost passed first time out) next week and want all the info i can get now..
-
@cyberstudentnewbie said in cyberstudent with basic questions about interface configurations:
just confused if having a separate subnet (like the /32 sub-net)
/32 isn't really a subnet, /32 is 1 IP address.
Lets say you have
192.168.0.0/25 = 192.168.0.0 - 192.168.0.127
and
192.168.0.128/25 = 192.168.0.128 - 192.168.0.255
Those would be different networks, but doesn't mean they are isolated at layer 2.. Which is what you would use vlans for, to actually isolate the 2 networks on different layer 2 networks.
The mask just tells you what IPs are in the layer 3 network. Setting an interface to anything/32 would not really be viable for an interface that wants to talk to anything, because that really isn't network, its a specific single IP.. Those would only really be valuable as a loopback address. Or a firewall rule, not really as mask for an IP that is on an interface that wants to talk to something else.
-
@cyberstudentnewbie said in cyberstudent with basic questions about interface configurations:
OPT1 interface is set to 192.168.50.20/32
A /32 isn't possible.
As that would mean that that IP "192.168.50.20" is the only IP usable on that "OPT1" network.Sneak peak how LAN is set up : 192.168.1.1/24 - you see that 24 ? That means IP 1 to 254 are usable.
256 is 2^8 or /24Also, with a /32 you can't activate the DHCP server on OPT1, as there is only 1 IP in that "192.168.50.20" network .... and you've already used it.
So when you connect a device to that OPT NIC : it wont reply on any DHCP request. As it has none to offer .... (and the DHCP isn't working anyway on that interface ...)And, please : don't do that : "192.168.50.20".
Use "192.168.50.1" of the pfSEnse OPT1 IP, or "192.168.50.254" if you have to.
For every other IP, be ready to receive the ......"don't do that - many have tried - they all ...."
Well, we never saw them again.No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
@Gertjan said in cyberstudent with basic questions about interface configurations:
Use "192.168.50.1" of the pfSEnse OPT1 IP, or "192.168.50.254" if you have to.
While I agree with you from a common practice point of view, using the first or last IP in a network is common practice as the gateway IP. But there is nothing saying you have to do that. I use for example .253 for all my pfsense IPs.
Mostly because devices tend to default to .1 or .254 as their IP when setting up.. And if I connected a new device to any of my networks I didn't want them by accident stepping on my routers IP. I don't run any common networks 192.168.0 or 192.168.1 or 10.0.0 for example - but not using .1 or .254 is habit from when used those common networks.
But agree, someone new to networking, common to use the .1 or the .254 as your routers IP in the network when using /24 networks.
-
@Gertjan said in cyberstudent with basic questions about interface configurations:
Sneak peak how LAN is set up : 192.168.1.1/24 - you see that 24 ? That means IP 1 to 254 are usable.
256 is 2^8 or /24Yes the /24 means 24bits out of the 32bit address are fixed. Leaving 8 bits that can be defined for addresses in the subnet. And, yes 2^8 means 256 addresses.
But here you can't use 0, that's the network address, and you can't use 255, that's the broadcast address. -
/24 is the cider version over using the 255 octets for your subnet mask 192.168.1.1 255.255.255.0 or just 192.168.1.1/24
You have your host address your network, and a broadcast address. this occurs on the private ip class. You have different class addresses also like class a, b, c, for the private addresses. check out subnet calculator. I had to do all this stuff by hand when it was taught at the College. You have to learn how to subnet by hand but the calculator can help you get a start on it.
Make sure to upvote
-
@JonathanLee said in cyberstudent with basic questions about interface configurations:
You have different class addresses also like class a, b, c
This hasn't been used in 30 years.. Why they still come up is beyond me.. I learned class because well cidr wasn't even a thing yet when I got into networking. But why it still comes up is just nuts..
An intelligent man is sometimes forced to be drunk to spend time with his fools
If you get confused: Listen to the Music Play
Please don't Chat/PM me for help, unless mod related
SG-4860 24.11 | Lab VMs 2.7.2, 24.11 -
Good to know it existed. At some point you're bound to find some ancient documentation referring to it.
-
@JonathanLee said in cyberstudent with basic questions about interface configurations:
You have different class addresses also like class a, b, c, for the private addresses
Address classes have been obsolete for about 30 years, replaced by CIDR.
-
@stephenw10 said in cyberstudent with basic questions about interface configurations:
Good to know it existed.
And it's also good to know, many years ago, computers were built with vacuum tubes. However, that's totally irrelevant to today's computing. If you want even more "good", we can't forget that before classful addresses, every address was what became known as class A, that is 8 bit network address and 24 bits for the host.
-
We use to use candles and whale oil lamps for light as well ;)
-
@johnpoz well I feel old now… it still feels like cutting edge technology. I mean 10baseT was the hottest thing since sliced bread a couple years ago… token ring… BNC connectors. Don’t forgot HUBs, I mean what’s a switch we rock massive collision domains here haha.
I was servicing a random site’s network equipment a couple years ago and they still had equipment racked in for an ancient IBM network design topology. It was no longer used and unplugged. But it had epic huge lock in plugs. I had never seen it before. Pre dated BNC stuff. Pre Ethernet. It was wicked cool.
The IBM Multistation Access Unit
Make sure to upvote
-
@JonathanLee said in cyberstudent with basic questions about interface configurations:
I mean 10baseT was the hottest thing since sliced bread a couple years ago
It was a bit longer than a couple of years.. But yeah as you get older, 20 years seem like just last week ;)
Doesn't seem like that long ago was installing tcp/ip on the old windows 3.11 machines via a bunch of floppies..
-
What we need is to build a firewall on Xenix it has a tcp stack hahaha, use that new April 4th release of pfSense.
Make sure to upvote
-
@JonathanLee said in cyberstudent with basic questions about interface configurations:
Pre dated BNC stuff. Pre Ethernet. It was wicked cool.
Actually, Ethernet predated token ring. That MAU is used for token ring. I don't think BNC connectors were ever used for it, just Ethernet and ARCNET.
I used to work for IBM Canada in the late 90s and there were racks full of those MAUs. When I was back on contract a few years later, token ring was nowhere to be found and everything was Ethernet.
-
@JKnott it was like they erased history of that network equipment, they don’t talk about MAU at all in any publication for higher education. I wanted to share it as it was an amazing find and rabbit hole to learn what it was for me. I remember token ring in elementary school. But never MAU technology. They had a token ring network for an apple computer lab with bnc cables 10baset stuff all wired in a circle with t connectors it was so cool to see it and work with.
Make sure to upvote
-
A while back, last year already, I found these : How To Start An ISP (like it's 1993)
All the big brands, operating systems, all the equipment, most of them I 'heard' about, but never actually saw it.
All I remember is that I had a Robotics Sporter 56K modem (that actually only synced up to 33.6).
Now you can see what was on the other side.No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
That Mac network might have been AppleTalk. (Do Apple computers have Mac addresses?
)MTU is something that should be discussed, otherwise we'll be stuck with 1500 forever. 16 Mb token ring could go almost 18K bytes. I doubt most people even know why 1500 was picked for Ethernet. Back in those days, networks weren't reliable and collisions were expected. So it became a trade off between efficiency and retransmitting lost frames. It became locked in with early Ethernet NICs that were hardware limited and also when 802.3 was introduced and the Ethertype/Length field was used to determine whether it was an Ethernet II or 802.3 frame.
These days, with switches, collisions are history and networks are both much faster and more reliable, so the 1500 MTU has become a bottleneck. I have a cheap TP-Link switch that can handle 16K frames and 9K are often used in data centres, etc.. It's time to move on.
BTW, my first Ethernet experience was with DECNet over 10base5 "Thicknet" and I'm probably the only one here who has ever hand wired an Ethernet controller.
-
@Gertjan said in cyberstudent with basic questions about interface configurations:
All I remember is that I had a Robotics Sporter 56K modem (that actually only synced up to 33.6).
I have a Courier (collecting dust in my junque closet). It could deliver 56K down, provided the ISP was on a digital phone connection. Up was always 33.6K max.
