SUN Solaris by MaMe

: "nicstat - print network traffic, Kb/s read and written. Solaris 8 . * 'netstat -i' only gives a packet count, this program gives Kbytes."

Free Shell Accounts: "The biggest Free Shell list on the net"

Proxy-World: "Bei einem Proxyservern handelt es sich gew�hnlich um einen zwischen Internet und LAN geschalteten Rechner mit Proxyserver (Software). Ein Proxy vermittelt bzw. leitet Datenstr�me weiter. Ein Anwender startet seine Anfrage (Request) an den Proxy, dieser leitet die Anfrage an den eigentlichen Zielserver weiter. Der Zielserver antwortet dem Proxy (Response) und dieser leitet die Antwort wieder an den Anwender.

Durch ein mehrfaches Hintereinanderschalten von Proxyservern, �ber die der User auf den wirklichen Zielhost zugreift wird die Sicherheit und Anonymit�t stark erh�ht. Durch diese Art der Anonymisierung k�nnen die meisten Webverbindungen realisiert werden.Ein Nachteil ist jedoch die Geschwindigkeitsbeeintr�chtigung auf Grund der zwischen geschalteten Proxys."

SixXS - IPv6 Deployment & Tunnel Broker :: Anything In Anything (AYIYA): "Anything In Anything"

Many users are currently located behind NATs which prohibit the usage of proto-41 IPv6 in IPv4 tunnels [RFC3056] unless they manually reconfigure their NAT setup which in some cases is impossible as the NAT cannot be configured to forward proto-41 ([RFC1933]) to a specific host. There might also be cases when multiple endpoints are behind the same NAT, when multiple NATs are used or when the user has no control at all over the NAT setup. This is an undesired situation as it limits the deployment of IPv6 [RFC3513], which was meant to solve the problem of the disturbance in end to end communications caused by NATs, which where created because of limited address space in the first place.

This problem can be solved easily by tunneling the IPv6 packets over either UDP [RFC0768], TCP [RFC0793] or even SCTP [RFC2960]. Taking into consideration that multiple separate endpoints could be behind the same NAT and/or that the public endpoint can change on the fly, there is also a need to identify the endpoint that certain packets are coming from and endpoints need to be able to change e.g. source addresses of the transporting protocol on the fly while still being identifiable as the same endpoint. The protocol described in this document is independent of the transport and payload's protocol. An example could be IPv6-in-UDP-in-IPv4, which is a typical setup that can be used by IPv6 Tunnel Brokers [RFC3053].

This document does not describe how to determine the identity, signature type or the inner and outer protocols. These should be negotiated manually or automatically by e.g. using TSP or a relevant protocol which is capable of describing the configuration parameters of AYIYA tunnels. Separate documents for the configuration protocols supporting AYIYA should include the details on how this is done.