Enabling IPv6 Routing in Solaris

You can enable IPv6 from the command line or by creating a specific file that is found by the /etc/rc2.d/S69inet startup scripts at boot time.

The in.ndpd Process on the Non-Router

The in.ndpd process implements the Neighbor Discovery Protocol (NDP). Systems on the same network link use NDP for IPv6 to:

• Perform address autoconfiguration – Systems automatically configure an address for an interface. This eliminates the common duplicate IP address problem experienced on IPv4 networks.
• Obtain MAC addresses similar to how the Address Resolution Protocol (ARP) is used in IPv4 – Neighbor solicitation messages are sent by a node to determine the link-layer address of a neighbor or to verify that a neighbor is still reachable by a cached link-layer address. A solicitation can be sent if a node does not have an entry for a system in its neighbor cache. Neighbor solicitations are also used for duplicate address detection.
• Gather reachability information about paths to active neighbors – The in.ndpd process sends unsolicited neighbor advertisements to discover newly available systems. The in.ndpd process can also send unsolicited neighbor advertisements to announce a link-layer address change. Systems use received neighbor advertisements to update their neighbor cache with the MAC address of the sender.
• Discover routers – In IPv4, hosts had no way of knowing how to locate routers unless the host had a static route defined or it was running a type of routing protocol. IPv6 neighbor discovery replaced the function that the IPv4’s Router Discovery (RDISC) Protocol provided. Systems send router solicitations to prompt routers to
  send router advertisements. Routers advertise their presence with various link and Internet parameters, either periodically or in response to a router solicitation message.
• Router advertisements contain prefixes used for on-link determination or address configuration, a suggested hop limit value, and other information.
• Systems use router advertisements to populate their neighbor cache with the MAC address of the router. When an interface becomes enabled, hosts can send router solicitations that request routers to generate router advertisements immediately, rather than at their next scheduled time. This enables the host to become part of a network more quickly than it would have if it waited for a normal router advertisement.
• Provide router redirects–A router informs a host of a better first-hop node to reach a particular destination.
  Refer to RFC 2461 for more information about neighbor discovery.

IPv6 on Non-Routers Configuration

You can configure a system to support both IPv4 and IPv6. This configured system is known as a dual-stack system.

IPv6 introduces new files, including:

• /etc/hostname6.interface This file has similar functionality to the /etc/hostname.interface file but contains no IP address or host name information.

  Note – The /etc/hostname6.interface file can still contain an IPv6 address or a resolvable host name to disable autoconfiguration and enforce a given IPv6 address; however, this is not the regular case.
   

• /etc/inet/ipnodes This file has similar functionality to the /etc/inet/hosts file but has no link to the /etc/ipnodes file.

  Note – If an application is IPv6-capable, the /etc/inet/ipnodes file is consulted first, and then the /etc/inet/hosts file is consulted. The /etc/inet/hosts file is the only file that is contacted for IPv4 applications, and it can only contain IPv4 addresses.

Configuring an Interface for IPv6

To configure IPv6 on a system, create a /etc/hostname6.interface file, and reboot the system or use the ifconfig utility to manually configure the interface. For example, to configure IPv6 on the  system’s hme0 interface, complete the following steps:

1. View the configuration of the system’s interfaces before making any changes.

# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000

hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255
ether 8:0:20:90:b5:c7

2. Create the /etc/hostname6.interfacefile to cause the interface to configure with IPv6, and then reboot the system.

# touch /etc/hostname6.hme0
# init 6
#
INIT: New run level: 6

3. Watch the start messages for IPv6 messages, which are similar to the
following:

...
...
configuring IPv6 interfaces: hme0.
...
...
Starting IPv6 neighbor discovery.
...
...

4. View the system’s interface configuration after the boot.

# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000

hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255
ether 8:0:20:90:b5:c7

lo0: flags=2000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6> mtu 8252 index 1
inet6 ::1/128

hme0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2
ether 8:0:20:90:b5:c7
inet6 fe80::a00:20ff:fe90:b5c7/10

