Welcome to netgraph.. I hope it was not an unpleasant experience..
Suggestions and complaints are definitly eccepted with pleasure.
E.g. Was the differnce between 4.x and 5.x too much of a pain.?
(it was needed for SMP)
I will be making a backport of SOME of the added functionality
of 5.x to 4.x
** Reply to note from Clark Gaylord <[EMAIL PROTECTED]> Thu, 8 Feb 2001 12:46:06 -0500
> It used to be the case that mediaopt half-duplex worked. It stopped
> working at some point (I don't recall exactly when ... somewhere
> between 4.0 and 4.2 I think),
So this IS a bug.
> but
Are the following ipfw lines sufficent to allow pptp?:
${fwcmd} add pass tcp from any to any established
${fwcmd} add pass tcp from any to ${EXT_IF} pptp setup
${fwcmd} add pass gre from any to any
Comments/suggestions?
Regards
+--
Dan Larsson | Tel: +46 8 550 120 21
Tyfon Svenska AB
Hi,
I am looking for the syntaxe to configure an ethernet interface as
fullduplex.
If it is just by "ifconfig", I just know the beginning:
ifconfig -fxp0="inet... netmask ... broadcast... media ???"
Thanks,
JC.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net
Garrett Wollman wrote:
>
> < said:
>
> > it occurs to me that there is a potential infinite loop in
> > most if not all ethernet drivers. Basically, on a
> > receive interrupt, such drivers loop around the status word
> > until the receive queue is drained.
>
> One possible right way to deal wi
Hello:
Has anyone considered doing a SCTP stack
implementation for FreeBSD? I have a
user space version working.. but before
I start doing one for the kernel space.. just
curious? Don't want to duplicate anyones efforts..
R
--
Randall R. Stewart
[EMAIL PROTECTED] or [EMAIL PROTECTED]
815-342-52
> it occurs to me that there is a potential infinite loop in
> most if not all ethernet drivers. Basically, on a
> receive interrupt, such drivers loop around the status word
> until the receive queue is drained.
>
> If the body of the loop takes approx the same as
> the packet interarrival time,
Aloha,
I think you need to do an ifconfig -a on your system, and
use the media and/or mediaopt option of ifconfig. My system at
home has a de0 interface, and as I recall the parameters are
slightly different from those shown below...
server# ifconfig pn0 media 100baseTX mediaopt full-dupl
On Fri, 9 Feb 2001, Jean-Christophe Varaillon wrote:
> Hi,
Hello.
>
> I am looking for the syntaxe to configure an ethernet interface as
> fullduplex.
>
> If it is just by "ifconfig", I just know the beginning:
>
> ifconfig -fxp0="inet... netmask ... broadcast... media ???"
Just to follow up for everyone on my e-mail of last night, I ran my
bridge download test overnight (to check out Luigi's packet length
patch in if_ed.c), and it ran fine, with no crashes.
I did get about 70 "invalid packet length" incidents overnight (with
abnormally short packets of length 10, 1
On Fri, Feb 09, 2001 at 12:27:53PM +, Jean-Christophe Varaillon wrote:
> I am looking for the syntaxe to configure an ethernet interface as
> fullduplex.
Try this:
ifconfig fxp0 media 100baseTX mediaopt full-duplex
--
Hroi Sigurdsson [EMAIL PROTECTED]
Netgroup A
< said:
> This is similar to the way most VxWorks network drivers operate:
Right -- in fact, as I recall, Mogul's paper mentions that his
solution is very similar to the way many RTOSes operate.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the
In the last episode (Feb 08), Chris Dillon said:
> > The channel bonding is done using the Cisco fast etherchannel
> > mechanism. The default hashing mechanism uses the MAC address,
> > however you can select IP address hashing as well. IPv4 and IPv6
> > address *should* work, though I must admit
> I've just finished scouring Cisco's documentation, and it doesn't look
> like FEC is anything beyond plain old trunking (with the option of
> autoconfiguration on some hardware). As long as you configure the
> appropriate ports on the switch on the other end as "SA-Trunk", or
> "Trunk", you sho
I'd like to see this in 2.2.x, any objections?
Index: sys/sys/socket.h
===
RCS file: /home/ncvs/src/sys/sys/socket.h,v
retrieving revision 1.15.2.1
diff -u -u -r1.15.2.1 socket.h
--- sys/sys/socket.h1999/09/05 08:22:55 1.15.2
On Fri, 9 Feb 2001, Dan Nelson wrote:
> In the last episode (Feb 08), Chris Dillon said:
> > > The channel bonding is done using the Cisco fast etherchannel
> > > mechanism. The default hashing mechanism uses the MAC address,
> > > however you can select IP address hashing as well. IPv4 and IPv6
On Fri, 9 Feb 2001, Chris Dillon wrote:
> On Fri, 9 Feb 2001, Dan Nelson wrote:
> Cool, if thats all it will take, I'll give it a try. But, whatever
> method Compaq/Intel is using doesn't require me to set up the ports on
> the switch as being part of a trunk. It "just works". And IIRC, when
In article [EMAIL PROTECTED]> you write:
>Hello:
>
>Has anyone considered doing a SCTP stack
>implementation for FreeBSD? I have a
>user space version working.. but before
>I start doing one for the kernel space.. just
>curious? Don't want to duplicate anyones efforts..
I think that Jonathan Misc
The crock in these trunking schemes is all the trouble and effort expended
to avoid re-ordering frames across the trunk bundle. This is why you
see things like the hashing techniques so that an individual flow of
traffic doesn't get reordered because it always is serialized over the
a single pat
On Fri, 9 Feb 2001, Alex Pilosov wrote:
> On Fri, 9 Feb 2001, Chris Dillon wrote:
>
> > Cool, if thats all it will take, I'll give it a try. But, whatever
> > method Compaq/Intel is using doesn't require me to set up the ports on
> > the switch as being part of a trunk. It "just works". And II
> On Fri, 9 Feb 2001, Chris Dillon wrote:
>
> > On Fri, 9 Feb 2001, Dan Nelson wrote:
>
> > Cool, if thats all it will take, I'll give it a try. But, whatever
> > method Compaq/Intel is using doesn't require me to set up the ports on
> > the switch as being part of a trunk. It "just works". A
> "Chris" == Chris Dillon <[EMAIL PROTECTED]> writes:
>> Its not real trunking. Your incoming traffic will still come on
>> a single link, only outbound traffic will be shared. (Or at
>> least that's how I think compaq stuff will work).
Chris> Yes, I think that is how it work
Sorry, my brain's fried this afternoon.
< u_int64_t mask = ~0 & (n-1);/* mask for iftab index */
> u_int64_t mask = n-1; /* mask for iftab index */
--lyndon
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
In article [EMAIL PROTECTED]> you
write:
>
>I would be grateful if someone could test the attached patch which
>deals with the following problem:
>
> on all *BSD version, socket buffers contain a list of
> incoming and/or outgoing mbufs. Unfortunately the list only
> has a point
Jonathan:
I know Taz quite well.. in fact I got their team
started working on a Linux version of SCTP.
I think if no volunteers spring forth other
than Taz and co on the linux side.. I think
I will start the effort.. I am already digging
in to the ole an driver ... I think I can
move up the stac
Thanks for the feedback...
there is another (performance) problem in my code, actually:
with TCP, or non-datagram sockets, the socket buffer usually
contains a single record, so that sbappend would still have to
scan the chain m->m_next . An additional tail pointer would
be needed to avoid that o
On 8 Feb 2001 09:32:34 -0500, in sentex.lists.freebsd.net you wrote:
>Hello.
>I'd like to share some thought on what happened to me: I had an external ADSL modem
>from
>Alcatel connected (with a straight cable, since the device has a reversed ethernet
>port) to
>a RealTek card on a FreeB
27 matches
Mail list logo
