On Mon, Aug 10, 2009 at 3:18 PM, Evgeny Yurchenko wrote:
>
> How can I test it? change patch-fbsd and recompile?
You still working with a FreeBSD 6.2-based version? You can clone the
tools repo and build it from there on a stock FreeBSD box, or I can
easily build a binary for you to test if you le
On Mon, Aug 10, 2009 at 10:47 AM, Pete Boyd wrote:
>
> Like I said, should pfSense _not_ be offering the broadcast address as a
> choosable option for an IP address for a client computer?:
>
It will if you tell it to. The input validation there is only on
subnet boundary, it doesn't have a sanity
On Mon, Aug 10, 2009 at 8:23 AM, Atkins, Dwane P wrote:
> We are trying to install, and upgrade, from 1.2 RELEASE and 1.2.3 to 1.2.3
> RC1. We are using Dell R200s. I am not sure if I possibly got a bad
> download or the R200 needs a different snapshot? We are loading with the
> multiple process
Ermal Luçi wrote:
On Fri, Jul 31, 2009 at 7:36 PM, Evgeny
Yurchenko wrote:
From: cbuech...@gmail.com [mailto:cbuech...@gmail.com] On
Behalf Of Chris Buechler
On Thu, Jul 30, 2009 at 8:33 PM, Evgeny
Yurchenko wrote:
The code of igmpproxy is heavily inhe
>
> Like I said, should pfSense _not_ be offering the broadcast address as a
> choosable option for an IP address for a client computer?:
>
>
I guess it shouldn't, but I've never used the whole subnet, because I always
need a couple of fixed addresses. So, I always have to modify the range
option.
Jaime Díaz wrote:
Ahh, I _really_ should have seen this earlier. The DHCP server offers an
available range of 10.1.0.0 - 10.1.0.255. 10.1.0.255 is the broadcast
address.
Is this a bug in pfSense?
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on e
>
> Ahh, I _really_ should have seen this earlier. The DHCP server offers an
> available range of 10.1.0.0 - 10.1.0.255. 10.1.0.255 is the broadcast
> address.
> Is this a bug in pfSense?
>
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on eth0 to 255.255.255.255 port 6
We are trying to install, and upgrade, from 1.2 RELEASE and 1.2.3 to 1.2.3 RC1.
We are using Dell R200s. I am not sure if I possibly got a bad download or
the R200 needs a different snapshot? We are loading with the multiple
processor option.
Thank you
Dwane
> On Wed, Aug 5, 2009 at 7:45 AM, Pete Boyd
> wrote:
>> Hi. I've added a second network card to an existing functioning pfSense
>> 1.2.2 firewall and setup dual LAN successfully apart from, unless I set
>> a
>> gateway address (of the new LAN IP interface) in the new LAN interface's
>> DHCP server
On Fri, Jul 31, 2009 at 7:36 PM, Evgeny
Yurchenko wrote:
>> From: cbuech...@gmail.com [mailto:cbuech...@gmail.com] On
>> Behalf Of Chris Buechler
>>
>> On Thu, Jul 30, 2009 at 8:33 PM, Evgeny
>> Yurchenko wrote:
>> >
>> > The code of igmpproxy is heavily inherited from mrouted and actual
>> > proxy
Evgeny Yurchenko wrote:
> Logs in pfSense are circular, they do not grow. But you can set up
> sending logs to remote syslog server.
with a little effort you can have both the local circular blog and
syslog-to-remote, and even to have three - local circular, local full
and remote.
this involves a
11 matches
Mail list logo
