On Tue 22 Apr 2014 15:56:52 NZST +1200, Volker Kuhlmann wrote:
> I just had another runaway after adding a mac/ip in the wifi interface's
> dhcp server. Confirmed with trivial test of adding another test entry to
> the dhcp server.
I should have mentioned that the pfsense syslog (sent to a syslog
On Tue 22 Apr 2014 01:28:08 NZST +1200, Jim Pingle wrote:
Thanks Jim!
> Some other setting appears to be causing the link on the NIC to bounce
> up and down when configured.
> We added some extra checks before resetting the MAC to prevent that sort
> of thing from being a problem though, but it'
OK, so I found the solution, or at least a workaround to my bigger issue.
It seems that the issues disappear when I check the "Clear invalid DF bits
instead of dropping the packets" checkbox under System: Advanced: Firewall
and NAT.
This gave me reason to scour through my old m0n0wall config, and
Hello all,
I have a strange problem. Over the weekend, I replaced an older M0n0wall
installation that has been faithfully serving me for several years with a
PFSense installation on a Soekris net6501. I had installed 2.1 on the
flash, and imported the config from the M0n0wall box (which worked
fla
On 14-04-21 03:46 PM, Bryan D. wrote:
FYI, in my case there was no MAC spoofing and the issue occurred when an hme port was
used for a LAN and/or WAN interface. I don't have the resources, right now, but it'd be
good if someone could try a "raw" OS-only install and see whether the issue
exist
On 2014-Apr-21, at 6:28 AM, Jim Pingle wrote:
>
>
> The Spoofed MAC address issue was a problem in the past with certain
> drivers that sounds very similar because it got into a chicken-and-egg
> scenario that went a little something like this:
>
> * pfSense sets the MAC address
> * The NIC dr
I have an embedded (soekris) install running 2.0.1-RELEASE.
This weekend, I attempted an in-place upgrade to 2.1.2-RELEASE. After the
upgrade, all interfaces appeared to be configured correctly:
- while ssh'ed into pfsense, I could access internet hosts
- all internal VLAN interfaces were configu
On 21 Apr 2014 at 10:32, Volker Kuhlmann wrote:
> I've been running pfsense for many years (and been very happy with it)
> on scrapped PCs with a Sun 4-port Ethernet PCI card because I need 5
> Ethernet ports.
This was discussed on the list last year.
[pfSense] 4 port ethernet card -- STARTECH S
On 4/20/2014 7:02 PM, Volker Kuhlmann wrote:
> On Mon 21 Apr 2014 09:54:49 NZST +1200, Jim Pingle wrote:
>
>> http://files.pfsense.org/jimp/patches/openvpn-tapbridgefix-2.1.x.diff
>
> This has no effect on the hme problem unfortunately.
>
> I rebooted and re-tested, but unplugging the cable to t
On Sun, Apr 20, 2014 at 6:32 PM, Volker Kuhlmann
wrote:
> I've been running pfsense for many years (and been very happy with it)
> on scrapped PCs with a Sun 4-port Ethernet PCI card because I need 5
> Ethernet ports.
>
> Now freebsd dieing on the hme driver effectively turns those cards into
> sc
On Sun, Apr 20, 2014 at 5:13 PM, Volker Kuhlmann
wrote:
> The number of spawned php processes that kill the system however look
> like a pfsense problem to me and the php code should prevent itself from
> meltdown. Or does freebsd really require php for handling interface
> hotplug events? As in,
On 21.04.2014 00:32 Volker Kuhlmann wrote:
> Now freebsd dieing on the hme driver effectively turns those cards into
> scrap and I'm stuck. What are alternatives now?
>
> Are there any other 4-port cards that are supported by pfsense in
> practice (not just in theory), that are also affordable?
I
Am 21.04.2014 02:13, schrieb Volker Kuhlmann:
> There is no 'doze in the house and on no account will I add a
> Billy-dependency to my infrastructure. Any manufacturer too stupid to make
> their stuff controllable by open source software can sell elsewhere.
> Period.
Well, there is http://sourcef
13 matches
Mail list logo
