Debug.pfftpproxy=1 to enable LAN to WAN FTP

ggzengel · Jul 4, 2013, 2:14 PM

But you don't see if server really connect from port 1234 to client port 2345 and the router expect this.

jimp · Jul 4, 2013, 2:19 PM

Yes, but as I said, a different problem entirely. They are both helpful but in different ways.

jlzentveld · Jul 5, 2013, 1:50 AM

I also had problems with ftp connections being very hit & miss since upgrading to 2.1. Setting this got it working again.

athurdent · Jul 5, 2013, 8:42 AM

I have setup a new pfSense VM on ESX 5.1 to debug this. I think I know what happened to my unresponisive ALIX test installation, pfSense just freezes after some time while trying to browse the FTP server stated some posts before. There's no error message, the console just freezes…
Any idea?

Edit: After 3 freezes while browsing the FTP my installation now crashed and rebooted. It collected the following attached crash report.

Edit2: I installed a fresh Snapshot from pfSense-LiveCD-2.1-RC0-amd64-20130701-1521.iso. I have tried everything but I was not able to freeze / crash it yet. Maybe the recent change to the FTP helper made pfSense somewhat unstable?

crash.txt

lucky · Jul 6, 2013, 4:04 PM

I started having issues on around the May 9th snapshot. I didn't notice it until this past week because my FTP server isn't used much. Setting debug.pfftpproxy=1 has restored services, for now.

My setup is fairly straightforward - three NICs, one WAN two LAN. The FTP server is in a VM that sits on one of the LAN segments. FTP server is a default Ubuntu wu-ftp daemon install. I have a NAT rule in place for FTP. I have traffic shaping, though FTP is not part of any special queue. That's about it. This has worked solidly until ~ May 9.

Note - When I was initially troubleshooting, I noticed that the firewall was denying SYN ACKs going from the FTP server back to the client. The client failed to properly FTP data to my server in both active and passive mode.

If I can provide anything else to help troubleshoot, please let me know and I'll get it for you.

eri-- · Jul 8, 2013, 12:55 PM

Wait for snapshots of tomorrow and test.

athurdent · Jul 9, 2013, 7:26 AM

