And with that, and my 20 years in the industry, I unsubscribe from this list.

Learn some fucking tact, Adam.


On Feb 21, 2014, at 10:12 PM, Adam Thompson <athom...@athompso.net> wrote:

> The obvious problem is that it looks like you have two interfaces in the same 
> subnet.  That (generally) doesn't work unless you are a routing guru in the 
> first place and know exactly what you're doing.  Which, with apologies for 
> bluntness, you obviously don't.
> 
> The  problem isn't with pfSense, it's with your entire concept of how IP 
> works.
> Go read a book on IP first, then try again?  (Sorry if I'm wrong, but it 
> seems like the problem is at that level...)
> 
> -Adam
> 
> On Feb 21, 2014 7:13 PM, Ryan Coleman <ryanjc...@me.com> wrote:
>> 
>> Does anyone have an ideas? 
>> 
>> Thanks! 
>> 
>> 
>> On Feb 20, 2014, at 4:04 PM, Ryan Coleman <ryanjc...@me.com> wrote: 
>> 
>>> I’m moving away from single server design on my ESXi box to dedicated 
>>> guests for each service but I cannot seem to get those dedicated services 
>>> through the firewall. 
>>> 
>>> I have a 29bit subnet (IPs 1 through 5). Everything is internal to the ESXi 
>>> (5.1) server. 
>>> 
>>> .1 = pfSense Firewall 
>>> .2 = OPT1 interface on pfSense 
>>> .3 = Customer VM (will port over to OPT2 after this works) 
>>> .4 = All-in-one hosted VM 
>>> .5 = Same All-in-one hosted VM 
>>> 
>>> I am going to eliminate .4 and .5 as I pull specific services out and into 
>>> VMs (I’ve already moved the basic part of the FTP, the entire SQL server 
>>> and LDAP to internal systems). 
>>> 
>>> But whenever I set up NAT rules on .2 it seems to be using .1’s stuff. 
>>> 
>>> I will have the following pushed through: 
>>> FTP 
>>> WWW (one primary, each subserver has functioning Apache for their services) 
>>> IMAP SSL/SMTP 
>>> SSH (via pushed ports to each server) 
>>> 
>>> Any thoughts would be helpful. The biggest thing I need to get running now 
>>> is the FTP part - I cannot get it to push through nor will it register on 
>>> the firewall log that it’s being blocked. 
>>> — 
>>> Ryan 
>>> _______________________________________________ 
>>> List mailing list 
>>> List@lists.pfsense.org 
>>> http://lists.pfsense.org/mailman/listinfo/list 
>> 
>> _______________________________________________ 
>> List mailing list 
>> List@lists.pfsense.org 
>> http://lists.pfsense.org/mailman/listinfo/list 

_______________________________________________
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to