https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184149
Craig Rodrigues changed:
What|Removed |Added
CC||rodr...@freebsd.org
As
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191468
Craig Rodrigues changed:
What|Removed |Added
CC||rodr...@freebsd.org
As
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164763
Craig Rodrigues changed:
What|Removed |Added
CC||rodr...@freebsd.org
As
On 10/17/14, 1:43 PM, vijju.singh wrote:
We've seen issues with vnet delete causing stale pointers in mbufs referencing
the per-vnet loopback interface (deleted with the vnet).
you can also see this sort of problem with removable devices. e.g. USB
network interfaces, so it's not unique to vnet.
We've seen issues with vnet delete causing stale pointers in mbufs referencing
the per-vnet loopback interface (deleted with the vnet).
Sent via the Samsung GALAXY S®4, an AT&T 4G LTE smartphone
Original message From: Dag-Erling Smørgrav
Date:10/16/2014 10:39 AM (GMT-08:00)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194314
--- Comment #9 from Eric Joyner ---
You could try replacing the two lines in ixgbe.h with these:
#define IXGBE_RX_COPY_HDR (sizeof(struct m_hdr) + sizeof(struct pkthdr))
#define IXGBE_RX_COPY_HDR_PADDED IXGBE_RX_COPY_HDR - 1) / 3
On Sat, Oct 11, 2014 at 11:15 PM, Adrian Chadd wrote:
> ... is it enabled by default on pcbsd?
>
Kris has answered the question about pcbsd and VIMAGE.
As an additional datapoint, I would like to point out that VIMAGE
has been enabled in FreeNAS for some time:
https://github.com/freenas/freena
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194314
--- Comment #8 from Eric Joyner ---
So it sounds like we may just need to change IXGBE_RX_COPY_LEN from a fixed
value of 160 to something that's calculated based on the length of struct m_hdr
and struct m_pkthdr combined.
I think they got
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194314
--- Comment #7 from Garrett Cooper ---
(In reply to Eric Joyner from comment #6)
> Does that mean only the sizes of struct m_hdr and struct m_pkthdr change, or
> do you change MSIZE as well?
The size of struct m_ext and struct m_hdr is lar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194314
--- Comment #6 from Eric Joyner ---
Does that mean only the sizes of struct m_hdr and struct m_pkthdr change, or do
you change MSIZE as well?
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194234
Eric Joyner changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #2 from
On Saturday, October 11, 2014 2:19:19 am Jason Wolfe wrote:
> On Fri, Oct 10, 2014 at 8:53 AM, John Baldwin wrote:
>
> > On Thursday, October 09, 2014 02:31:32 PM Jason Wolfe wrote:
> > > On Wed, Oct 8, 2014 at 12:29 PM, John Baldwin wrote:
> > > > My only other thought is if a direct timeout ro
--- Original message ---
From: "Dag-Erling Smørgrav"
Date: 16 October 2014, 20:39:22
> "Bjoern A. Zeeb" writes:
> > Dag-Erling Smørgrav writes:
> > > There are other serious issues with our current pf (checksum
> > > corruption) which I think can only be resolved by importing a newer
"Bjoern A. Zeeb" writes:
> Dag-Erling Smørgrav writes:
> > There are other serious issues with our current pf (checksum
> > corruption) which I think can only be resolved by importing a newer
> > version.
> Sorry, but you lost context. I was talking about security
> implications in VIMAGE contex
On Sat, Oct 11, 2014 at 10:58 AM, Craig Rodrigues
wrote:
> Hi,
>
> What action items are left to enable VIMAGE by default for FreeBSD 11?
>
> Not everyone uses bhyve, so VIMAGE is quite useful when using jails.
>
>
Based on the discussion in this thread, I started writing down
a list of action i
On 16 Oct 2014, at 08:52 , Dag-Erling Smørgrav wrote:
> "Bjoern A. Zeeb" writes:
>> Also if people are seriously thinking about virtualising pf we need to
>> import the openbsd/apple pf fix from a few years ago because otherwise
>> people in virtualised stacks with a /dev/pf can do ugly things.
Hi Freddie,
I have tested on 10.1-RC2 and I’m seeing exactly the same issue. I am running a
Windows 8.1 machine with a 10.1-RC2 i386 VM in Virtualbox, configured to bridge
to my Intel network adapter. (I’d rather use amd64 but unfortunately it appears
that although my OS is 64bit, it’s old hard
ifconfig_em0="up"
ifconfig_em0="vhid 10 pass mypass 192.168.0.100/24"
The problem with that is that rc.conf is basically just a list of variables, so
the second ifconfig_em0 entry will overwrite the first one.
I'm not too bothered about my 'up' problem at the moment. I actually have no
current
FreeBSD 9 and FreeBSD 10 have very different implementations of CARP, and
they are configured differently.
On 9, you need to have an IP configured on the interface before you
configure the shared IP, and the subnet of the shared IP is used to
determine the interface to use. And there's carpX pseud
Hi Matt
thanks a lot for the help!
Unfortunately the Forum was down before I could read the replies. But
what you said makes sense and now it is clearly for me.
The new Setup is working great and now the routing table looks good. I
also identified my mistake on the test machine and now I knew
"Bjoern A. Zeeb" writes:
> Also if people are seriously thinking about virtualising pf we need to
> import the openbsd/apple pf fix from a few years ago because otherwise
> people in virtualised stacks with a /dev/pf can do ugly things. I
> think it’s been this one:
> http://cve.mitre.org/cgi-bin
HI Sascha,
This example is wrong:
ifconfig_em0="inet vhid 10 pass mypass alias 192.168.0.100/32"
As discussed in the forum (not sure if you saw the last couple of messages
before forum was taken down), if the carp address is the primary address on the
interface, it needs to use the real mask.
Hi Matt,
I think I'm the user you try to help in the forum ;-).
I had the same problem like you when doing the first tests with carp.
The alias must be a /32 as subnet declaration. I didn't read properly
the examples in the manual and Handbook. So I configured CARP as usual
in FreeBSD 9. The
23 matches
Mail list logo