Notice how both the lo0 and hme0 interfaces have inet6 components and that each interface has an inet6 address. Recall from a previous step that an IPv6 address was not defined.

Configuring IPv6 Name Service Lookup

Like IPv4, you can apply names to IPv6 addresses so that you can more easily refer to a system. For example, to name this system’s IPv6 hme0 interface -v6, you can add an entry to the /etc/inet/ipnodes file to make it look similar to the following:

# tail -2 /etc/inet/ipnodes
# added for ipnode example
fec0::a00:20ff:fe90:b5c7 -v6
 

You can now address the system by its IPv6 interface by using the -v6 host name, for example:

# ping -v6
-v6 is alive

Name service lookup configuration for IPv6 is similar to name service lookup configuration for IPv4.

The following are additional files:

• Two new Network Information Service (NIS) IPv6 maps are the ipnodes.byname and ipnodes.byaddr maps. These maps have similar functionality to the hosts.bynameand hosts.byaddrfiles in IPv4.
• An additional Network Information Service Plus (NIS+) IPv6 table is created: ipnodes.org_dir. This table has similar functionality to the hosts.org_dir. table in IPv4.
• A new Domain Name System (DNS) record type, AAAA (quad A) is available. The reverse is similar to a normal PTR record but is much longer. Following is an example of an AAAA record and a PTR record:
  sys22.two.edu. IN AAAA fec0::a00:20ff:feb5:4137

  
  7.3.1.4.5.b.e.f.f.f.0.2.0.0.a.0.0.0.0.0.0.0.0.0.0.0.0.0.0.c.e.f.ip6.int. IN PTR sys22.two.edu.
   

• The ipnodes line is used in the nsswitch.conf file for IPv6 system name resolution.
  
  hosts: files nisplus dns
  ipnodes: files nisplus dns

Non-Router Configuration Troubleshooting

You can use the netstat utility with the address-family (-f) inet6 option to display only IPv6-specific information when you troubleshoot. The netstat utility has multiple forms and produces different types and levels of output depending on the options that are used with the utility. To view the IPv6 route table, perform the command:

# netstat -f inet6 -r

Routing Table: IPv6
Destination/Mask Gateway Flags Ref Use If

fe80::/10 -v6 U 1 0 hme0
ff00::/8 -v6 U 1 0 hme0
default -v6 U 1 0 hme0
localhost localhost UH 1 0 lo0
 

To view multicast group information for IPv6 interfaces, perform the command:

# netstat -f inet6 -g
Group Memberships: IPv6
If Group RefCnt

lo0 ff02::1:ff00:1 1
lo0 ff02::1 1
hme0 ff02::202 1
hme0 ff02::1:ff90:b5c7 1
hme0 ff02::1 2
 

You can use the ifconfig utility to obtain IPv6-specific information by using the inet6 address family parameter. For example, to view the configuration of all IPv6 interfaces, perform the command:

# ifconfig -a inet6

lo0: flags=2000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6> mtu 8252 index 1
inet6 ::1/128

hme0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2
inet6 fe80::a00:20ff:fe90:b5c7/10

The in.ndpd Process on the Router

The IPv6 NDP is implemented by the in.ndpd process. The in.ndpd process implements IPv6 functions, including:

1. Router discovery
2. Prefix discovery
3. Address autoconfiguration
4. Address resolution
5. Neighbor unreachability detection

IPv6 Routing Information Protocol

Routing in IPv6 is almost identical to IPv4 routing in CIDR, except that the IPv6 addresses are 128 bits instead of 32 bits. The in.ripngd process is the IPv6 routing daemon for the Solaris.

In normal operation, the in.ripngd process listens on the UDP port 521 for route information datagrams. If the host is a router, it periodically supplies copies of its route table to any directly connected host and
network.

IPv6 Router Configuration

You can use the command line to configure an IPv4 router to support IPv6. You can activate IPv6 by starting specific processes or by rebooting the system.

Configuring Interfaces for IPv6

To designate which interfaces are configured with IPv6 at boot time, use the touch utility to create a /etc/hostname6.interface file for each interface. For example, to configure the system to configure the hme0and
qfe0 interfaces with IPv6 at boot time, enter the following:

