Re: Dingo and PerForce

2004-12-19 Thread Maxim Konovalov
On Mon, 20 Dec 2004, 16:01+1030, Wilkinson, Alex wrote: > 0n Sun, Dec 19, 2004 at 02:50:09PM +0100, Andre Oppermann wrote: > > >> now a dingo branch, named "dingo". The dingo branch contains > >> all of src, not just sys, as I suspect there are userland bits > >>

Re: Dingo and PerForce

2004-12-19 Thread Wilkinson, Alex
0n Sun, Dec 19, 2004 at 02:50:09PM +0100, Andre Oppermann wrote: >> now a dingo branch, named "dingo". The dingo branch contains >> all of src, not just sys, as I suspect there are userland bits >> we'll want to do. I know I'll be doing userland things.

Re: Dingo and PerForce

2004-12-19 Thread gnn
At Sun, 19 Dec 2004 12:32:27 -0500, Bosko Milekic wrote: > You develop in your individual branch, test your changes. If all is > well, you push into dingo, where changes get tested with respect to > other dingo-related changes (which have not yet been pushed into HEAD). > When it's all ready, ever

Re: vlan double tagging

2004-12-19 Thread Eric Brunner-Williams in Portland Maine
I'm still working on the problem. I'm waiting on a cert renewal that seems to have gotten stuck. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: vlan double tagging

2004-12-19 Thread James
On Sat, Dec 18, 2004 at 07:10:51PM +1030, Wilkinson, Alex wrote: > 0n Sat, Dec 18, 2004 at 03:16:27AM -0500, James wrote: > > > /me thinks he's asking for q-in-q tunneling feature. > > What is 'q-in-q tunneling' ? http://www.google.com/search?hl=en&q=q-in-q+tunneling -J -- Jam

Re: vlan double tagging

2004-12-19 Thread Wilkinson, Alex
0n Sat, Dec 18, 2004 at 03:16:27AM -0500, James wrote: > On Fri, Dec 17, 2004 at 03:03:49PM -0800, Mike Hunter wrote: > > On Dec 17, "Brooks Davis" wrote: > > > > > On Fri, Dec 17, 2004 at 01:22:02PM +0200, Donatas wrote: > > > > hello, > > > > i'd like to

Re: Marvell 88E8001 on sk0 and RELENG_5_3 - big problems

2004-12-19 Thread Bjoern A. Zeeb
On Sun, 19 Dec 2004, Heinz Knocke wrote: > > Index: sys/pci/if_sk.c > > (...) > > I tried this one and seems to work corectly :) Jumbograms were used, data > stream was smooth, > I haven't seen any error messages in system log. > In rough tests I had a little bit better speeds than with this one:

Re: Marvell 88E8001 on sk0 and RELENG_5_3 - big problems

2004-12-19 Thread Heinz Knocke
- Original Message - From: "Bjoern A. Zeeb" <[EMAIL PROTECTED]> To: "Heinz Knocke" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, December 16, 2004 2:45 PM Subject: Re: Marvell 88E8001 on sk0 and RELENG_5_3 - big problems > would you mind trying this patch. It should only a

Re: FW: Curiosity in IPFW/Freebsd bridge. [more] 802.1q VLAN at fault?

2004-12-19 Thread asegu
Ok, the whole discussion to date led to how VLAN traffic wasn't being registered by IPFW in my system. I think that it'll probably be too late for a code change to fix my problem, so I'm going to go the route of changing the network configuration. I've rebuilt to 4.10 and.. And I had no luck there

Re: Dingo and PerForce

2004-12-19 Thread Bosko Milekic
This way he can push changes back into 'dingo' before pushing them back into HEAD. It makes a lot of sense, actually, to do this sort of 3-tier approach when multiple people are working on different parts of a larger sub-project, like for example dingo. HEAD (top, must work) <-- (dingo, pre-prod

Re: Dingo and PerForce

2004-12-19 Thread Max Laier
On Sunday 19 December 2004 05:23, [EMAIL PROTECTED] wrote: > For those who use PerForce and want to work on Dingo there is > now a dingo branch, named "dingo". The dingo branch contains > all of src, not just sys, as I suspect there are userland bits > we'll want to do. I

Re: Dingo and PerForce

2004-12-19 Thread Andre Oppermann
[EMAIL PROTECTED] wrote: > > Howdy, > > For those who use PerForce and want to work on Dingo there is Did you update the Dingo project page with the stuff I sent you about three weeks ago? -- Andre > now a dingo branch, named "dingo". The dingo branch contains > all

Re: Alternate port randomization approaches

2004-12-19 Thread Maxim Konovalov
Hi Mike, On Sat, 18 Dec 2004, 04:03-0600, Mike Silbersack wrote: [...] > Although this isn't a perfect fix, I think that it should be > acceptable for the vast majority of systems, and I'd like to get it > in before 4.11-release ships. To be conservative, I'll probably > choose a value like 5, w