On 4/20/2014 4:13 PM, Volker Kuhlmann wrote:
On Sun 20 Apr 2014 19:46:41 NZST +1200, Bryan D. wrote:
I reported this issue with the HME's a while ago (it's nasty!):
bug #3481 -- https://redmine.pfsense.org/issues/3481
Executive summary: replace the NIC with a different model. Too bad,
they use
The GS108T-200 is the one with a web-based config tool
Worth adding that you can pick up the HP 1700-8 for less than £60 these
days, now that it's been superceded by the 1810-x series switches.
Fairly intuitive web interface and talks SNMP too. Admittedly not
gigabit, but as a multi-WAN VLAN
On Mon 21 Apr 2014 10:51:13 NZST +1200, Stefan Baur wrote:
Thanks muchly for the tip, Stefan!
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 elsewher
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 the wifi AP from
the pfsense box and re-plugging it still g
Am 21.04.2014 00:40, schrieb Stefan Baur:
> I heard the 8-port model GS108E is actually easier to configure (Web GUI
> instead of Adobe-Air-based proprietary tool), but I can't claim personal
> experience with that, so don't take my word for it, but ask someone who
> actually configured it.
Errat
Am 21.04.2014 00:32, schrieb Volker Kuhlmann:
> The frequently recommended option of using VLANs may look good for
> larger commercial networks, but just buying a VLAN capable switch costs
> more than a suitable pfsense box and brings the power budget of the
> combination to the same level as a scr
On Mon 21 Apr 2014 09:54:49 NZST +1200, Jim Pingle wrote:
> Apply this patch with the system patches package, see if it's maybe
> hitting a bug similar to what was happening with OpenVPN (rc.newwanip
> was being fired from rc.linkup repeatedly... something made it fall into
> a loop)
Thanks Jim!
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
scrap and I'm stuck. What are alternatives now?
Are there any other 4
On 4/20/2014 5:13 PM, Volker Kuhlmann wrote:
> On Sun 20 Apr 2014 19:46:41 NZST +1200, Bryan D. wrote:
>> I reported this issue with the HME's a while ago (it's nasty!):
>> bug #3481 -- https://redmine.pfsense.org/issues/3481
>>
>> Executive summary: replace the NIC with a different model. Too bad,
On Sun 20 Apr 2014 19:46:41 NZST +1200, Bryan D. wrote:
> I reported this issue with the HME's a while ago (it's nasty!):
> bug #3481 -- https://redmine.pfsense.org/issues/3481
>
> Executive summary: replace the NIC with a different model. Too bad,
> they used to work very well and virtually neve
On 2014-Apr-20, at 12:33 AM, Volker Kuhlmann wrote:
> Ever since upgrading to pfsense 2.1 I have been let down by it. It looks
> like there are multiple issues and I am trying to separate them. One is
> system suicide by memory gobbling - but it's been a little tricky to
> find out why exactly.
Ever since upgrading to pfsense 2.1 I have been let down by it. It looks
like there are multiple issues and I am trying to separate them. One is
system suicide by memory gobbling - but it's been a little tricky to
find out why exactly.
It's a system with 512MB RAM, 768M swap.
Mobo Ethernet, Intel
12 matches
Mail list logo
