Intel 82551

2002-10-02 Thread Eugene Vigovskiy
Hello. I wonder if FreeBSD supports Intel 82551 NICs. Eugene Vigovskiy R&D Department To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message

Q about sbin/ipfw2.c:list()

2002-10-02 Thread Andrey Simonenko
Hello, Why is it needed to check both r->rulenum and (void *)r < lim in sbin/ipfw2.c:list() ? /* * Count static rules. They have variable size so we * need to scan the list to count them. */ for (nstat = 1, r = data, lim = data + nbytes;

Re: Q about sbin/ipfw2.c:list()

2002-10-02 Thread Luigi Rizzo
On Wed, Oct 02, 2002 at 02:15:42PM +0300, Andrey Simonenko wrote: > Hello, > > Why is it needed to check both r->rulenum and (void *)r < lim in > sbin/ipfw2.c:list() ? because the buffer has a limited size (nbytes) and you don't want to read past it. However there is a bug in the code below, bec

Re: New natd available

2002-10-02 Thread Luigi Rizzo
On Tue, Oct 01, 2002 at 09:50:23AM -0700, Lars Eggert wrote: > Andre Oppermann wrote: > > > > In the FreeBSD May-June 2002 Status Report we have announced a natd > > rewrite to make it's configuration options more powerful and support > > more ip addresses to nat to. > > I haven't had time to lo

Re: Intel PRO/100 S

2002-10-02 Thread Bruce M Simpson
On Tue, Oct 01, 2002 at 06:33:13PM +0200, Marc Ernst Eddy van Woerkom wrote: > As far as I can tell from a bit of Google > research, it features hardware encryprtion/decryption. Check the BGA ASIC. If it's an 82550EY or 82550GY, it should be crypto capable. The 82559ED may also be crypto capable.

Re: Intel PRO/100 S

2002-10-02 Thread Attila Nagy
Hello, > > - Can I make use of that hardware acceleration? > Not yet. It relies on as-yet undocumented hardware registers and TCB > formats which Intel will not release documentation for without signing > an NDA. Just a stupid question: couldn't pdeuskar@ help on this topic? Or is it all about th

Re: Q about sbin/ipfw2.c:list()

2002-10-02 Thread Barney Wolff
Hmmm. In ipfw1 there is always a rule 65535, unless I'm confused. Is that not true of ipfw2? In either case, should it or should it not be counted? Can it ever be deleted? Can one have multiple rules with the same number, as one can with ipfw1? What happens if there are multiple rules with nu

Re: non-transparent IPsec via a tun interface?

2002-10-02 Thread Guido van Rooij
On Tue, Oct 01, 2002 at 06:34:29AM -0700, Julian Elischer wrote: > I have done similar to this using teh GIF interface. > > Each tunnel between sites had a gif interface and I firewalled > for only ESP packets to and from the correct machines on the external > interface, and for correct packets f

NFS client code calls sosend() directly...

2002-10-02 Thread Robert Watson
I was groping around through the socket code today looking for more places to sprinkle mandatory access control magic, and noticed that in most parts of the system call and protocol-independent socket implementation, sosend() is never invoked directly: instead, pru_sosend() is invoked, and protoc

Re: NFS client code calls sosend() directly...

2002-10-02 Thread Robert Watson
While I was reviewing the rest of the kernel tree, I also found... /cboss/p4/rwatson/trustedbsd/mac/sys/fs/fifofs/fifo_vnops.c: error = sosend(wso, (struct sockaddr *)0, ap->a_uio, 0, /cboss/p4/rwatson/trustedbsd/mac/sys/fs/portalfs/portal_vnops.c: error = sosend(so, (struct so

Re: Q about sbin/ipfw2.c:list()

2002-10-02 Thread Andrey Simonenko
On Wed, 2 Oct 2002, Barney Wolff wrote: > Hmmm. In ipfw1 there is always a rule 65535, unless I'm confused. > Is that not true of ipfw2? In either case, should it or should it > not be counted? Can it ever be deleted? Can one have multiple > rules with the same number, as one can with ipfw1

NFS client code calls sosend() directly...

2002-10-02 Thread Garrett Wollman
< said: > protocols have the option of implementing pru_sosend() using the central > sosend(), or providing their own optimized implementation. However, the > exception to this appears to be in the nfsclient code, where sosend is > invoked directly on the socket: The NFS code is hairy and evil

Re: NFS client code calls sosend() directly...

2002-10-02 Thread Robert Watson
On Wed, 2 Oct 2002, Garrett Wollman wrote: > < said: > > > protocols have the option of implementing pru_sosend() using the central > > sosend(), or providing their own optimized implementation. However, the > > exception to this appears to be in the nfsclient code, where sosend is > > invoked

multicast ftp?

2002-10-02 Thread shubha mr
Does freeBSD support ftp for a multicast address? Thanks shubha __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: Token Ring - Ethernet bridge

2002-10-02 Thread Gianmarco Giovannelli
At 16/09/2002, you wrote: >uhh... wakeup(&me->ibm_4.3bsd) > >What are people using for token-ring now a days? I have a box which acts as firewall with ipfw and dummynet on a public company that still uses token ring for its intranet. oltr0: port 0xd000-0xd03f irq 10 at device 10.0 on pci0 olt