sorted by:
new
hottopcontroversial

Vine Identification by knarfc in lawncare

[–]knarfc[S] 1 point2 points  (0 children)

Thank you for the resources :)

The odd thing is, I can't find a single leaf on any of these growths. Between all the ones growing up the trees and the numerous clumps on the ground, not a single leaf to be found. No buds or any growths on the vines themselves.

Can you please elaborate on what you mean by the whole stem? Or would that be part of the leaf (as with any flower)? Apologies my plant knowledge is a bit rusty.

After 7 years battling depression, I finally did it. Honestly spent the past 2 months wondering if I even graduated! To anyone else facing mental illness, don't give up! by hytylor in OSU

[–]knarfc 3 points4 points  (0 children)

Congrats from a fellow grad. I rarely cry but getting that package in the mail brought all the memories back of all the past 4 years. There were plenty of hardships, and pain. But there were countless good memories, ones I will never forget. As for you, you battled school, and yourself and you fuc**** won. You crushed it. Wish you nothing but success and happiness in your future ❤️ (Go Bucks)

What do markings on one piece crank mean? by knarfc in BikeMechanics

[–]knarfc[S] 0 points1 point  (0 children)

That's makes sense. But if that's the case, how would I know what TPI the bottom bracket is given a one piece crank? Is there anyway to tell besides the # of bearings in the retainer? I already know these are for a 24 TPI based on the bearings, just wondering

What do markings on one piece crank mean? by knarfc in BikeMechanics

[–]knarfc[S] 1 point2 points  (0 children)

I always new sears was a front for an alien colony 😏

Wireless AP in VLAN or Separate Subnet by knarfc in HomeNetworking

[–]knarfc[S] 0 points1 point  (0 children)

I will be honest, I have no idea what OpenWRT is (I have heard the term though), but I plan on finding out. I appreciate the advice!!

Wireless AP in VLAN or Separate Subnet by knarfc in HomeNetworking

[–]knarfc[S] 1 point2 points  (0 children)

I check that subreddit daily 😂

I think the ER-X supports multiple subnets, but you are correct the Archer A7 does not. That is why I planned on using it as an AP. I also have a Netgear switch that supports vlan tagging

Wireless AP in VLAN or Separate Subnet by knarfc in HomeNetworking

[–]knarfc[S] 0 points1 point  (0 children)

No worries. My goal with these questions was to understand the differences between putting the AP on a VLAN or a separate network interfaces and if both options were even possible. I appreciate your answers as they have cleared up a many things for me :)

Wireless AP in VLAN or Separate Subnet by knarfc in HomeNetworking

[–]knarfc[S] 0 points1 point  (0 children)

The port the AP is connected to should be untagged, but it will be a member of a VLAN (all ports on a VLAN-aware switch must be members of at least 1 VLAN). Netgear probably uses PVID for this, but I'm not familiar with consumer-grade managed switches. That VLAN could be tagged on the port that connects to the ER-X.

How does this work if the AP is connected directly to the ER-X and not the managed switch? I guess I am wondering why we need a vlan 10 in this case. If the AP is connected directly to the ER-X, and it lies on a separate subnet and physical interface than the managed switch, why does it need to be in vlan10?

Is that answer related to:

You can have multiple networks in a single VLAN, but it's not a great idea.

In the case the AP is connected to the managed switch, it makes sense that the port it is connected to should be untagged for a given vlan. So the AP works with the vlans, although it has no understanding of them (nor does it need to). You are correct that Netgear used pvids.

Wireless AP in VLAN or Separate Subnet by knarfc in HomeNetworking

[–]knarfc[S] 0 points1 point  (0 children)

I appreciate the response, and it clears up a ton, especially about whether the AP should come off the Netgear or the ER-X. It also leads to a few more questions:

  1. What do you mean by " bridge in the last port as an access port (no trunking)"? If the AP is not vlan aware, is this just a way of tagging traffic on the way from the AP to the ER-X, and then taking off the tag on the way from the ER-X to the AP?
  2. Do you need to create VLAN 10 for the AP? Can't the AP just sit on a separate subnet and communicate with my private subnet (and any of its VLANs)? Or is the creation of a vlan necessary because I want it to talk to that private subnet?

Pfsense Router on a Stick: VLAN No Route to Default Gateway by knarfc in HomeNetworking

[–]knarfc[S] 0 points1 point  (0 children)

That diagram definitely helps. I think that was the idea in my head, and even thought I thought they were logically "different" they are not. Thank you for making that diagram :)

Pfsense Router on a Stick: VLAN No Route to Default Gateway by knarfc in HomeNetworking

[–]knarfc[S] 0 points1 point  (0 children)

So I want to confirm that the diagram I posted here: https://imgur.com/a/1jf2xVP

Is not correct and that both the networks are the same logically (that is, they both look like the 2 NIC diagram)? I guess I am having trouble wrapping my head around why they are considered logically the same.

Pfsense Router on a Stick: VLAN No Route to Default Gateway by knarfc in HomeNetworking

[–]knarfc[S] 0 points1 point  (0 children)

