> > On 26. mai 2017, at 12:27, Andriy Gapon wrote:
> >
> > On 09/03/2017 08:01, Mariusz Zaborski wrote:
> >> Author: oshogbo
> >> Date: Thu Mar 9 06:01:24 2017
> >> New Revision: 314948
> >> URL: https://svnweb.freebsd.org/changeset/base/314948
> >>
> >> Log:
> >> Try to extract the RFC1048 da
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219428
--- Comment #2 from a...@neu.net ---
No need to look thru ML threads, I just mentioned that so there was more
reports than just mine. Not much to report, install CURRENT on a physical
machine with an Intel gigabit nic. DHCP and static addr
On Fri, May 26, 2017 at 12:27:45PM +0300, Andriy Gapon wrote:
> On 09/03/2017 08:01, Mariusz Zaborski wrote:
> > Author: oshogbo
> > Date: Thu Mar 9 06:01:24 2017
> > New Revision: 314948
> > URL: https://svnweb.freebsd.org/changeset/base/314948
> >
> > Log:
> > Try to extract the RFC1048 data
> On 26. mai 2017, at 12:27, Andriy Gapon wrote:
>
> On 09/03/2017 08:01, Mariusz Zaborski wrote:
>> Author: oshogbo
>> Date: Thu Mar 9 06:01:24 2017
>> New Revision: 314948
>> URL: https://svnweb.freebsd.org/changeset/base/314948
>>
>> Log:
>> Try to extract the RFC1048 data from PXE. If we
Bezüglich Vincenzo Maffione's Nachricht vom 26.05.2017 11:06 (localtime):
> Yes, it should integrate and compile out of the box, I've done that
> several times with FreeBSD-11.0 and 10.3.
Impressive, it needed just a small addition to sys/conf/files to make
the linker happy :-)
I also recomplied
On 09/03/2017 08:01, Mariusz Zaborski wrote:
> Author: oshogbo
> Date: Thu Mar 9 06:01:24 2017
> New Revision: 314948
> URL: https://svnweb.freebsd.org/changeset/base/314948
>
> Log:
> Try to extract the RFC1048 data from PXE. If we get enough info we can skip
> the bootp(). It removes unnece
On 25.05.2017 20:58, Harry Schmalzbauer wrote:
> thank you for your fix, which made it into stable/11 in the meantime,
> where I can confirm it does work.
>
> But I noticed a possibly related oddity:
> Setting "-vlanhwcsum" seems to have no effect, at least ifconfig(8)
> reports always 'VLAN_HWCSU
Yes, it should integrate and compile out of the box, I've done that several
times with FreeBSD-11.0 and 10.3.
And yes, HEAD contains recent code, you can also use that.
Cheers,
Vincenzo
2017-05-26 11:01 GMT+02:00 Harry Schmalzbauer :
> Bezüglich Vincenzo Maffione's Nachricht vom 26.05.2017 10:
Bezüglich Vincenzo Maffione's Nachricht vom 26.05.2017 10:41 (localtime):
> Ok, so you should try to completely replace the code in your
> /usr/src/sys with the code in the upstream netmap
> repository https://github.com/luigirizzo/netmap (sys directory).
Sorry beeing so complicated; But is there
Ok, so you should try to completely replace the code in your /usr/src/sys
with the code in the upstream netmap repository
https://github.com/luigirizzo/netmap (sys directory).
2017-05-26 10:38 GMT+02:00 Harry Schmalzbauer :
> Bezüglich Vincenzo Maffione's Nachricht vom 26.05.2017 09:31 (localtime
Bezüglich Vincenzo Maffione's Nachricht vom 26.05.2017 09:31 (localtime):
> Is lagg0 the only interface attached to vale0?
> Is lagg0 aggregating a VLAN interface?
>
> You can try this trivial patch
>
> diff --git a/sys/dev/netmap/netmap_generic.c
> b/sys/dev/netmap/netmap_generic.c
> index f148b
Bezüglich Vincenzo Maffione's Nachricht vom 26.05.2017 09:31 (localtime):
> Is lagg0 the only interface attached to vale0?
Yes.
> Is lagg0 aggregating a VLAN interface?
No.
> You can try this trivial patch
>
> diff --git a/sys/dev/netmap/netmap_generic.c
> b/sys/dev/netmap/netmap_generic.c
>
Is lagg0 the only interface attached to vale0?
Is lagg0 aggregating a VLAN interface?
You can try this trivial patch
diff --git a/sys/dev/netmap/netmap_generic.c
b/sys/dev/netmap/netmap_generic.c
index f148b228..46a3c2c6 100644
--- a/sys/dev/netmap/netmap_generic.c
+++ b/sys/dev/netmap/netmap_gen
Bezüglich Vincenzo Maffione's Nachricht vom 26.05.2017 09:14 (localtime):
> Hi,
> Your stack trace report this:
>
> #7 0x8069dc50 at vlan_input+0x1f0
>
> which means VLANs are involved, in some way. Is that the correct trace?
The trace is from the pnaic after doing 'vale-ctl -a vale0:l
Hi,
Your stack trace report this:
#7 0x8069dc50 at vlan_input+0x1f0
which means VLANs are involved, in some way. Is that the correct trace?
Cheers,
VIncenzo
2017-05-26 9:12 GMT+02:00 Harry Schmalzbauer :
> Bezüglich Vincenzo Maffione's Nachricht vom 25.05.2017 22:57 (localtime):
>
Bezüglich Vincenzo Maffione's Nachricht vom 25.05.2017 22:57 (localtime):
> No, the thing is that I misinterpreted your stack trace. The patch is ok
> for a different bug. It seems that the problem are vlans more than lagg.
> Which interface did you put in netmap mode, em or em.345?
Good morning,
16 matches
Mail list logo