On Thu, Sep 13, 2012 at 11:29 PM, Вадим Уразаев wrote:
> I am using two lagg interfaces :
> lagg0: flags=8843 metric 0 mtu 1500
> options=400b8
> ether 00:1b:21:55:a7:c4
> nd6 options=9
> media: Ethernet autoselect
> status: active
> laggproto lacp
> laggport: igb1 flags=1c
> laggport: igb0 flags=
I am using two lagg interfaces :
lagg0: flags=8843 metric 0 mtu 1500
options=400b8
ether 00:1b:21:55:a7:c4
nd6 options=9
media: Ethernet autoselect
status: active
laggproto lacp
laggport: igb1 flags=1c
laggport: igb0 flags=1c
lagg1: flags=8843 metric 0 mtu 1500
options=400b8
ether 00:1b:21:63:59:c
On Fri, Sep 07, 2012 at 05:44:48PM -0400, Jeremiah Lott wrote:
> On Apr 27, 2012, at 2:07 AM, lini...@freebsd.org wrote:
>
> > Old Synopsis: sosend sometimes return EINVAL with TSO and VLAN on 82599 NIC
> > New Synopsis: [netinet] [patch] sosend sometimes return EINVAL with TSO and
> > VLAN on 82
On Thu, 13 Sep 2012 21:53:23 +0300, ? ??? wrote:
> Then my guess is wrong. I found the message, where similiar problem was
> described in ipfw mailling list
> http://lists.freebsd.org/pipermail/freebsd-ipfw/2011-March/004582.html, with
> no answer.
> Maybe it will be usefull for someb
On Thu, 13 Sep 2012, Glen Barber wrote:
On Thu, Sep 13, 2012 at 08:34:40AM -0700, Yuri wrote:
On 09/12/2012 20:01, Glen Barber wrote:
It would be helpful if you would at least try my cron(8) suggestion.
So I tried adding the lines into crontab:
@reboot root/sbin/kldload /boot/kernel/if_n
On Thu, Sep 13, 2012 at 11:31:25PM +0400, Gleb Smirnoff wrote:
> On Thu, Sep 13, 2012 at 07:41:05PM +0200, Luigi Rizzo wrote:
> L> Second:
> L>What i contest is the fact that you classify ipfw as a "pfil client",
> L>when pfil is just a tiny adaptation layer to access ipfw.
> L>I mentio
On 09/12/2012 10:51 PM, Freddie Cash wrote:
On Wed, Sep 12, 2012 at 1:48 PM, Jack Vogel wrote:
On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash wrote:
Thanks for checking. I've used lagg(4) with igb, just not on 9.x.
You're right, it seems to be pointing to the igb(4) driver in 9.x
compared t
On Thu, Sep 13, 2012 at 07:41:05PM +0200, Luigi Rizzo wrote:
L> Second:
L>What i contest is the fact that you classify ipfw as a "pfil client",
L>when pfil is just a tiny adaptation layer to access ipfw.
L>I mentioned the three alternative APIs (netmap, netfilter, ndis)
L>to witness
Then my guess is wrong. I found the message, where similiar problem was
described in ipfw mailling list
http://lists.freebsd.org/pipermail/freebsd-ipfw/2011-March/004582.html, with
no answer.
Maybe it will be usefull for somebody.
___
freebsd-net@freebsd
Hi,
Altough I'm using ipfw for traffic shaping, I'm not using it for NAT. I'm using
PF for NAT.
--
-Message d'origine-
De : owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@freebsd.org] De la
part de Adrian Chadd
Envoyé : 13 septembre 2012 13:04
À : Вадим Уразаев
Cc : freebsd
On Thu, Sep 13, 2012 at 04:36:10PM +, Bjoern A. Zeeb wrote:
> On Wed, 12 Sep 2012, Luigi Rizzo wrote:
>
> >On Wed, Sep 12, 2012 at 04:34:57PM +0400, Gleb Smirnoff wrote:
> >> Hi,
> >>
> >> we (me and Bjoern) would like to establish a single place
> >>for all kinds of pfil(9) consumers, for c
W dniu 2012-09-13 19:04, Adrian Chadd pisze:
On 13 September 2012 03:04, Вадим Уразаев wrote:
I have the same issue (default gateway unexpectedly changes on some random
address) on FreeBSD 9.0 Box with lot of traffic going through it, I have a
wild guess that it is related to libalias compille
On 13 September 2012 03:04, Вадим Уразаев wrote:
> I have the same issue (default gateway unexpectedly changes on some random
> address) on FreeBSD 9.0 Box with lot of traffic going through it, I have a
> wild guess that it is related to libalias compilled into kernel (troubles
> start showing it
On Thu, Sep 13, 2012 at 08:34:40AM -0700, Yuri wrote:
> On 09/12/2012 20:01, Glen Barber wrote:
> > It would be helpful if you would at least try my cron(8) suggestion.
>
> So I tried adding the lines into crontab:
> @reboot root/sbin/kldload /boot/kernel/if_ndis.ko >/dev/null 2>&1
> @reboot r
On Wed, 12 Sep 2012, Luigi Rizzo wrote:
On Wed, Sep 12, 2012 at 04:34:57PM +0400, Gleb Smirnoff wrote:
Hi,
we (me and Bjoern) would like to establish a single place
for all kinds of pfil(9) consumers, for current ones and
for future as well.
The place chosen is sys/netpfil.
On first
On 09/12/2012 20:01, Glen Barber wrote:
It would be helpful if you would at least try my cron(8) suggestion.
So I tried adding the lines into crontab:
@reboot root/sbin/kldload /boot/kernel/if_ndis.ko >/dev/null 2>&1
@reboot root/sbin/kldload /boot/modules/bcmwl5_sys.ko >/dev/null 2>&1
On Tuesday, September 11, 2012 4:00:21 pm Sean Bruno wrote:
> The following reply was made to PR kern/171524; it has been noted by GNATS.
>
> From: Sean Bruno
> To: bug-follo...@freebsd.org, dhoj...@brainbits.net
> Cc:
> Subject: Re: kern/171524: [ipmi] ipmi driver crashes kernel by reboot or
>
Old Synopsis: ndis(4) driver includes 'pccard'-specific code, even if 'device
pccard' absent from config
New Synopsis: [ndis] ndis(4) driver includes 'pccard'-specific code, even if
'device pccard' absent from config
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By:
I have the same issue (default gateway unexpectedly changes on some random
address) on FreeBSD 9.0 Box with lot of traffic going through it, I have a
wild guess that it is related to libalias compilled into kernel (troubles
start showing itself when I started to use ipfw nat functionality ).
19 matches
Mail list logo
