I am running the latest snapshot:
1.0-SNAPSHOT-09-14-06
Whenever I tick the
Enable Static Arp Entries box on the DHCP server
I get the following complaint in my logs:
dhcpd: failover peer dhcp6: invalid argument
I've tried to search the support archives, as well as
check dhcp man pages, but
Okay, upon turning off the `anti-lockout rule`, my ssh is getting
SIGTERM. Continously, every minute. I tried changing its port, but it
behaves the same way.
Nov 11 12:05:56 sshd[43770]: Server listening on 0.0.0.0 port 22.
Nov 11 12:05:56 sshd[43770]: Server listening on :: port
I have not tested this yet. Does anyone else have these problems?
Does anyone else have static arp entries working properly?
On 11/11/05, Szasz Revai Endre [EMAIL PROTECTED] wrote:
Okay, upon turning off the `anti-lockout rule`, my ssh is getting
SIGTERM. Continously, every minute. I tried
I am trying to replace a FireBox Firewall with pfsense. Our current
setup has 5 static IP addresses. The range is xxx.xxx.xxx.138-142. On
the firebox (which has a limited way of entering things anyway) this is
specified 162.39.251.138/29 and thme it uses aliases. How should I set
these up so
On Nov 9, 2005, at 11:05 AM, Robert Goley wrote:
I am trying to replace a FireBox Firewall with pfsense. Our current
setup has 5 static IP addresses. The range is xxx.xxx.xxx.
138-142. On
I did this transition recently and it went very well. What you want
to do is set up an ARP alias
I tried adding the ARP entries. That is what this email is about. I
was trying to make sure I was doing this correctly. When I added the
addresses as single entry per IP (like xxx.xxx.xxx.139/32,
xxx.xxx.xxx.140/32) the only one that pfsense answered to was the 139
address. I noticed you could
Hello,
Why is it, when Static ARP entries are enabled, a user which is not in
the DHCP client list still `sees` the server ? (can ping, etc)
Even if the user uses an ip that is in the list, and the mac is
different, it can still connect to captive portal for example.
How to get around this ?
Interesting, sounds like a bug. Are these clients on LAN or other
interface? I wonder if we made this only work on LAN.
--Bill
On 11/8/05, Szasz Revai Endre [EMAIL PROTECTED] wrote:
Hello,
Why is it, when Static ARP entries are enabled, a user which is not in
the DHCP client list still
These are on LAN, it's weird..
For a client on the LAN, I have deleted a DHCP mac/ip entry, and that
client would still have access to the captive portal, or any other
service pfsense would offer.
On 11/8/05, Bill Marquette [EMAIL PROTECTED] wrote:
Interesting, sounds like a bug. Are these
On 11/8/05, Szasz Revai Endre [EMAIL PROTECTED] wrote:
These are on LAN, it's weird..
For a client on the LAN, I have deleted a DHCP mac/ip entry, and that
client would still have access to the captive portal, or any other
service pfsense would offer.
So basically there was a static-arp entry
Szasz Revai Endre wrote:
No, a reboot doesn't fix the error.
The problem is, as I see, that no client is denied on the network
(none of those who have static ip addresses), everyone has access to
this machine (pfsense).
to the firewall itself, yeah. The anti-lockout rule assures that.
Of course, that is normal.
But for example any client on the network has access to the captive
portal and to echo request, which is normal?
If i turn that anti lockout rule off, this shouldn't be possible ?
On 11/9/05, Chris Buechler [EMAIL PROTECTED] wrote:
to the firewall itself, yeah. The
12 matches
Mail list logo
