Thanks, I have done everything but the logs. I haven't had time to get to
them. I was sure it should be something simple, but for the life of me I
couldn't get a connection.
So, I will watch the logs this weekend and see what gives.
--
Heath Henderson
[EMAIL PROTECTED]
1800 288 7750
--
> Fr
I do it a little differently... There are machines I don't want proxied,
like the servers and my workstation.
So I tell pfSense to allow port 80 outbound from 192.168.0.0/23 and block it
for other ranges. Users get the proxy information entered by their windows
domain login script, and don't have
Shouldn't be anything special - make sure SSH is turned on in the advanced
page, and give the machine time to generate ssh keys etc. (you'll get a
message at the top of your window when that is done)
Also confirm you're using the right port (22)
Check out the firewall logs page as well, just aft
Craig,
Thanks for the reply.
This is for my home network and I'm using Macs. I can obviously point them
to a proxy, but I'd like to avoid that. I like the FW to Filter box to
handle everything. The main reason for this transparency is that when I
have friends or family over with a wireless laptop
I guess I'm not seeing a way to do this in the GUI. If that's the case,
how is it done from the command line?
Thanks,
Stephan
> Adding a rule (before the default rules) that takes port 80 from
> !squidserverip --> and forward it to the squid box should do the trick.
>
> -lsf
>
>
> On 8/18/06, ste
On 8/24/06, Robert Mortimer <[EMAIL PROTECTED]> wrote:
> On 8/24/06, Robert Mortimer <[EMAIL PROTECTED]> wrote:
> > I have 2 ADSL lines each with it's own pfsense box.
> >
> > I have set up CARP to provide a common LAN address shared
> between the two
> > boxes
> >
> > Should this configuration l
Is there a trick to getting SSH to work? I have enabled this setup, but I
can't seem to access this from either my LAN or WAN side. I would bet I
can't get it from the WAN, but I thought I should be able to access from the
LAN when enabled. Also, I see no rules stating that I can't access port 2
It won't be added to 1.0 for sure. 1.0 is featurefrozen due to the release
coming soon. However, it should be integrateable in the next version
(hopefully). Nobody said this will never come true.
Holger
> -Original Message-
> From: Tunge2 [mailto:[EMAIL PROTECTED]
> Sent: Thursday, Augu
On 8/24/06, Robert Mortimer <[EMAIL PROTECTED]> wrote:
No problem. Is it in Head or are you looking for volunteers? I'm still
moving on with DDNS for the local DHCP server but I am away to the wilds of
Wales (sans computer) for a while so it will be two weeks before I have
results.
No, I don't
I posted this to the forum, but I know a lot of people are more active on
the mailing list, so I figured I'd repost here, in hopes of some more help
:)
I've noticed since moving to RC2, that the CPU usage on our PFSense box is
higher than it normally is. I'm not sure if this is cause for alar
> On 8/24/06, Robert Mortimer <[EMAIL PROTECTED]> wrote:
> > I have 2 ADSL lines each with it's own pfsense box.
> >
> > I have set up CARP to provide a common LAN address shared
> between the two
> > boxes
> >
> > Should this configuration load balance? At the moment the traffic graphs
> > seem to
On 8/24/06, Robert Mortimer <[EMAIL PROTECTED]> wrote:
I have 2 ADSL lines each with it's own pfsense box.
I have set up CARP to provide a common LAN address shared between the two
boxes
Should this configuration load balance? At the moment the traffic graphs
seem to have all traffic going out
I have 2 ADSL lines each with it's own pfsense box.
I have set up CARP to provide a common LAN address shared between the two
boxes
Should this configuration load balance? At the moment the traffic graphs
seem to have all traffic going out of the master address until fail over
--Robert
--
A few weeks back I found a problem with dhclient, or much rather with
/etc/rc and /etc/rc.newwanip. The problem was impacting the (Australia)
Bigpond WAN connection. The dhclient-script has exit hooks which trigger
/etc/rc.newwanip to be executed. The later not only (re)starts Bigpond WAN
connec
On 8/24/06, Tunge2 <[EMAIL PROTECTED]> wrote:
Is it so difficult to add this feature? We have the same problem (missing
pppoe on OPT port) But the rest of Pfsense (IPSec, openvpn, features,
stability) are much better then the rest of the crap in
Internet-router-land
It will be added in a futu
Is there something changed in the dhclient version/configuration in Pfsense
version RC2?? We had many problems with a exiting dhclient in RC1 and the
versions before RC1. But in RC2 the problem is fully disappeared?
Keep up the good work!!!
-Oorspronkelijk bericht-
Van: Scott
Is it so difficult to add this feature? We have the same problem (missing
pppoe on OPT port) But the rest of Pfsense (IPSec, openvpn, features,
stability) are much better then the rest of the crap in
Internet-router-land
-Oorspronkelijk bericht-
Van: Scott Ullrich [mailto:[EMAIL PROTE
17 matches
Mail list logo
