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 used to work very well and virtually never die.
Confirm on (almost) all counts.
I moved the printer to an rl driver port and the problem disappeared.
top reports 350MB free memory.
The same problem exists with the wifi AP connected to an hme driver
port. Turning the AP off then on kills pfsense.
I'll update the report.
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, a basic minimal freebsd system does not work
without php installed?
Thanks for the hint Bryan.
Volker
When moving to 2.1.2 on a system with realtek (re* drivers), I ran into
problems with 10/100/1000 auto-negotiation. My setup is unusual , in
that I have a gigabit fiber media converter, in the path. The symptom
was you could watch the ethernet PHY switch from various modes
(master/slave/full-duplex/half/etc). (Repeatedly calling ifconfig.)
When I put an ethernet switch at each end, the problem goes away. As far
as I know, there isn't really a case defined in 802.3u (Clause 28) to
handle auto-negotiation through a media converter. (Media Converters
"lie" to the other end, in order to pass link status notification through).
I'd put a cheap un-managed switch in and see if it goes away.
The Intel quad port GB nics work quite well with pfSense. They are more
expensive than other random hardware, but...
The changes from 2.0.x to 2.1 were a lot more than the changes from 2.1
to 2.1.1(2.1.2)
Putting the unmanaged (gigabit) switch in would give a good clue as to
the negotiation issues. If it fixes it, is probably related to the PHY
handling.
_______________________________________________
List mailing list
[email protected]
https://lists.pfsense.org/mailman/listinfo/list
