Hi Steve, I think we did recently update so that could definitely have been it. Thanks though for all your help!!

@philipputrus said in FTP server behind pfSense...: The server use Active mode I checkd that by connecting to it from the CMD For active mode you need to have the client FTP proxy installed and configured. It will not allow the server to open data channels without it. Steve

No I haven't but I'm thinking of it as updating our infrastructure.

When you run tcpdump on the interface in pfSense you see eveything the driver is sending but that might not necessarily make it onto the wire. By using a switch in between, mirroring the port and capturing on there you see what traffic is actually going back and forth. Steve

Ah in Tautulli interface - thanks.. Yeah that does make it easy to find ;) that scope would all be great if you made them vlans and actually isolated them.. But if they are all on the same L2 kind of just meaning less.. And means you have to for sure hand out reservations for every mac address.

You are only opening one port so you're exposing only the service listening on that port. The RasPi could have everything open but nothing is going to reach it except what you're forwarding. Steve

I set on accept for Promiscuous mode, mac address changes and forget tramits on WAN vswitch, Since my network goes Virtuel WAn switch-pfsense-virtuel LAN switch. Also very important to note that is a reboot of whole esxi is necessary for it to acctually implement the changes made. I didnt discover this at beginning.... so alot of my testing was flawed cause changed wasent acutally being made... Thanks for all help.

Sure... without success :(

Thank you. That fixed my problem.

Traffic between the modem and Asus router there is all inside PPPoE apart from traffic to the modem itself. So that's probably not what you want to do. pfSense would not 'see' most of that traffic. pfSense as the gateway and Asus as an access point is the way to go there. Steve

If you use a shellcmd that gets stored in the config file and hence can be retsored and is never lost at an update etc. If that command calls a custom script that might be lost though. You can use the filer package to store that in the config so it's all restored however. Steve

TNSR is a completely different product than pfSense, and both will be developed concurrently from what the Netgate people have said recently.

Upgrade fixed it! Thanks. Impressive response time. 3 minutes. :)

@akuma1x Hi Jeff, thank you for showing me the way to the discussion about it. Now I know a bit more. James

Could be an MTU issue. Try to ping with large packets, how large will pass? https://docs.netgate.com/pfsense/en/latest/routing/unable-to-access-some-websites.html Steve

If you do need to apply that command at boot you can do so with a shellcmd: https://docs.netgate.com/pfsense/en/latest/development/executing-commands-at-boot-time.html And actually now I think about it if you use the 'afterfilerchnages' type there it will be applied if the WAN goes down and comes back up. That might be all you need there. Steve

Did it work just connected directly behind pfSense then? Steve

Very cool. I have a synology NAS. Thanks!!!

Just to report back, in our situation the upstream Zyxel modem had features to block ping, probably to mitigte DoS: [image: 1551958166952-problemi_monitor-resized.png] Disabling this stuff fixed gateway monitoring

Hello, yes I edited manually by adding that to an <earlyshellcmd> Anyway, now i created a new gateway via WebUI , i checked the box to say that gateway is not part of the wan network, deleted my earlyshellcmd, rebooted and yes now it is working. I was used to put all my initial route and the way to reach the gateway onto the earlyshellcmd as i was not aware of this options, maybe this option is quite new. Anyway before version 2.2 it was working find and never had this problem. but pb is solved now. thanks. Regards