Old Synopsis: ARP cache can be poisoned or polluted with ease.
New Synopsis: [arp] ARP cache can be poisoned or polluted with ease.
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Fri Jul 9 07:42:45 UTC 2010
Responsible-Changed-Why:
I have the same problems like in
http://lists.freebsd.org/pipermail/freebsd-current/2009-November/013222.html
and you are discussing. Unfortunately, I have no test machine yet. But I
think in short time I can send you backtrace.
The problem with Intel Gigabit ET Quad Port Server Adapter (Ethernet
On Fri, 19 Jun 2009 13:55:26 +0300
Vladimir Terziev wrote:
> What should i put for HOSTAPD_CFLAGS, HOSTAPD_DPADD, HOSTAPD_LDADD or
> WPA_SUPPLICANT_* (not sure which ones i should use) in order to get
> hostapd rebuilt with the functionality i want ?
For the archives, the following lines in /et
Пересылаемое сообщение
09.07.10, 13:23, "Dmukha Nikolay" :
I have the same problems like in
http://lists.freebsd.org/pipermail/freebsd-current/2009-November/013222.html
and you are discussing. Unfortunately, I have no test machine yet. But I think
in short time I can send y
On 8 Jul 2010, at 07:17, Hiroki Sato wrote:
> Darren Pilgrim wrote
> in <4c3565e8.5040...@bitfreak.org>:
>
> fr> I can't find any hint of support for it. Did I miss something? If
> fr> not, is there any work adding support for 6RD (RFC5569)?
>
> A patch for 8.x is available:
>
>
> http://
On Wed, 2010-07-07 at 09:22 -0700, Jack Vogel wrote:
> Interesting, didn't know any vendor had combined PCH and 82574 on one board,
> yes, they are
> completely different, as you can see the one only supports MSI, its a client
> NIC.
>
> I would agree with Mike, disable anything having to do with
On Wed, 7 Jul 2010, Shtorm wrote:
>
> > Yow, 30 vlans, but only em1 is using vlans not em0?
> >
> > Is only em1 having watchdogs? I noticed you appear to
> > have flow control off, maybe turning it on would help.
> >
> > I would like to see the log messages from the watchdogs.
> > Jack
Synopsis: [arp] ARP cache can be poisoned or polluted with ease.
State-Changed-From-To: open->closed
State-Changed-By: remko
State-Changed-When: Fri Jul 9 14:36:42 UTC 2010
State-Changed-Why:
Hello, this is why we invented static ARP if you do not want to have the
cache modified. Else this is a p
On Fri, 2010-07-09 at 23:58 +1000, Ian Smith wrote:
> On Wed, 7 Jul 2010, Shtorm wrote:
> >
> > > Yow, 30 vlans, but only em1 is using vlans not em0?
> > >
> > > Is only em1 having watchdogs? I noticed you appear to
> > > have flow control off, maybe turning it on would help.
> > >
> > >
Today is your last chance to submit a CFP abstract for the 2010 Surge
Scalability Conference. The event is taking place on Sept 30 and Oct 1,
2010 in Baltimore, MD. Surge focuses on case studies that address
production failures and the re-engineering efforts that led to victory
in Web Application
On 3 July 2010 08:27, Ryan Stone wrote:
> I just bought a laptop with a Atheros AR9XXX and as far as I can tell
> there is no driver support yet in FreeBSD. Some googling has seemed
> to indicate that there is a driver in OpenBSD(athn) that supports this
> family of cards. I was wondering if the
On Fri, Jul 9, 2010 at 1:03 AM, Jack Vogel wrote:
> Damn, thats bad, and this is with what installed exactly, RC1, 2? I'll have
> someone in validation install to see if we can repro this tomorrow, let me
> know what it is asap.
>
Here are some pictures of the screen, with the backtrace, the ifco
Is this kernel 32 bit? And is my code altered, it seemed some debug I saw
was
not familiar. Last, can you try the code in HEAD to see if it changes
anything.
Jack
On Fri, Jul 9, 2010 at 9:06 AM, Chris Buechler wrote:
> On Fri, Jul 9, 2010 at 1:03 AM, Jack Vogel wrote:
> > Damn, thats bad, and
LOL, the way the watchdog code works these days it records the clock
at key TX points and then compares that in the timer code, so if your
system is dinking around with the time that could be the cause of this.
Can you change the environment to guarantee a continuous time
stream and then see what
On Fri, 9 Jul 2010, Shtorm wrote:
> Yeah, saw this too, it was first boot for this install and I forgot to
> run tzsetup during flash image build.
>
> As for the latest log, this box connected to internet via em0, ntpd just
> says it have some peers to sync with after interface flap.
>
>
Hm, I see that you're using the ticks variable. To the best of my
knowledge, changing the current time should not cause ticks to change.
A lot of things, like the callout wheel, would be pretty broken if
that were happening. My knowledge of this stuff is several major
versions out of date, thoug
OK, its just that something odd is going on since my testers are not seeing
this happening, fishing for ideas
Jack
On Fri, Jul 9, 2010 at 9:52 AM, Ryan Stone wrote:
> Hm, I see that you're using the ticks variable. To the best of my
> knowledge, changing the current time should not cause
Yes, I'm not a kernel hacker, but cat understand what C code says, I see
your point. It will take few days until I can get to server room, will
try without ntpd.
Also, I have kern.hz=4000 in loader.conf, as far as I understand tick
length will be 25 ms and timeout for watchdog will be 10*25 ms = 2
No, defining EM_WATCHDOG as 10 * hz should mean that the watchdog
expires after 10 seconds no matter what your kern.hz is. hz is set to
the number of ticks in a second.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fr
Well, you can always try increasing it, but its unlikely that the
problem is the constant, in the older style watchdog code this
was set to 5 so I am already being lenient :)
Jack
On Fri, Jul 9, 2010 at 10:24 AM, Shtorm wrote:
> Yes, I'm not a kernel hacker, but cat understand what C code says
On Fri, Jul 9, 2010 at 12:18 PM, Jack Vogel wrote:
> Is this kernel 32 bit?
It does exactly the same with 32 and 64 bit.
> And is my code altered, it seemed some debug I saw
> was
> not familiar.
Nothing in sys/dev/e1000 is changed. Copying Ermal who wrote most/many
of the changes. They don't t
The following reply was made to PR misc/148463; it has been noted by GNATS.
From: Paul Miseiko
To: "bug-follo...@freebsd.org" ,
"pmise...@gmail.com"
Cc:
Subject: Re: misc/148463: [arp] ARP cache can be poisoned or polluted with
ease.
Date: Fri, 9 Jul 2010 10:45:17 -0700
--_000_3B704
On Fri, Jul 9, 2010 at 11:05 AM, Chris Buechler wrote:
> On Fri, Jul 9, 2010 at 12:18 PM, Jack Vogel wrote:
> > Is this kernel 32 bit?
>
> It does exactly the same with 32 and 64 bit.
>
> > And is my code altered, it seemed some debug I saw
> > was
> > not familiar.
>
> Nothing in sys/dev/e1000
On Fri, 9 Jul 2010, Ryan Stone wrote:
> No, defining EM_WATCHDOG as 10 * hz should mean that the watchdog
> expires after 10 seconds no matter what your kern.hz is. hz is set to
> the number of ticks in a second.
Ok, one more probably wild punt .. Shtorm you say HZ=4000, giving:
===
And here
On Sat, 10 Jul 2010, Ian Smith wrote:
>
> HZ=4000 ticks are 250ns, not 25ms.
Up way too late .. that's 250us of course, thanks Ryan.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send an
On Fri, Jul 9, 2010 at 12:05 PM, Ian Smith wrote:
> On Sat, 10 Jul 2010, Ian Smith wrote:
> >
> > HZ=4000 ticks are 250ns, not 25ms.
>
> Up way too late .. that's 250us of course, thanks Ryan.
>
Even so, very good points Ian, thanks.
Hmmm, wondering if this points to a design flaw in what I
d
On (09/07/2010 18:10), Paul Miseiko wrote:
> The following reply was made to PR misc/148463; it has been noted by GNATS.
>
> From: Paul Miseiko
> To: "bug-follo...@freebsd.org" ,
> "pmise...@gmail.com"
> Cc:
> Subject: Re: misc/148463: [arp] ARP cache can be poisoned or polluted with
>
27 matches
Mail list logo
