I just made one of my 4.x remote servers inaccessible and just tested it on my
5.x laptop, and it does the same thing ... not sure if this is considered a
'desirable' effect, or a but ... but ... 'ifconfig -alias' will wipe
out all IPs on the device:
mobile# ifconfig -a
lo0: flags=8049 mtu 16
Karim Fodil-Lemelin wrote:
>
> Ok here is an example, just to make sure I understand:
>
> CLI1 : SERVER1 (first connection, option negociated, tuple hash
> created)
> CLI1 : SERVER1 (second connection, sending payload in first packet,
> using previously negotiated cookie)
> ...
> CL
Ok here is an example, just to make sure I understand:
CLI1 : SERVER1 (first connection, option negociated, tuple hash
created)
CLI1 : SERVER1 (second connection, sending payload in first packet,
using previously negotiated cookie)
...
CLI1 : SERVER1 ( nth connection, sending pa
Karim Fodil-Lemelin wrote:
>
> In the case where all connections go through the SATLINK and are
> splitted by proxies, it make sense to use this knowledge and not
> renegotiate cookies for every connections since we know there is only
> one path to the internet and that all SATLINK connections
In the case where all connections go through the SATLINK and are
splitted by proxies, it make sense to use this knowledge and not
renegotiate cookies for every connections since we know there is only
one path to the internet and that all SATLINK connections will support
(T/TCP or whatever na
Karim Fodil-Lemelin wrote:
>
> Now,
>
> I have a question. In our application which can be described as:
>
> Client > (Client Gateway) ---> SATLINK --> (Server Gateway)
> -> Internet
>
> We act as the Internet servers (transparent proxies) and therefore T/TCP
> traffic is on
Now,
I have a question. In our application which can be described as:
Client > (Client Gateway) ---> SATLINK --> (Server Gateway)
-> Internet
We act as the Internet servers (transparent proxies) and therefore T/TCP
traffic is only sent over the SATLINK. In the current T/TCP
i
Our product is a TCP/IP accelerator for satellite communications please
see http://www.xiplink.com/technology/xiplink_technology-datasheet.html.
Also, please see http://www.scps.org/scps/ for an explanation of our
Transport layer implementation. BTW, The marketing dep has renamed T/TCP
to fast
xl0: transmission error: 90
xl0: tx underrun, increasing tx start threshold to 120 bytes
xl0: watchdog timeout
xl0: transmission error: 90
xl0: tx underrun, increasing tx start threshold to 120 bytes
How do I reset things like this (and the anti-flood protection
too)?
--
Matt Sealey <[EMAIL PRO
