Hi Andre, did some careful testing yesterday and last night. I seem to
be still hitting an unknown buffer although the probem is much alleviated.
The system achieved a 7hour run at 500mbit where ETIMEDOUT occured. I
was feeding 11 other streams to the server whos counters show an
uninterrupted
Alexander Motin wrote:
Oleksandr Samoylyk wrote:
Julian Elischer wrote:
this may be the issue:
http://www.nabble.com/GRE-Mux-td16201899.html
I think so. Should we hope for some progress in this direction in future?
This is not an issue any more for mpd.
Originally multiplexing based on p
Oleksandr Samoylyk wrote:
Alexander Motin wrote:
Oleksandr Samoylyk wrote:
Julian Elischer wrote:
this may be the issue:
http://www.nabble.com/GRE-Mux-td16201899.html
I think so. Should we hope for some progress in this direction in
future?
This is not an issue any more for mpd.
Origin
Alexander Motin wrote:
Oleksandr Samoylyk wrote:
Alexander Motin wrote:
Oleksandr Samoylyk wrote:
Julian Elischer wrote:
this may be the issue:
http://www.nabble.com/GRE-Mux-td16201899.html
I think so. Should we hope for some progress in this direction in
future?
This is not an issue
Oleksandr Samoylyk wrote:
Julian Elischer wrote:
this may be the issue:
http://www.nabble.com/GRE-Mux-td16201899.html
I think so. Should we hope for some progress in this direction in future?
This is not an issue any more for mpd.
Originally multiplexing based on peers addresses by socket
Alexander Motin wrote:
Try to rebuild mpd to be sure it uses this feature. Also you can check
this by observing the name of any ng_pptpgre hook used. If it is
"upper", then ng_pptpgre multiplexing is not used and if it is
"session_" then OK.
I can't even list all nodes.
# ngctl list
ng
Oleksandr Samoylyk wrote:
Alexander Motin wrote:
Try to rebuild mpd to be sure it uses this feature. Also you can check
this by observing the name of any ng_pptpgre hook used. If it is
"upper", then ng_pptpgre multiplexing is not used and if it is
"session_" then OK.
I can't even list al
Alexander Motin wrote:
Try to rebuild mpd to be sure it uses this feature. Also you can check
this by observing the name of any ng_pptpgre hook used. If it is
"upper", then ng_pptpgre multiplexing is not used and if it is
"session_" then OK.
# ngctl show mpd24375-L-237-lt:
Name: mpd
El día Saturday, May 10, 2008 a las 12:49:02AM +1000, Ian Smith escribió:
> > Stevens explains further more that client and server could handshake to
> > omit the constant flag (7e) and adress field (ff) and reduce the
> > protocol field (0021) to one byte (21), but in the above packages 'flag'
Oleksandr Samoylyk wrote:
# ngctl show mpd24375-L-237-lt:
Name: mpd24375-L-237-lt Type: tee ID: 0008e919 Num hooks: 2
Local hook Peer name Peer typePeer ID Peer hook
-- - ---- -
right
Alexander Motin wrote:
Oleksandr Samoylyk wrote:
# ngctl show mpd24375-L-237-lt:
Name: mpd24375-L-237-lt Type: tee ID: 0008e919 Num
hooks: 2
Local hook Peer name Peer typePeer ID Peer hook
-- - ---- -
On Sat, May 10, 2008 at 12:34 PM, Matthias Apitz <[EMAIL PROTECTED]> wrote:
> El día Saturday, May 10, 2008 a las 12:49:02AM +1000, Ian Smith escribió:
>
>> > Stevens explains further more that client and server could handshake to
>> > omit the constant flag (7e) and adress field (ff) and reduce
Oleksandr Samoylyk wrote:
Alexander Motin wrote:
Oleksandr Samoylyk wrote:
It's "upper". And I don't know why :(
The sources were updated before building new kernel on May, 5, 2008.
The mpd5 port was rebuilt and restarted just few hours ago.
Have you updated your world also?
No, just kernel
Alexander Motin wrote:
Oleksandr Samoylyk wrote:
Alexander Motin wrote:
Oleksandr Samoylyk wrote:
It's "upper". And I don't know why :(
The sources were updated before building new kernel on May, 5, 2008.
The mpd5 port was rebuilt and restarted just few hours ago.
Have you updated your world
Hi,
I have an if_bridge, thus:
bridge0: flags=8843 metric 0 mtu
1500
inet XX.XX.XXX.20 netmask 0xfff8 broadcast XX.XX.XXX.23
inet 192.168.1.30 netmask 0xff00 broadcast 192.168.1.255
On one side of the bridge is a layer 2 switch with clients of a mix of
addresses from
Old Synopsis: iwi periodically disassociates/assotiates
New Synopsis: [iwi] iwi periodically disassociates/associates [regression]
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Sat May 10 20:07:33 UTC 2008
Responsible-Changed-Why:
Alexander Motin wrote:
Oleksandr Samoylyk wrote:
Alexander Motin wrote:
Oleksandr Samoylyk wrote:
It's "upper". And I don't know why :(
The sources were updated before building new kernel on May, 5, 2008.
The mpd5 port was rebuilt and restarted just few hours ago.
Have you updated your world
17 matches
Mail list logo