Koozali.org: home of the SME Server
Contribs.org Forums => General Discussion => Topic started by: Yull on February 05, 2015, 08:45:31 AM
-
Good Morning
I'm not a network expert, but I focus on the most of free software in a professional context (a cooperative), software to which I bring a little financial support
For several years, I use a firewall (pfsense 2.2) with behind sme server 9.0
Since the pfsense update to 2.15 to 2.2, it appears that the operation of pfsense has changed, because I have problems to enter the FTP passive mode:
Since the update pfsense during the sme server in passive mode transition back its internal IP: 192.168.99.1, which works with a lot of programs that know how to handle this error, but I have a problem with some of the most respectful software standard ...
I also access the FTP server internally with 192.168.99.1
My network:
192.168.100.* 192.168.100.254
LAN ------- LAN 1 ---------|
SME Server ------- LAN 2 - -------| pfSense --- WAN --- Modem bridge
192.169.99.1 192.168.99.254 mon-adresse.dyndns.info (dynamic IP)
If someone could explain to me just how to set sme server to bypass the change in operating pfsense
FYI, my Linux skills are not terrible, I limit myself to use winscp and putty
Thank you in advance
-
Please do not cross post, and continue your thread here http://forums.contribs.org/index.php/topic,51479.0.html
-
Not strictly SME related, as it is used to work before pFsense upgrade..
moving to General Discussion
-
I don't think there's anything SME can (or should) do. SME is doing the correct thing, it has no idea of your public address. You have to fix what's not working on the pfsense.
-
I would add that if it is used to work before pFsense upgrade, it's likely a pFsense issue and so OP should ask on pFsense's fourms