Managed switch not distributing other VLAN addresses
-
-
@mannenor said in Managed switch not distributing other VLAN addresses:
I'm not getting your point right here tbh..
Do you own 192.95.1 space? That is owned by the University.. You should not be using public space on your internal networks... Use valid rfc1918 space 192.168/16, 10/8, 17.16/12 - there is ZERO reason to just pull some public IP range out of thin air and think its valid to use on your local networks.
So unless your actually at this university, and their IT told you to yeah put all that /24 behind your pfsense install you should be using it!!
See my edit for for how to do vlan 45 and vlan 46 for your testing.
-
@mannenor said in Managed switch not distributing other VLAN addresses:
@johnpoz I'm not getting your point right here tbh..
His point is you're using public IP's on your LAN.
Lets say Google's IP was 192.95.1.6.
When you try to go to Google from your LAN, what's gonna happen??
In case you don't know, You will never leave your LAN. Meaning you will never get to Google. Why would a packet destined for your LAN addres ever go to the internet?@Jarhead So I should remove the VLAN of the OPT port I guess? And how can I set the OPT port to a trunk port in that case?
As I said, just don't assign an address to it.
Then add the 2 vlans to that interface. -
@johnpoz Man tbh, you are really toxic and from a non experienced person you can't expect them to know everything. I'm not getting it to work with feedback because you literally are in full rage mode. Nice staff from a company selling products and handling customers like that
"An intelligent man is sometimes forced to be drunk to spend time with his fools"
Take another one bud! -
@mannenor said in Managed switch not distributing other VLAN addresses:
literally are in full rage mode
What?? What do think I am raging about - pointing out that your using public space on an internal network?
And I am not staff - just a fan, fellow user helping users with my personal time..
Clearly you do not understand the quote, have you read much Hemingway?
-
@johnpoz Here's one of the screenshots from your previously edited posts, you are toxic man don't try to avoid it because it's the truth. I understand the quote better than you don't worry about that my friend :)
-
-
@mannenor said in Managed switch not distributing other VLAN addresses:
@johnpoz Here's one of the screenshots from your previously edited posts, you are toxic man don't try to avoid it because it's the truth. I understand the quote better than you don't worry about that my friend :)
In John's defense you did start this thread with:
"I am trying to make my switch "TL-SG108E" route my pfsense vlans. For some reason they keep going on my main OPT1 VLAN.I have attached screenshots of how I set up my VLANs and other settings. I probably am almost there but I can't figure the rest out sadly.."
And now that you see the truth, were you realy "almost there"??
Not even close and you are not following the instructions given to you so, yeah, maybe there's some frustration here. -
@mannenor said in Managed switch not distributing other VLAN addresses:
I understand the quote better than you don't worry about that my friend :)
No I don't think you do to be honest.. I get it your frustrated trying to get your setup to work. But I was in no way raging about anything, nor do I really care if your system works or not to be bluntly honest.
The OP is rarely the person that gets the most help - its the other users reading the threads and learning from others mistakes, etc.
Pointing out issues in setups, helps everyone.. So yeah I call out stuff like using public space internally all the time.. Because its BAD IDEA to do that. And honestly would like to know where you got the idea to use 192.95.1? Did someone tell you it was ok to use that space? There had to be some thought process behind using that specific space - was there not?
Does my other sig quote meet with your approval? Or am I also raging against something with that one as well?
-
