| Microware OS-9 Support Links | ||||||
|---|---|---|---|---|---|---|
| Home | Training | Resources | TECH-CHECK | History | Registered Support | Logout |
Hint: You can dynamically change your IP address, hostname, and other ISP parameters with the 'ispcfg' command (ISP 2.1 or later only)
Example: Change the IP address on a 821ADS board (the 821's ethernet descriptor is qe0)
ispcfg /qe0 (to show your current setup)
ispcfg /qe0 addr=206.72.9.92
ispcfg /qe0 (demonstrate the IP address has been changed)Note that this change will not be permanent, and will only be in effect until you reinitialize the descriptor (such as by rebooting). For a permanent change, follow the configuration instructions in the ISP manual.
Hints: When trying to set up your system to use ISP, a good first test to see if the basics are properly configured is to 'telnet localhost'. If you get to a login prompt, you know that you have all the proper modules in place to establish a network connection. If this works and then you find that you cannot telnet to another machine, re-examine your network settings and verify that you are using the proper descriptor. A dump -m of your network descriptor will allow you to see if the IP addresses are configured properly (they will be in hex). For example, on a MVME167 machine, dump -m ie0 reveals:
$ dump -m ie0
Addr 0 1 2 3 4 5 6 7 8 9 A B C D E F 0 2 4 6 8 A C E
-------- ---- ---- ---- ---- ---- ---- ---- ---- ----------------
00000000 4afc 0001 0000 00d4 0000 0000 0000 00c4 J|.....T.......D
00000010 0555 0f01 8000 00c8 0000 0000 0000 0000 .U.....H........
00000020 0000 0000 0000 0000 0000 0000 0000 3f8e ..............?.
00000030 fff4 6000 6705 0503 00be 00b8 0000 0000 .t`.g...>.8.....
00000040 0000 0000 0000 0001 0900 0000 00c4 05dc .............D.\
00000050 0022 00a2 ffff ff00 0092 00b2 0000 0000 .".".......2....
00000060 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000070 0000 0000 0000 0000 0000 0000 0002 0000 ................
00000080 0000 0000 0000 0004 0020 0008 00af 0019 ............./..
00000090 0054 0002 0000 c034 6dff 0000 0000 0000 .T....@4m.......
000000a0 0000 0002 0000 c034 6d39 0000 0000 0000 ......@4m9......
000000b0 0000 0000 0000 0000 6966 3136 3700 6966 ........if167.if
000000c0 6d61 6e00 6965 3000 0000 0000 0000 0000 man.ie0.........
000000d0 0054 41d3 .TASLooking at offset 0x96, you see the string 'c034 6dff' and on the line directly below, at offset 0xa6, you see the string 'c0346d39'. These translate to 192.52.109.255 and 192.52.109.57 respectively. The offsets to your addresses may be found at different offsets, but if you look for the hexadecimal representation of your IP and do not find it, chances are you are using the wrong descriptor.
Retrace your steps and pay close attention to where the descriptor will be placed. Normally, this will be in your particular port directory. For example, on the MVME167 system above running ISP V2.1, the descriptor is found in the directory: /h0/MWOS/OS9/68020/PORTS/MVME167/CMDS/BOOTOBJS/ISP
Problem: When I try mounting a NFS exported disk on my OS-9® machine, I get "Invalid client credital".
This is not an OS-9® specific problem. From the Solaris 2 FAQ:
Some vendors still ship a version of RPC/NFS that allows at most 8 groups in the client credentials. Root on Solaris is by default in 10 groups. As a result, the Solaris 2.x mount command will send AUTH_UNIX credentials that are too big to cope with for the remote mount daemon resulting in the "Invalid client credential"' error. Workaround: put root and all your users in 8 or less groups. NOTE: You must logout and login again for changes in the number of groups to take effect. (or exit root's shell and re-su)