# touch /etc/hostname6.hme0 /etc/hostname6.qfe0
 

Alternatively, configure the hme0 and qfe0 interfaces from the command line as follows:

1. View the interfaces configuration.

# ifconfig -a

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000

hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.30.31 netmask ffffff00 broadcast 192.168.30.255
ether 8:0:20:b9:72:23

qfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.1.1 netmask ffffff00 broadcast 192.168.1.255
ether 8:0:20:ac:9b:20

2. Use the ifconfig utility to configure the hme0 interface.

# ifconfig hme0 inet6 plumb up

3. Use the ifconfig utility to configure the qfe0 interface.

# ifconfig qfe0 inet6 plumb up
 

4. View the interfaces configuration.
# ifconfig -a

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000

hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.30.31 netmask ffffff00 broadcast 192.168.30.255
ether 8:0:20:b9:72:23

qfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.1.1 netmask ffffff00 broadcast 192.168.1.255
ether 8:0:20:ac:9b:20

hme0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2
ether 8:0:20:b9:72:23
inet6 fe80::a00:20ff:feb9:7223/10

qfe0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 3
ether 8:0:20:ac:9b:20
inet6 fe80::a00:20ff:feac:9b20/10

Configuring IPv6 Name Service Lookup

The IPv6 name service lookup mechanism is controlled in the same way as IPv4. Verify that the ipnodes database is defined correctly for your site’s name service lookup mechanism. For example, make sure that the following entry exists if the ipnodes database uses the system’s local file:

# grep ipnodes /etc/nsswitch.conf
ipnodes: files
 

Configuring the ndpd.conf File

Configure the ndpd.conf file to contain route configuration information on the routers. You do not have to advertise link-local addresses on a router because a link-local address cannot be routed. Recall that:

• A link-local address starts with FE8
• A site-local address starts with FEC
• An aggregatable global unicast address starts with 2or 3.

The following example demonstrates how to configure this router information

• Router advertisements are to be sent out to all interfaces. A site-local address, where the hme0 interface has a prefix of fec0:0:0:9255::0/64.
  
• An aggregatable global unicast address, where the hme0interface has aprefix of 2000:0:0:9255::0/64.
• A site-local address, where the qfe0 interface has a prefix of fec0:0:0:9256::0/64.
• An aggregatable global unicast address, where the qfe0interface has a prefix of 2000:0:0:9256::0/64.

Complete the following steps:

1. Define the /etc/inet/ndpd.conf file to have the following contents:

# cat /etc/inet/ndpd.conf

# Send router advertisements out all interfaces
ifdefault AdvSendAdvertisements on
#
# Advertise an unregistered (bogus) global prefix and a site
# local prefix using the default lifetimes
prefix fec0:0:0:9255::0/64 hme0
prefix 2000:0:0:9255::0/64 hme0
#
prefix fec0:0:0:9256::0/64 qfe0
prefix 2000:0:0:9256::0/64 qfe0
#

2. Reboot the system. Proceed to the Step 3 to configure the system from the command line.

# init 6
#
INIT: New run level: 6
...
...
Machine is an IPv4 router.
Machine is an IPv6 router.
Setting default IPv6 interface for multicast: add net ff00::/8: gateway
fe80::a00:20ff:feb9:7223

...
...

1. View the IPv6 configuration of the interfaces.


# ifconfig -a inet6
lo0: flags=2000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6> mtu 8252 index 1
inet6 ::1/128
hme0: flags=2100841<UP,RUNNING,MULTICAST,ROUTER,IPv6> mtu 1500 index 2
inet6 fe80::a00:20ff:feb9:7223/10
hme0:1: flags=2180841<UP,RUNNING,MULTICAST,ADDRCONF,ROUTER,IPv6> mtu 1500 index 2
inet6 2000::9255:a00:20ff:feb9:7223/64
hme0:2: flags=2180841<UP,RUNNING,MULTICAST,ADDRCONF,ROUTER,IPv6> mtu 1500 index 2
inet6 fec0::9255:a00:20ff:feb9:7223/64
qfe0: flags=2100841<UP,RUNNING,MULTICAST,ROUTER,IPv6> mtu 1500 index 3
inet6 fe80::a00:20ff:feac:9b20/10
qfe0:1: flags=2180841<UP,RUNNING,MULTICAST,ADDRCONF,ROUTER,IPv6> mtu 1500 index 3
inet6 2000::9256:a00:20ff:feac:9b20/64
qfe0:2: flags=2180841<UP,RUNNING,MULTICAST,ADDRCONF,ROUTER,IPv6> mtu 1500 index 3
inet6 fec0::9256:a00:20ff:feac:9b20/64
#

