11-06-2007
Solaris 10 has no support for TCP splicing.
10 More Discussions You Might Find Interesting
1. IP Networking
Hello,
I have 4 unix (Solaris 8) stations need to setup on network.
what is a easy way and quick to setup TCP/IP so I can bring it online?. Please advise! (3 Replies)
Discussion started by: phapvn
3 Replies
2. IP Networking
I have just installed solaris 8 for Intel on one of my machines at home and I have a cable modem connection with a static IP and I am using a linksys cable/dsl router to assign IP's to my machines. I was wondering if any of you guys know the specific files and examples of the files I have to... (2 Replies)
Discussion started by: reggie316
2 Replies
3. Solaris
I've installed sun solaris 9 and i need to know how can i enable TCP Keepalive to ping socket connections every 300 seconds?
Thanks,
Mohammed Amin (1 Reply)
Discussion started by: m_amin
1 Replies
4. Solaris
hi expert,
hi all very need help please advice, i have v890 production server (gateway server) which running on telecommunication application (e.g USSD application) on this few month i have a problem with the connection to application server, for 2 - 3 hours the connection always down and cannot... (0 Replies)
Discussion started by: bucci
0 Replies
5. Solaris
Hi all
I haven't had much experience with Solaris 10 but we've started running into a problem where a process hangs, it is killed and leaves a zombie process. The sysadmins are saying this zombie process is locking a tcp port and not allowing the process to start up.
The process is a usually... (5 Replies)
Discussion started by: casphar
5 Replies
6. Solaris
I want to log tcp-wrapper events Solaris 10. I researched and saw that I could make a syslog entry in the hosts.deny, which I did below. After restarting syslog and having ssh blocking, I see nothing logging. I also do not get the email that should be generated. The file was taken from a... (2 Replies)
Discussion started by: csgonan
2 Replies
7. Solaris
Hi,
I have 3 solaris servers. Two servers of differnet network and one gateway.
Server1 --> 192.168.0.1 --> Solaris 9
Server2 --> 10.27.40.2 --> Solaris 10
Server3 --> Iface1 --> 192.168.0.5 --> Solaris 10 --> Gateway
Iface2 --> 10.27.40.5
Now I am able to ssh... (36 Replies)
Discussion started by: neel.gurjar
36 Replies
8. Solaris
Hi,
I am having a solaris server. I want to start a dummy TCP listner on UNIX OS on a specific port can anyone please let me know the process.
IP ADDRESS: 123.123.123.123
Port: 8010 (1 Reply)
Discussion started by: mayank2211
1 Replies
9. IP Networking
Hi
I am looking to tweek the rpcmod:clnt_max_conns to take advantage of extra bandwidth. I am running iperf -c <server_ip> -t 1800 -i 10
to check the throughput before and after I change the value in /etc/system,
but not seeing any throughput improvement.
How should I be testing this? Any... (4 Replies)
Discussion started by: eeisken
4 Replies
10. Solaris
I have problem with oracle solaris 10 running on oracle sparc T4-2 server.
Os information: 5.10 Generic_150400-03 sun4v sparc sun4v
Output from tcpstat.d script
TCP bytes: out outRetrans in inDup inUnorder
6833763 7300 98884 0... (2 Replies)
Discussion started by: insatiable1610
2 Replies
FAITH(4) BSD Kernel Interfaces Manual FAITH(4)
NAME
faith -- IPv6-to-IPv4 TCP relay capturing interface
SYNOPSIS
device faith
DESCRIPTION
The faith interface captures IPv6 TCP traffic, for implementing userland IPv6-to-IPv4 TCP relay like faithd(8).
Each faith interface is created at runtime using interface cloning. This is most easily done with the ifconfig(8) create command or using
the cloned_interfaces variable in rc.conf(5).
Special action will be taken when IPv6 TCP traffic is seen on a router, and the routing table suggests to route it to the faith interface.
In this case, the packet will be accepted by the router, regardless of the list of IPv6 interface addresses assigned to the router. The
packet will be captured by an IPv6 TCP socket, if it has the IN6P_FAITH flag turned on and matching address/port pairs. As a result, faith
will let you capture IPv6 TCP traffic to some specific destination addresses. Userland programs, such as faithd(8) can use this behavior to
relay IPv6 TCP traffic to IPv4 TCP traffic. The program can accept some specific IPv6 TCP traffic, perform getsockname(2) to get the IPv6
destination address specified by the client, and perform application-specific address mapping to relay IPv6 TCP to IPv4 TCP.
The IN6P_FAITH flag on a IPv6 TCP socket can be set by using setsockopt(2), with level IPPROTO_IPV6 and optname IPv6_FAITH.
To handle error reports by ICMPv6, some ICMPv6 packets routed to an faith interface will be delivered to IPv6 TCP, as well.
To understand how faith can be used, take a look at the source code of faithd(8).
As the faith interface implements potentially dangerous operations, great care must be taken when configuring it. To avoid possible misuse,
the sysctl(8) variable net.inet6.ip6.keepfaith must be set to 1 prior to using the interface. When net.inet6.ip6.keepfaith is 0, no packets
will be captured by the faith interface.
The faith interface is intended to be used on routers, not on hosts.
SEE ALSO
inet(4), inet6(4), faithd(8)
Jun-ichiro itojun Hagino and Kazu Yamamoto, An IPv6-to-IPv4 transport relay translator, RFC3142.
HISTORY
The FAITH IPv6-to-IPv4 TCP relay translator first appeared in the WIDE hydrangea IPv6 stack.
BSD
April 10, 1999 BSD