| | 22 | As of now, network can be configure only manually using the `inetcfg` command. |
| | 23 | |
| | 24 | === Manual network configuration === |
| | 25 | |
| | 26 | Manual network configuration is quite easy. You can always check the current setting via the `inetcfg` command without arguments: |
| | 27 | |
| | 28 | {{{ |
| | 29 | / # inetcfg |
| | 30 | Configured addresses: |
| | 31 | 127.0.0.1/24 net/loopback v4a 1500 |
| | 32 | Static routes: |
| | 33 | None |
| | 34 | }}} |
| | 35 | |
| | 36 | Now, let's assume you want to configure HelenOS to have address 192.168.1.4. This is simply achieved by typing: |
| | 37 | |
| | 38 | {{{ |
| | 39 | / # inetcfg create 192.168.1.4/24 net/eth1 myaddr |
| | 40 | }}} |
| | 41 | |
| | 42 | `net/eth1` is one of the available links, in this case the first discovered network card. You may use the `locinfo` command to see what other links are there in the system. `myaddr` is a user-defined name given to the configured address. It is used to identify the address to other `inetcfg` commands. |
| | 43 | |
| | 44 | You may also want to configure the default gateway for your networked HelenOS system. Provided the gateway is at 192.168.1.1, type: |
| | 45 | |
| | 46 | {{{ |
| | 47 | / # inetcfg add-sr 0.0.0.0/0 192.168.1.1 default |
| | 48 | }}} |
| | 49 | |
| | 50 | Your HelenOS system is now configured for networking. Note that `inetcfg` understands also other commands that you can use to fix any potential problems with the configuration. To see the complete list, just type: |
| | 51 | |
| | 52 | {{{ |
| | 53 | / # inetcfg -h |
| | 54 | }}} |
| | 55 | |