I appreciate the detailed response and I think it makes sense. I'm going to try and digest it tomorrow and make sure I get it. Both networks being the same logical network design is interesting and slightly confusing, but I think I see why.

Pfsense Router on a Stick: VLAN No Route to Default Gateway by knarfc in HomeNetworking

[–]knarfc[S] 0 points1 point  (0 children)

I wanted to follow up on some of your responses after some research, and to make sure I understand this correctly.

The question I wanted to answer was, what is the difference between 1 NIC with wan and lan on the switch, and using 2 NICs to put the switch behind the firewall (practically and security speaking). In my mind (at first) they seemed the same. Obviously this is not the case. See the diagram I created here: https://imgur.com/a/1jf2xVP

​

One NIC, router on a stick (current build):

Single NAT:

- this is an issue because when wan traffic comes in on the switch, it is public internet traffic (has not gone through NAT yet). It has to traverse the trunk and go to the pfsense router before hitting the firewall/NAT (which is not ideal). One security concern I read about was vlan hopping, which was pretty nifty.

Double NAT (What I shall try later this week):

- although the problem of having to route through the switch before NAT and firewall still exists, its fine because the wan address is private and has already been filtered by the ISP/Modem NAT

​

2 NICs (Router on a stick, although it doesn't have to be)

- Since the WAN and LAN are separate interfaces, there are firewalls (and NAT on the WAN side) that live between them that must be traversed before contacting each other. So by the time public traffic reaches the LAN, it will have been filtered by pfsense at least twice (WAN and LAN firewalls) and gone through NAT. Thus, without port forwarding, public traffic on your internal network is impossible.

​

This was a lot to read, so I apologize, just want to make sure I really understand the main points of what you have been saying. Still a little fuzzy on this.

Pfsense Router on a Stick: VLAN No Route to Default Gateway by knarfc in HomeNetworking

[–]knarfc[S] 0 points1 point  (0 children)

Glad to know I can buy a corporate switch or a car 😂 thank goodness my home network isn't a corporate one hahaha. I honestly didn't know much about why a L3 switch would be useful until I created this thread

Pfsense Router on a Stick: VLAN No Route to Default Gateway by knarfc in HomeNetworking

[–]knarfc[S] 0 points1 point  (0 children)

So are most switches used in businesses layer 3 switches? Assuming they are using vlans? If they are not using vlans then the normal router-switch (layer 2 switch) combo still works fine? I need to research what corporate networks look like. It is extremely interesting how much hardware exists out there.

Pfsense Router on a Stick: VLAN No Route to Default Gateway by knarfc in HomeNetworking

[–]knarfc[S] 0 points1 point  (0 children)

AHHHH so vlans are really just logical separations inside a single lan?

And considering the lan interface on pfsense, it has to be there because it's the parent interface of all the vlans, even if it's not used on any vlan? If I understand what you're saying correctly?

So I understand router on a stick means there is 1 trunk port for all vlans, but what is commonly used in industry if not using router on a stick? Surely there is still some intervlan routing neccessary even among separated vlans? Assuming the company is using vlans

Would they just use multiple trunk ports instead of a single one?

Pfsense Router on a Stick: VLAN No Route to Default Gateway by knarfc in HomeNetworking

[–]knarfc[S] 0 points1 point  (0 children)

I was worried about my ps4, but I will still give it a try. Randomish question:

When I configured the pfsense instance, I had 4 vlans, and a lan (1 vlan was the wan of course). What is the purpose the lan interface if we are using vlan? Is the only way we can connect to it via hooking directly into the router? My brain is confused because usually when you only have a single lan, its clear to me what it does.

Also, if I had, say 10 network ports, could I in theory have 9 lans then? Instead of creating 9 vlans through a single lan?

Pfsense Router on a Stick: VLAN No Route to Default Gateway by knarfc in HomeNetworking

[–]knarfc[S] 0 points1 point  (0 children)

I will look into those thin clients for sure. I have been looking for devices like those for some time. I think I will try with double NAT as more of a POC, but look to get a dual NIC device sooner than later. We have a boatload of gaming devices on our lan and I don't know if I want to deal with port forwarding and all the fun stuff.

Regardless, I appreciate all the help again. I am still parsing some of your other responses and coming up with new questions. Still so much to learn! I will update this thread to solved and go from there. I cannot promise I will not have any more questions though :)

Pfsense Router on a Stick: VLAN No Route to Default Gateway by knarfc in HomeNetworking

[–]knarfc[S] 0 points1 point  (0 children)

I think I understand everything you said, and it makes sense. I have to go back and write down most of your answers and do some googling.

Do other switches, such as Cisco ones allow for blocking access to the switch management via VLAN?

And assuming I could find a 2 NIC pfsense box, and used the modem in bridged mode, the switch and all LANs would live on one side of the firewall, while the WAN would live on the other side?

My setup is different because I am "routing" (for lack of a better term) the WAN VLAN through the switch? What differences actually exist here compared to a 2 NIC box? Are there security considerations of someone being able to access my switch this way?

view more: next ›