2. Observe how the site-local and aggregatable-global unicast addresses are assigned to unique logical interfaces.

3. To configure your system without rebooting it, complete the following steps:

1. Switch IPv6 IP forwarding on.
   # /usr/sbin/ndd -set /dev/ip ip6_forwarding 1
2. If required, configure the system to send routing redirects.
   # /usr/sbin/ndd -set /dev/ip ip6_send_redirects 1
    
3.  If required, configure the system to ignore routing redirects for
   IPv6.
   # /usr/sbin/ndd -set /dev/ip ip6_ignore_redirect 1
    
4. Start the in.ndpdprocess that reads the ndpd.conffile. Restart
   it if it is already running.
   # /usr/lib/inet/in.ndpd
    
5. Start the in.ripngd process, and force it to supply route
   information to the network.
   # /usr/lib/inet/in.ripngd -s
    
6. View the interface configuration:

   # ifconfig -a inet6
   lo0: flags=2000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6> mtu 8252 index 1
   inet6 ::1/128
   hme0: flags=2100841<UP,RUNNING,MULTICAST,ROUTER,IPv6> mtu 1500 index 2
   inet6 fe80::a00:20ff:feb9:7223/10
   hme0:1: flags=2180841<UP,RUNNING,MULTICAST,ADDRCONF,ROUTER,IPv6> mtu 1500 index 2
   inet6 2000::9255:a00:20ff:feb9:7223/64
   hme0:2: flags=2180841<UP,RUNNING,MULTICAST,ADDRCONF,ROUTER,IPv6> mtu 1500 index 2
   inet6 fec0::9255:a00:20ff:feb9:7223/64
   qfe0: flags=2100841<UP,RUNNING,MULTICAST,ROUTER,IPv6> mtu 1500 index 3
   inet6 fe80::a00:20ff:feac:9b20/10
   qfe0:1: flags=2180841<UP,RUNNING,MULTICAST,ADDRCONF,ROUTER,IPv6> mtu 1500 index 3
   inet6 2000::9256:a00:20ff:feac:9b20/64
   qfe0:2: flags=2180841<UP,RUNNING,MULTICAST,ADDRCONF,ROUTER,IPv6> mtu 1500 index 3
   inet6 fec0::9256:a00:20ff:feac:9b20/64
   #

Router Configuration Troubleshooting

You can perform basic troubleshooting of an IPv6 router by confirming that processes are running, examining the route table, and using the ping utility as shown in the following examples:

• Determine if the NDP daemon is running on each of the routers in question:

  # pgrep -lf ndpd

  108 /usr/lib/inet/in.ndpd
  
  # pgrep -lf ndpd

  1497 /usr/lib/inet/in.ndpd
   

• View the IPv6 route table on each router in question:
  
  # netstat -rn -f inet6
  
  Routing Table: IPv6
  Destination/Mask Gateway Flags Ref Use If

  
  2000:0:0:9255::/64 2000::9255:a00:20ff:feb9:7223 U 1 0 hme0:1
  fec0:0:0:9255::/64 fec0::9255:a00:20ff:feb9:7223 U 1 0 hme0:2
  2000:0:0:9256::/64 2000::9256:a00:20ff:feac:9b20 U 1 0 qfe0:1
  fec0:0:0:9256::/64 fec0::9256:a00:20ff:feac:9b20 U 1 0 qfe0:2
  2000:0:0:9257::/64 fe80::a00:20ff:fec0:449d UG 1 0 hme0
  fec0:0:0:9257::/64 fe80::a00:20ff:fec0:449d UG 1 0 hme0
  fe80::/10 fe80::a00:20ff:feac:9b20 U 1 0 qfe0
  fe80::/10 fe80::a00:20ff:feb9:7223 U 1 2 hme0
  ff00::/8 fe80::a00:20ff:feb9:7223 U 1 0 hme0
  ::1 ::1 UH 1 0 lo0
   

