On 12/10/2009 6:56 PM, Scott Ullrich wrote:
> On Thu, Dec 10, 2009 at 6:54 PM, RB wrote:
>> Well, for posterity's sake then: if you have trouble in
>> pfSense/FreeBSD with traffic not passing through an Intel 10/100 NIC
>> (fxp), particularly when return/inbound packets aren't showing up in
>> mpd
On Thu, Dec 10, 2009 at 6:54 PM, RB wrote:
> Well, for posterity's sake then: if you have trouble in
> pfSense/FreeBSD with traffic not passing through an Intel 10/100 NIC
> (fxp), particularly when return/inbound packets aren't showing up in
> mpd or another user-level program, turn off TCP Offlo
On 2009-12-10, Scott Ullrich wrote:
>> I'll try turning off ToE in a few hours and report the results. If
>> all goes well, I'd hope the 1.2.3 final version picks up the noted
>> stable/7 change.
This was the fix - thanks, Tom, for identifying such an edge case and
linking it to your bug!
> Sor
On Thu, Dec 10, 2009 at 1:21 PM, RB wrote:
> On Thu, Dec 10, 2009 at 10:29, Tim Dressel wrote:
>> For me the issue was exactly like you are describing. Can connect and
>> everything appears OK, but just zero traffic flow. Nothing useful in logs.
>> Then all of a sudden it would start passing traf
On Thu, Dec 10, 2009 at 10:29, Tim Dressel wrote:
> For me the issue was exactly like you are describing. Can connect and
> everything appears OK, but just zero traffic flow. Nothing useful in logs.
> Then all of a sudden it would start passing traffic, but then get sketchy
> and eventually stop a
Not that it helps much, but I have had severe problems with the fxp driver
under BSD/pfsense. I mentioned this a while back and Chris suggested that
this was only in a few snapshots. Not being one to argue with a
support/developer because I am in awe with this project, but I can replicate
traffic f
Am 09.12.2009 um 15:38 schrieb RB:
I made a special trip - log attached. A check of my tcpdump
monitoring actually indicates that while ng0 does not see return
traffic, the physical interface (actually fxp3) does. It's also
indicating that the return packets are 2 bytes larger than it expects
On Wed, Dec 9, 2009 at 07:38, RB wrote:
> I made a special trip - log attached. A check of my tcpdump
> monitoring actually indicates that while ng0 does not see return
> traffic, the physical interface (actually fxp3) does. It's also
> indicating that the return packets are 2 bytes larger than
On 2009-12-09, Jim Pingle wrote:
> Are you sure that your DSL link is solid and noise-free? I have seen
> cases where routers would sign on but could not pass traffic and it
> turned out to be a weak DSL signal. Does this same line work with any
> other router?
It works with the same physical set
On 12/9/2009 9:01 AM, RB wrote:
> On Wed, Dec 9, 2009 at 01:34, Ermal Luçi wrote:
>> Please provide logs of mpd and explain more what you are trying to do and
>> how you are trying to achive it!
>
> What I'm trying to achieve is awfully simple - with a fresh install of
> 1.2.3-RC3, I'm plugging a
On Wed, Dec 9, 2009 at 3:01 PM, RB wrote:
> On Wed, Dec 9, 2009 at 01:34, Ermal Luçi wrote:
> > Please provide logs of mpd and explain more what you are trying to do and
> > how you are trying to achive it!
>
> What I'm trying to achieve is awfully simple - with a fresh install of
> 1.2.3-RC3, I
On Wed, Dec 9, 2009 at 01:34, Ermal Luçi wrote:
> Please provide logs of mpd and explain more what you are trying to do and
> how you are trying to achive it!
What I'm trying to achieve is awfully simple - with a fresh install of
1.2.3-RC3, I'm plugging a dumb Speedport ADSL modem in to one ether
On Wed, Dec 9, 2009 at 8:58 AM, RB wrote:
> I've been fighting a losing battle with an update from 1.2.3-RC1 to
> 1.2.3-RC3 and am at the end of my options. This also exhibits in the
> 2.0-ALPHA-ALPHA 8.0-based snapshot I grabbed two days ago.
>
> With both an upgrade and a fresh install, when I
I've been fighting a losing battle with an update from 1.2.3-RC1 to
1.2.3-RC3 and am at the end of my options. This also exhibits in the
2.0-ALPHA-ALPHA 8.0-based snapshot I grabbed two days ago.
With both an upgrade and a fresh install, when I configure a simple
LAN + PPPoE WAN, the WAN negotiat
14 matches
Mail list logo