FTP did not get any better with the lastest snapshot Mon Jul 8 21:53:11 EDT 2013 . It should contain the newest fixes according to```
cat /etc/version.lastcommit

Half of the time passive FTP works, but I am still seeing those in the logs when the passive FTP session hangs.
em0 is the LAN interface. My test system is single LAN/WAN.

Jul 9 08:51:02 pfsense-ipv6 pf: 00:00:14.413456 rule 4/0(match): block out on em0: (tos 0x0, ttl 53, id 24551, offset 0, flags [DF], proto TCP (6), length 52)
Jul 9 08:51:02 pfsense-ipv6 pf: 83.141.4.210.56941 > 192.168.x.x.56941: Flags [S.], cksum 0xa08a (correct), seq 1305586650, ack 72292906, win 5840, options [mss 1380,nop,nop,sackOK,nop,wscale 7], length 0

So the state table still does not get updated correctly by the FTP proxy/helper.
On the bright side, at least pfSense did not crash, yet.

Edit:
Active FTP does not work anymore, I'm getting those in the log:

Jul 9 09:25:29 pfsense-ipv6 pf: 83.141.4.210.21 > 192.168.x.x.49686: Flags [P.], cksum 0x966e (correct), ack 212331008, win 5840, length 51
Jul 9 09:25:29 pfsense-ipv6 pf: 00:00:00.212976 rule 4/0(match): block out on em0: (tos 0x0, ttl 53, id 9015, offset 0, flags [DF], proto TCP (6), length 91)
Jul 9 09:25:29 pfsense-ipv6 pf: 83.141.4.210.21 > 192.168.x.x.49686: Flags [P.], cksum 0x966e (correct), ack 212331008, win 5840, length 51
Jul 9 09:25:30 pfsense-ipv6 pf: 00:00:00.090747 rule 4/0(match): block out on em0: (tos 0x0, ttl 53, id 52027, offset 0, flags [DF], proto TCP (6), length 52)
Jul 9 09:25:30 pfsense-ipv6 pf: 83.141.4.210.21 > 192.168.x.x.49686: Flags [.], cksum 0x1e4e (correct), ack 212331009, win 5840, options [nop,nop,sack 1 {212330981:212331009}], length 0
Jul 9 09:25:30 pfsense-ipv6 pf: 00:00:00.335257 rule 4/0(match): block out on em0: (tos 0x0, ttl 53, id 23454, offset 0, flags [DF], proto TCP (6), length 91)
Jul 9 09:25:30 pfsense-ipv6 pf: 83.141.4.210.21 > 192.168.x.x.49686: Flags [P.], cksum 0x966d (correct), ack 212331009, win 5840, length 51
Jul 9 09:25:30 pfsense-ipv6 pf: 00:00:00.255013 rule 4/0(match): block out on em0: (tos 0x0, ttl 53, id 41021, offset 0, flags [DF], proto TCP (6), length 52)
Jul 9 09:25:30 pfsense-ipv6 pf: 83.141.4.210.21 > 192.168.x.x.49686: Flags [.], cksum 0x1e4d (correct), ack 212331009, win 5840, options [nop,nop,sack 1 {212330981:212331010}], length 0
Jul 9 09:25:31 pfsense-ipv6 pf: 00:00:00.597293 rule 4/0(match): block out on em0: (tos 0x0, ttl 53, id 24176, offset 0, flags [DF], proto TCP (6), length 91)
Jul 9 09:25:31 pfsense-ipv6 pf: 83.141.4.210.21 > 192.168.x.x.49686: Flags [P.], cksum 0x966d (correct), ack 212331009, win 5840, length 51
Jul 9 09:25:31 pfsense-ipv6 pf: 00:00:00.604381 rule 4/0(match): block out on em0: (tos 0x0, ttl 53, id 26446, offset 0, flags [DF], proto TCP (6), length 52)
Jul 9 09:25:31 pfsense-ipv6 pf: 83.141.4.210.21 > 192.168.x.x.49686: Flags [.], cksum 0x1e4d (correct), ack 212331009, win 5840, options [nop,nop,sack 1 {212330981:212331010}], length 0
Jul 9 09:25:32 pfsense-ipv6 pf: 00:00:01.101145 rule 4/0(match): block out on em0: (tos 0x0, ttl 53, id 11135, offset 0, flags [DF], proto TCP (6), length 91)
Jul 9 09:25:32 pfsense-ipv6 pf: 83.141.4.210.21 > 192.168.x.x.49686: Flags [P.], cksum 0x966d (correct), ack 212331009, win 5840, length 51
Jul 9 09:25:32 pfsense-ipv6 pf: 00:00:00.103532 rule 4/0(match): block out on em0: (tos 0x0, ttl 53, id 42482, offset 0, flags [DF], proto TCP (6), length 52)
Jul 9 09:25:32 pfsense-ipv6 pf: 83.141.4.210.21 > 192.168.x.x.49686: Flags [.], cksum 0x1e4d (correct), ack 212331009, win 5840, options [nop,nop,sack 1 {212330981:212331010}], length 0
Jul 9 09:25:34 pfsense-ipv6 pf: 00:00:01.204942 rule 4/0(match): block out on em0: (tos 0x0, ttl 53, id 64293, offset 0, flags [DF], proto TCP (6), length 52)
Jul 9 09:25:34 pfsense-ipv6 pf: 83.141.4.210.21 > 192.168.x.x.49686: Flags [.], cksum 0x1e4d (correct), ack 212331009, win 5840, options [nop,nop,sack 1 {212330981:212331010}], length 0

lucky · Jul 10, 2013, 2:44 PM

@ermal:

Wait for snapshots of tomorrow and test.

Still having the issue on: 2.1-RC0 (amd64) built on Tue Jul 9 23:33:36 EDT 2013

Update: just to clarify, setting debug.pfftpproxy=1 still makes connections to my FTP server work again.

doktornotor · Jul 10, 2013, 2:20 PM

@lucky:

Still having the issue on: 2.1-RC0 (amd64) built on Tue Jul 9 23:33:36 EDT 2013

I had no issues before the latest patches. Broke more than it fixed.

athurdent · Jul 10, 2013, 2:40 PM

My issues with FTP began after:
https://redmine.pfsense.org/issues/2650#note-9
Would be great if those patches could be reverted. FTP is sluggish/broken on both of my WAN lines now.

gogol · Jul 13, 2013, 8:06 AM

I am on "built on Fri Jul 12 10:55:43 EDT 2013" but I still have problems when the proxy is enabled (default value).

doktornotor · Jul 13, 2013, 8:13 AM

On another note, I still managed to get kernel panic with FTP traffic with

2.1-RC0 (i386) built on Thu Jul 11 23:06:42 EDT 2013 FreeBSD 8.3-RELEASE-p8

The more patches here go in, the more broken the thing is, and I have yet to see anyone reporting any improvement to the issues they were supposed to be fixed. Please, revert the stuff altogether.

datentod · Jul 14, 2013, 7:41 AM

Same issue here on same build.

@doktornotor:

On another note, I still managed to get kernel panic with FTP traffic with
2.1-RC0 (i386) built on Thu Jul 11 23:06:42 EDT 2013 FreeBSD 8.3-RELEASE-p8
The more patches here go in, the more broken the thing is, and I have yet to see anyone reporting any improvement to the issues they were supposed to be fixed. Please, revert the stuff altogether.

doktornotor · Jul 14, 2013, 7:46 AM

@datentod:

Same issue here on same build.

The patches thankfully got reverted.. Try later with today's snapshots, the panics should be all gone.

athurdent · Jul 18, 2013, 7:04 AM

Just updated to the lastest snapshot. Passive FTP is still hanging frequently. It would be really nice if the patches from about 2 month ago could be reverted, too. After those FTP started to behave odd, it was working perfectly fine before.

AeroWB · Jul 18, 2013, 10:12 AM

Same problem here with a simple setup and the snapshot from July 17, the browser ftp test to dd-wrt fails. While pfSense 2.0.3 works.
Hopefully these ftp helper changes get reverted to what worked in 2.0.3

I do not have multi WAN so I am not affected by the problems that the old code had, hopefully for those who do there exists a good workaround.

Maybe a new ftp helper could be tested and developed on a different version then pfSense stable and release candidate as it seems to be quite complicated as the 2.1.0 release candidates have a broken ftp helper for over 2 months.

doktornotor · Jul 18, 2013, 10:17 AM

Devs, could someone make a testing "out-of-band" 2.1 snapshots with the recent (2+ months) FTP "fixes" removed? I suspect those really don't improve much, but rather keep breaking things for more people. This way, those lots of people who posted on this thread could test those and report if they get actual improvement, or whether there are some regressions from reverting the patches, or whether it changes nothing for them.

On a positive note, after several days of downloading and uploading via FTP, the panics seem to be gone for good. Pheeeeew.

athurdent · Aug 3, 2013, 2:54 PM

Many thanks to Jimp for finally removing the rest of the problematic patches! FTP is finally working again :)

lucky · Aug 3, 2013, 3:12 PM

@athurdent:

Many thanks to Jimp for finally removing the rest of the problematic patches! FTP is finally working again :)

Awesome! Do you know which snapshot this takes/took effect in? I'd like to test it out. Thanks!

doktornotor · Aug 3, 2013, 3:14 PM

@lucky:

Awesome! Do you know which snapshot this takes/took effect in? I'd like to test it out. Thanks!

Certainly there with 2.1-RC1 (i386) built on Thu Aug 1 19:03:48 EDT 2013 and anything newer.