In need of help with any form of suggestions. Not sure if this error is related to my not connecting to anything across my router. I can ping /telnet/ftp & exceed into my unix box from anyone of my workstations on my side of the router. My "defaultrouter" is setup pointing to my router. I've even attempted to add a route using "route add default xxx.xxx.xxx.xxx" but the return response is "route: socket: Protocol not supported." BELOW is what I found when I ran DMESG uranus in.mpathd[108]: [ID 801587 daemon.error] setup_rtsock: socket PF_ROUTE: Address family not supported by protocol family. Thanks Dave

U didn't mention whether r u using the hardened Monolithic Kernel or some thing else. By the way u can change the Default gateway address in Solaris box by editing the file present in /etc/inet. But if u r not using the hardened Unix box or Monolithic Kernel. Mukesh Kesharwani CCNA, SCSA, CUA,CNA, MCSE,MCP+I,CCNSE,Certified HIPPA Security http://www.keekar.com

What are you trying to do that isn't working? Mark

It all began when I attemtped to browse a website (any website) on the other side of my router. I first pinged my router which came back good. I figured DNS was working so I renamed my resolv.conf file to some other name to determine if I could ping hostnames after reanming this file. I could not. I checked my defaultrouter file and the correct ip is located in there. This is where I'm at at the moment. I can from another machine linux of windows ftp and telnet or exceed into my solaris box on this side of the router, but anything on the other side is impossible. whether its IP or hostname its always the same unreachable result. I have swamped the card using a new one. If I do a netstat -r my default router is listed. I've even attempted to complete a netstat -f to flush the table but this is where the "protocol not supported comes up. Any route add ??????????anything?????? comes up with the same results. Today I reloaded the OS thinking I missed something in the install but that did not help matters either. Same results. Anyway any suggestions would be greatly appreciated. As for a Monolithic Kernel hey ya got me. Never heard that one before. Dave

Till time I am not able to understand what u r trying to do but as u mentioned that u are interested to browse the internet from your Solaris machine. If it yes Please check the following components 1.) Check nsswitch.conf file for Name resolution service specially the sequence of search and its order ex the hosts line should be look like this hosts: nisplus dns files. 2.) Resolve.conf files should be directed to DNS Server 3.) If U r using the private IP in this machine then the IP should be NATed at the Gateway level. 4.) Of course the /etc/defaultrouter file should be directed towards the router or to gateway. 5.) Last but not least your gateway should contain the route map for this machine to forward the packets to your desired network. Please let me know whether your problem is solved or not. OK u mentioned that you heard first time the terminology of monolithic kernel. We generally call all the hardened box which are used as firewall are running on Monolithic Kernel. because in such Boxes the dynamic change in system properties are not accepted by system until you accept the changes internally and reboot the system. Mukesh Kesharwani CCNA, SCSA, CUA,CNA, MCSE,MCP+I,CCNSE,Certified HIPPA Security Consultant http://www.keekar.com

Sorry about the previous verbage. Some how gets lost in the translation. >>>u are interested to browse the internet from your Solaris machine. Yes I’m interest in browsing the WEB. But for no other reason than fixing the connection issue that I’m facing at the moment. Connections to and from my other PCs/Linux all work okay. I am using the standard non routable IP (this may be my problem) 192.168.0.? My router currently NATs for all my other machines. On occasion I’ve atttmpted to add a route using “route add default hostname” but each time I enter at the command line “route add (anything at this point)” I get the protocol not supported. I listed below what my current settings are. At this point I’ve relaoded the OS and swapped out the NIC with a new NIC (Same make model). Running DMESG gives me information about my NIC, and I assume it about my NIC uranus in.mpathd[108]: [ID 801587 daemon.error] setup_rtsock: socket PF_ROUTE: Address family not supported by protocol family. If it yes Please check the following components 1.) >>>>Check nsswitch.conf file for Name resolution service specially the sequence of search and its order ex the hosts line should be look like this hosts: nisplus dns files. My nsswitch is currently set with hosts: dns files netmask : 255.255.255.0 2.) Resolve.conf files should be directed to DNS Server My resolv.conf is set with the following domain universe.net Local DNS Box 3.) If U r using the private IP in this machine then the IP should be NATed at the Gateway level. I assume this is happening. Not sure how to check My unix box is using a private 192.168.0.8 My gateway is 192.168.0.10 4.) Of course the /etc/defaultrouter file should be directed towards the router or to gateway. Is set with 192.168.0.10 5.) Last but not least your gateway should contain the route map for this machine to forward the packets to your desired network. Using netstat –r shows my default gateway of 192.168.0.10 OK u mentioned that you heard first time the terminology of monolithic kernel. We generally call all the hardened box which are used as firewall are running on Monolithic Kernel. because in such Boxes the dynamic change in system properties are not accepted by system until you accept the changes internally and reboot the system. Sorry not sure how to answer this one. I have rebooted my system many times with all settings staying the same. AMD SLOT A 750 512MB 20GB HD Solaris 9.0 X86 Thanks Dave

For years, I had thought that a monolithic kernel was a kernel in which everything gets compiled and linked into one BIG unix program. An example of this is the original Unix System V and BSD kernels as well as the original Linux kernel. The AIX, Solaris, and latest Linux kernel are micro kernels, designed to separate services from the operation policies of the kernel. When was this terminology hijacked by the computer security people and the definition changed to indicate a security hardened kernel? As to the users question. Protocol families are defined in the /usr/include/sys/sockets.h file. I believe that the mpathd daemon is attempting to create a socket using a protocol that has not been defined to your system. Here is the C code to open a create a socket: #include <sys/types.h> #include <sys/socket.h> socket( int domain, int type, int protocol ); Where the domain parameter specifies the communication domain (or protocol family) in which the socket should be created. These are defined in sys/socket.h or bits/socket.h (Linux). The type parameter is a socket type defined in sys/socket.h or bits/socket.h. The system call getprotobyname is used to obtain protocol parameter. Having said all the above, I think what is happening is that the mpathd process is discovering what it believes is a NIC failure and unfortunately, your system is not configured to support NIC fail over. Do a man on in.mpathd on your Sun box. I am not familar with Solaris (I am certified, but haven't work with Solaris in over 3 years). I think a call to Sun might be in order. Jerry Lemieux