Brian Bobowski wrote:
> Norberto Meijome wrote:
>
>> Brian Bobowski wrote:
>>
>>
>>> I'm poking at that now, yes. I had difficulty getting it to work with
>>> virtual hosts... but I can at least reference it by the private-side IP
>>> address and get places.
>>>
>>
>> assuming you are using Ap
Norberto Meijome wrote:
Brian Bobowski wrote:
I'm poking at that now, yes. I had difficulty getting it to work with
virtual hosts... but I can at least reference it by the private-side IP
address and get places.
assuming you are using Apache, you can use * for Ip address and let it
be
Brian Bobowski wrote:
> Norberto Meijome wrote:
>
>> Brian Bobowski wrote:
>>
>>
>>> All right. I've got my firewall up and running, and my workstation can
>>> get almost anywhere it needs to just fine.
>>>
>>
>> you dont' say if you are using ipfw, ipf , pf
>>
>>
>>
> Sure I do. IPFW;
Norberto Meijome wrote:
Brian Bobowski wrote:
All right. I've got my firewall up and running, and my workstation can
get almost anywhere it needs to just fine.
you dont' say if you are using ipfw, ipf , pf
Sure I do. IPFW; mentioned lower down.
I can access it by directly r
Brian Bobowski wrote:
> All right. I've got my firewall up and running, and my workstation can
> get almost anywhere it needs to just fine.
you dont' say if you are using ipfw, ipf , pf
> I can access it by directly referencing the private-interface IP, but if
> my workstation tries to get t
All right. I've got my firewall up and running, and my workstation can
get almost anywhere it needs to just fine.
The lone exception being the web server located on the firewall machine
itself.
I can access it by directly referencing the private-interface IP, but if
my workstation tries to g