Opened 6 years ago
Closed 2 months ago
#748 closed enhancement (fixed)
Persistent network configuration
| Reported by: | Jiri Svoboda | Owned by: | Jiri Svoboda |
|---|---|---|---|
| Priority: | major | Milestone: | 0.14.2 |
| Component: | helenos/unspecified | Version: | mainline |
| Keywords: | Cc: | ||
| Blocker for: | Depends on: | ||
| See also: |
Description
Network configuration in HelenOS is not preserved across reboots, even if persistent /w is available. Making it persistent is tricky, since we don't have a way to persistently identify IP links.
The current configuration model is too static and does not account for things like Wi-FI or walking around with a laptop and plugging an Ethernet cable into different networks.
Perhaps the configuration model should be changed to introduce a 'network connection' as the persistent entity against which we would anchor the configuration. Then we would detect network connection on a IP link by examining the SSID (for wireless), HW MAC address (for wired), etc.
Change History (3)
comment:1 by , 6 years ago
| Milestone: | 0.8.0 |
|---|
comment:2 by , 2 months ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:3 by , 2 months ago
| Milestone: | → 0.14.2 |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Implemented in changeset 1bbc6dc64db723b798344b36c45a156bdd6ccc13.
The current configuration model is unchanged, but configuration is retained across reboots in
/w/cfg/inetsrv.sif. Note that we do rely on the IP link names not changing (e.g. net/eth1), but that should work at least in the simple cases.