Route ipv6 through Mac OS Server 10.6.6. Support - Discussions - Native IPv6 configuration ... From whom did you get your IPv6 block?
A native block from your ISP? A block from a tunnel broker? I don't have native IPv6 from my ISP to play with, but the AEBS IPv4 setup for tunnels is very simple (and elegant.) In fact, I wish it was better advertised how easy IPv6 on the AEBS is because even a total noob could have it running on day 1. Basically, under Advanced|IPv6, if you simply choose tunnel and automatic, it setups up a 6to4 IPv6 tunnel:1) it grabs your WAN IP address and generates a 2002:xxxx.xxxx:: 6to4 IPv6 network number from it. I have a static IPv4 address, so my 2002:xxxx.xxxx:: stays the same, but I'm guessing that if you have DHCP on the WAN, the AEBS will change your 2002:xxxx.xxxx:: network address dynamically. Alternatively, if you have an IPv6 block from a tunnel broker, you choose Tunnel| Manual, and enter in the tunnel's remote and local IP addresses and the assigned IPv6 block for your LAN (all provided provided by the tunnel broker.)
Using OpenSSH through a SOCKS compatible firewall on your LAN. Using OpenSSH through a SOCKS compatible PROXY on your LAN This guide has been written by J. Grant. 2002-04-15 Version 0.9 Copyleft J. Grant. Including this in any other documents is permitted under the GNU Free Documentation Licence, providing my name is given next to the section. Distributing this any other way is permitted providing it is complete and contains this message. New versions can be found on the page hosted by Goto-san: This guide has been featured on the Mandrake website: Tested on Linux Mandrake 8.1, this will not affect you providing you have RPM support.
Introduction The SOCKS firewall protocol was fostered by NEC, they currently DO NOT support a free version of their tools for UNIX (free as in freedom, not beer). TCP_CORK: More than you ever wanted to know. April 6, 2005 I previously mentioned the leakiness of Unix's file metaphor.
The leak often becomes a gushing torrent when trying to bump up performance. TCP_CORK is yet another example. Before I get into the details of TCP_CORK and the problem it addresses, I want to point out that this is a Linux only option, although variants exist on other *nix flavors -- for instance TCP_NOPUSH on FreeBSD and Mac OS X (although from what I read the OS X implementation is buggy).
This is one of the unfortunate aspects of modern Unix programming. What are "physical" socket writes? The root of the abstraction leak derives from the semantics of the write() function when applied to TCP/IP. Any data that has been sent to the kernel with write() is placed into one or more packets and immediately sent onto the wire. The resulting behavior is what application programmers expected.
Nagle's algorithm Nagle not optimal for streams It also requires the peer to process more packets when network latency is low. The C10K problem. [Help save the best Linux news source on the web -- subscribe to Linux Weekly News!] It's time for web servers to handle ten thousand clients simultaneously, don't you think? The ultimate SO_LINGER page, or: why is my tcp not reliable. Edit The ultimate SO_LINGER page, or: why is my tcp not reliable Posted by bert hubert on 01/18/2009 This post is about an obscure corner of TCP network programming, a corner where almost everybody doesn’t quite get what is going on.
I used to think I understood it, but found out last week that I didn’t. So I decided to trawl the web and consult the experts, promising them to write up their wisdom once and for all, in hopes that this subject can be put to rest. The experts (H. Even though I refer a lot to the Linux TCP implementation, the issue described is not Linux-specific, and can occur on any operating system. What is the issue? Sometimes, we have to send an unknown amount of data from one location to another.
“TCP provides a reliable, stream-oriented, full-duplex connection between two sockets on top of ip(7), for both v4 and v6 versions. Sock = socket(AF_INET, SOCK_STREAM, 0); connect(sock, &remote, sizeof(remote)); write(sock, buffer, 1000000); // returns 1000000 close(sock);