I've got some changes in beta2.  Please test
http://www.pfsense.com/~sullrich/pfSense-Full-Update-1.0-PREBETA2-BUG-VALIDATION-EDITION.tgz

If for some reason it is not working, follow this procedure:

Boot up firewall, disable helper for interface in question.  Try again.

I've added FTPSESAME in hopes that it will catch the edge cases.   All
in all, I hate FTP.

Scott


On 1/3/06, Charles Sprickman <[EMAIL PROTECTED]> wrote:
> Following up to myself...
>
> On Tue, 3 Jan 2006, Charles Sprickman wrote:
>
> > # ps -auxw|grep ftp
> > proxy     551  0.0  0.4  1276   884  ??  Ss   Sun10PM   0:00.78
> > /usr/local/sbin/pftpx -c 8021 -g 8021 192.168.0.254
>
> Problem one, apparently pftpx isn't notified about LAN IP change, so it
> still was doing something with the old LAN IP.
>
> > So I killed it and then tried to run it again with the same args, but with a
> > different IP to bind to:
> >
> > # /usr/local/sbin/pftpx -c 8021 -g 8021 192.168.0.1
> > pftpx: bind failed: Can't assign requested address
>
> Apparently it tries to bind to the loopback (127.0.0.1).
>
> After some looking around for anything else listening on those ports and
> not finding anything and then running pftpx with full debugging, I thought
> I'd check out if anything odd was going on with the loopback:
>
> lo0: flags=8048<LOOPBACK,RUNNING,MULTICAST> mtu 16384
>          inet6 ::1 prefixlen 128
>          inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
>
> See anything interesting there? :)
>
> No IPv4 IP address.
>
> ifconfig'd lo0 with 127.0.0.1 and started pftpx and all is well.
>
> Any idea where my loopback went?
>
> Thanks,
>
> Charles
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to