TCP packet with RST flag not carrying DSCP

10 More Discussions You Might Find Interesting

1. Solaris

XSCF, SP and Dscp - confused.

Hi all, I understand SP is a separate processor use for management purposes. I understand XSCF is the management facility (similar to IDRAC, ILOM etc). I understand that we can create multiple domains in a SPARC machine (something like VM) and we can install OS in it. I am able to use...

2. UNIX for Dummies Questions & Answers

Get the id with specify flag

.... means multi line ddd,bug fgdrg dfdfsdfdfsd fsdfdfdfd fdfdsfdsfsd ....... flag2 ...... aaa,bug sfsfsfsfs dfdfsdfdfsd fsdfdfdfd fdfdsfdsfsd ...... flag1 ...... ddd,bug fgdrg dfdfsdfdfsd

3. Solaris

WakeOnLan, tcp packet

I'd like to use SPARC Solaris10 to 'wake up' an old PC on same LAN. what is the simplest way of doing it? (preferably without installing new software) thanks.

4. Solaris

Too much TCP retransmitted and TCP duplicate on server Oracle Solaris 10

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...

5. AIX

Packet loss coming with big packet size ping

6. Shell Programming and Scripting

User switching without carrying over LC_CTYPE env variable

I am using Solaris8, userA's shell '/usr/ace/prog/sdshell', AppuserB's shell '/bin/ksh'. serverT:/home/userA>LC_CTYPE=iso_8859_1; export LC_CTYPE; vtemp='userA variable'; export vtemp serverT:/home/userA>echo "LC_CTYPE=$LC_CTYPE, vtemp=$vtemp"; LC_CTYPE=iso_8859_1, vtemp=userA...

7. UNIX for Dummies Questions & Answers

'h' flag in du

Hey, all! Why is the "human readable" flag changing the behavior of du? And while I'm at it, can you make du only look at files, not directories. I often find myself wanting to find the largest file(s) in a dir or vol. Using 'find' itself, it seems you have to at least be able to guess the size of...

8. IP Networking

TCP Packet size

Hi! I'm writing an application (using BSD sockets on a Linux host) which communicates over TCP/IP with an embedded device. This embedded device has an old and real slow integrated circuit (Epson S1S6000) which handles all of the TCP/IP communication for it. Problem is, this circuit (S1S6000)...

9. Programming

Changing source port number of a TCP client packet

Hi all, I need to change the source port number of an outgoing TCP packet. First I have to bind the socket to a particular port(suppose 9001) but when I send the TCP packet I want to change the source port number lets say to 9002 still letting the socket to be bound to the same old port (9001)....

10. Red Hat

Fedora 9 lands carrying OpenJDK 6 and more for developers

Dev Fu focuses on the fresh and free OpenJDK 6 in Fedora 9 (Sulphur) because this is great news for developers. Especially developers who want to use the best software because it’s free and it doesn’t suck. However, there is much more of interest for developers than just OpenJDK: Developers...

LEARN ABOUT PLAN9

faith

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

IP Networking