@ninthwave

One very important thing, don't let them run as Admin!!! Most people get a Windows computer and run as Admin, which leaves the computer wide open for malware. Run as a user and only use the Admin account when necessary. This is the way things are normally done in the Linux/Unix world.

So it was a routing issue after all.

I checked the actual routing table on the pfSense (should have done this before) and there was a route for that range 192.168.3.128/26 via one of the OpenVPN servers.

Sorry if I wasted anyone's time.

Thanks I thought as much, I will give it a go.

@viragomann thanks, I didn't see this checkbox! 😳

Nevermind. It was traffic shaper mucking me up.

@cdarsac i guess you should start by learning about vlans in general.
I don't have any links to any good tutorials / courses that go down to the basics of vlans

I don’t have enough privileges to suppress this discussion.
Can you do it for me?

@faktorqm said in Question about VLANs and interfaces:

increase the port count in 2 xD it will cost me around 15€ second hand

There you go - much better plan than trying to do some nonsense bridge thing in software ;)

Your 1 cable that caries both vlans run it into a switch first.. Here is thread with really the same question..

Here I did a drawing here how to run it through switch first..
https://forum.netgate.com/post/1000430

I I believe me removing all layer 3 interfaces from the cisco switch might have done the trick. I can ping the interfaces from the server IP's.

Thank you again for letting me bounce things off of you. Extremely important to have other eye look at your work. Thanks again!

@chrisjenk

Yes, the whole point of VLANs is to have multiple virtual networks share a single physical network. In my case, I use it to carry guest WiFi to pfsense. In offices, the computers might share the cable and switch port with VoIP phones, etc..

@m200
Hello,

I’m afraid I’m in the same situation, because the VLAN interface does not respond to the ping of my PC (Windows 10).

I used the "Realtek Ethernet diagnostic utility", but the utility doesn’t show me anything at all...
54540434-5363-4c5a-ac0d-c690ef5e3300-image.png

@grimmsh0t

Nice to hear it works.

Unless you only tested DHCP on Lan interface

It has to be the AgentID tickbox that worked.
As you already had : allow ip any any on Vlan30

/Bingo

Ps: Did you notice the 👍 "Thank you" button in the bottom of each post

You can run lan on a tag if you want.. But yeah during first install its just native.. During install it asks you right up front if you need any vlans set or not.

https://docs.netgate.com/pfsense/en/latest/install/assign-interfaces.html

setup.jpg

@farmerb3d said in Does LAGG + Trunk add any overhead?:

LACP works it would simply use the next best link.

nope doesn't work that way ;) hehehe

@biggsy Perfect, thats what I needed! Thank you!

@marvosa Well I forgot to mention that my Pfsense is virtualized in Proxmox, but I use a dedicated two port Intel gigabit NIC for WAN and LAN. This problem appeared when I upgraded my whole network to gigabit. The WAN interface just drops for parts of the second and the connectivity just comes and goes during the file transfer. I tried today to tweek QoS on the switch and actualy managed to fix the problem for now, but the transfer speeds dropped significantly.