Send an ICMP echo request to a remote system to determine if you receive an ICMP echo response from the remote system. Do not attempt to communicate with the link-local address of a system across a router because routers do not forward link-local addresses.

# ping fec0::9255:a00:20ff:fec0:449d
fec0::9255:a00:20ff:fec0:449d is alive

# ping 2000::9255:a00:20ff:fec0:449d
2000::9255:a00:20ff:fec0:449d is alive

Managing IPv6

The tasks you use to manage IPv6 interfaces are similar to the tasks you use to manage IPv4 interfaces.

Displaying the State of IPv6 Interfaces

Use the ifconfig utility with the inet6 option to display the state of the IPv6 interfaces, for example:

# ifconfig -a inet6

lo0: flags=2000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6> mtu 8252 index 1
inet6 ::1/128

hme0: flags=2100841<UP,RUNNING,MULTICAST,ROUTER,IPv6> mtu 1500 index 2
inet6 fe80::a00:20ff:feb9:7223/10

hme0:1: flags=2180841<UP,RUNNING,MULTICAST,ADDRCONF,ROUTER,IPv6> mtu 1500 index 2
inet6 2000::9255:a00:20ff:feb9:7223/64

hme0:2: flags=2180841<UP,RUNNING,MULTICAST,ADDRCONF,ROUTER,IPv6> mtu 1500 index 2
inet6 fec0::9255:a00:20ff:feb9:7223/64

qfe0: flags=2100841<UP,RUNNING,MULTICAST,ROUTER,IPv6> mtu 1500 index 3
inet6 fe80::a00:20ff:feac:9b20/10

qfe0:1: flags=2180841<UP,RUNNING,MULTICAST,ADDRCONF,ROUTER,IPv6> mtu 1500 index 3
inet6 2000::9256:a00:20ff:feac:9b20/64

qfe0:2: flags=2180841<UP,RUNNING,MULTICAST,ADDRCONF,ROUTER,IPv6> mtu 1500 index 3
inet6 fec0::9256:a00:20ff:feac:9b20/64

Modifying an IPv6 Interface Configuration

Use the ifconfig utility to modify IPv6 interface configuration in a similar manner to IPv4 interfaces. The family type of IPv6 must be defined in the command after the interface option, for example:

ifconfig hme0 inet6 configuration options

Caution – Be sure to specify the inet6 family, or the command changes the configuration of an IPv4 interface.

Configuring Logical Interfaces

You can configure logical IPv6 interfaces by using the ifconfig utility with the inet6 parameter like you do in IPv4, for example:

ifconfig qfe0:3 inet6 plumb configuration options

To remove the logical interface, disable the interface, and then use the unplumb parameter, for example:

# ifconfig qfe0:3 inet6 down unplumb
 

Troubleshooting IPv6 Interfaces

You troubleshoot IPv6 interfaces like you troubleshoot IPv4 interfaces. Recall that different FPs are required on addresses destined beyond the local subnet. Therefore, do not spend time attempting to determine why you cannot access a system on another subnet with an IPv6 address that starts with fe8.

Displaying the IPv6 Route Table

You use the netstat utility with the address-family -finet6 option to display the IPv6 route table, for example:

# netstat -f inet6 -r
 
Routing Table: IPv6
Destination/Mask Gateway Flags Ref Use If

fe80::/10 -v6 U 1 0 hme0
ff00::/8 -v6 U 1 0 hme0
default -v6 U 1 0 hme0
localhost localhost UH 1 0 lo0

Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotes :  Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce :  Bernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS :  Programming Languages History : PL/1 : Simula 67 : C : History of GCC development :  Scripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month :  How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019