> I believe you're misunderstanding the meaning of the timeout in select(2).
> Timeout applies only when no FDs are ready.
The specific problem with bpf is that one might have a half-full buffer
of captured data when the select timeout hits. In that case the select
returns with no FDs ready whil
Hello,
I'm using FreeBSD for routing and shaping in my company.
Now, I have a problem: each time the pipe queue is full, the router sends : ICMP:
Source quench.
Please, help me to disable this message.
Looking forward to your reply,
Vladimir Girnet
"MEGADAT.COM" S.R.L.
MOLDOVA, Chisinau
www.
Hi list;
i read NG manual and i cannot get something :
1. is NG just for FreeBSD nodes connection
2. is NG for p2p connection
3. can i use 2 Nodes like this ...
LAN ---TCP/IP---NG1---NG connection--NG2---TCP/IP-WAN
lan doesn't have the ng run on it and also WAN but between 2 ng-nodes i can
HI net'ers !!
i read some message on the list archive and someone says that we can use
spoofing with ng
how can i do spooging with ng like this ???
WAN --- spoofer ( one ng node ) --- lan
THANX
_
The new MSN 8: advanced ju
On Tue, 5 Nov 2002, Archie Cobbs wrote:
> Iasen Kostov writes:
> > As I experience system crushes at time of mbufs exhaustion I've compiled
> > a debug kernel and traced the problem. I seems the NFS functions
> > (nfsm_rpchead, nfsm_reqh ...) does *NOT* chek if they really have
> > allocated m
: 1) Device driver in Netgraph node. When hardware is
:activated new Netgraph node is created and new
:kevent sent. devd (or something like devd) listens
:for these events and does something (loads firmware,
:activates device, etc.)
Device drivers are not netgraph nodes. They will
On Wed, 6 Nov 2002, Iasen Kostov wrote:
IK>
IK>
IK>On Tue, 5 Nov 2002, Archie Cobbs wrote:
IK>
IK>> Iasen Kostov writes:
IK>> > As I experience system crushes at time of mbufs exhaustion I've compiled
IK>> > a debug kernel and traced the problem. I seems the NFS functions
IK>> > (nfsm_rpchead, n
On Tue, Nov 05, 2002 at 09:05:47PM +0300, Anton Vinokurov wrote:
> Hi!
>
> I am running FreeBSD 4.7-release and try to use ATEN UC10T USB-to-Ethernet
> adapter. Unfortunately it causes my system to print something like:
> kue0: watchdog timeout
> kue0: usb error on tx: TIMEOUT
> following by freez
> I believe the select operation on bpf is not functioning as supposed to.
> I'm calling select with 100ms timeout. The bpf interface is listening to
> an interface with constant packet rate, so it's certain that multiple
> packets have been received during the select call. However the fd for
On Wed, Nov 06, 2002 at 10:03:06AM +0200, Petri Helenius wrote:
>
> The specific problem with bpf is that one might have a half-full buffer
> of captured data when the select timeout hits. In that case the select
> returns with no FDs ready while I think it really should return with
> the bpf fd.
Harti Brandt writes:
> IK>> > As I experience system crushes at time of mbufs exhaustion I've compiled
> IK>> > a debug kernel and traced the problem. I seems the NFS functions
> IK>> > (nfsm_rpchead, nfsm_reqh ...) does *NOT* chek if they really have
> IK>> > allocated memory by MGET macro.
> IK
In message <[EMAIL PROTECTED]>, Archie Cobbs wri
tes:
>Oops, you're right.. sorry for the misinformation.
>
>Sounds like a bug to me (did Iasen file a PR?)
kern/38872 already exists, and I'm sure there is a much older PR
that also describes this problem. Basically it is hard to fix because
the err
Hi,
> On Tue, 5 Nov 2002 17:00:40 -0800
> Maxime Henrion <[EMAIL PROTECTED]> said:
mux>ipv6_enable="YES"
mux>ipv6_defaultrouter="2002:c058:6301::" # Use this for 6to4 (RFC 3068)
mux>ipv6_prefix_xl1="2002:5143:8351:"
mux>stf_interface_ipv4addr="81.67.131.81"
It seems you
Hajimu UMEMOTO wrote:
> Hi,
>
> > On Tue, 5 Nov 2002 17:00:40 -0800
> > Maxime Henrion <[EMAIL PROTECTED]> said:
>
> mux> ipv6_enable="YES"
> mux> ipv6_defaultrouter="2002:c058:6301::" # Use this for 6to4 (RFC 3068)
> mux> ipv6_prefix_xl1="2002:5143:8351:"
> mux> stf_interface_ipv4ad
On Wed, 6 Nov 2002, Ian Dowse wrote:
> In message <[EMAIL PROTECTED]>, Archie Cobbs wri
> tes:
> >Oops, you're right.. sorry for the misinformation.
> >
> >Sounds like a bug to me (did Iasen file a PR?)
>
> kern/38872 already exists, and I'm sure there is a much older PR
> that also describes th
On Wed, 6 Nov 2002, M. Warner Losh wrote:
> : 1) Device driver in Netgraph node. When hardware is
> :activated new Netgraph node is created and new
> :kevent sent. devd (or something like devd) listens
> :for these events and does something (loads firmware,
> :activates device, e
Andrea Venturoli wrote:
> I don't really understand the reason why either the modem or the serial port would
>change their setting spontaneously.
You are right. They don't.
> Let's deal with the serial port: it's initialized at boot time by rc.serial, so a
>reboot should have set it up right.
>
Hi,
> On Wed, 6 Nov 2002 09:25:34 -0800
> Maxime Henrion <[EMAIL PROTECTED]> said:
mux> However, it still doesn't seem to work properly. When pinging an IPv6
mux> host from a box in my local subnet, I'm getting this warning on the box
mux> running rtadvd(8) :
mux> cannot forward src fe8
Hajimu UMEMOTO wrote:
> Hi,
>
> > On Wed, 6 Nov 2002 09:25:34 -0800
> > Maxime Henrion <[EMAIL PROTECTED]> said:
>
> mux> However, it still doesn't seem to work properly. When pinging an IPv6
> mux> host from a box in my local subnet, I'm getting this warning on the box
> mux> running rt
Hi,
> On Wed, 6 Nov 2002 10:20:30 -0800
> Maxime Henrion <[EMAIL PROTECTED]> said:
mux> Well, my interface which is connected to the net is xl1. The interface
mux> connected to the local subnet is xl0. If I change rtadvd_interfaces to
mux> xl1, ping6 on the box behind the router gets a
Hajimu UMEMOTO wrote:
> Hi,
> mux> Well, my interface which is connected to the net is xl1. The interface
> mux> connected to the local subnet is xl0. If I change rtadvd_interfaces to
> mux> xl1, ping6 on the box behind the router gets a no route to host while
> mux> the DNS lookup worked before,
Hi,
> On Wed, 6 Nov 2002 11:02:28 -0800
> Maxime Henrion <[EMAIL PROTECTED]> said:
mux> Sorry to ask you about this again, but I have no idea what to set as a
mux> prefix for xl0. Does 2002:5143:8351:2 sounds sane? The prefix for xl1
mux> is 2002:5143:8351:1 as you suggested.
Yes.
--
In message: <[EMAIL PROTECTED]>
Julian Elischer <[EMAIL PROTECTED]> writes:
:
:
: On Wed, 6 Nov 2002, M. Warner Losh wrote:
:
: > : 1) Device driver in Netgraph node. When hardware is
: > :activated new Netgraph node is created and new
: > :kevent sent. devd (or something lik
On Wed, 6 Nov 2002, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Julian Elischer <[EMAIL PROTECTED]> writes:
> :
> :
> : On Wed, 6 Nov 2002, M. Warner Losh wrote:
> :
> : > : 1) Device driver in Netgraph node. When hardware is
> : > :activated new Netgraph node is
On Wed, Nov 06, 2002 at 12:48:07PM -0800, Julian Elischer wrote:
>
> Ok but there cound be netgraph nodes that have no hardware but could be
> called into creation by some external event.
> e.g. a netgraph hook on a pseudointerface like gif or tun.
> (not at present but a possibility I was looking
In message: <[EMAIL PROTECTED]>
Julian Elischer <[EMAIL PROTECTED]> writes:
: Ok but there cound be netgraph nodes that have no hardware but could be
: called into creation by some external event.
: e.g. a netgraph hook on a pseudointerface like gif or tun.
: (not at present but a possi
26 matches
Mail list logo
