View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000153 | Kolibri OS (trunk) | Applications | public | 2022-01-29 19:17 | 2024-02-23 21:40 |
Reporter | floppy121 | Assigned To | hidnplayr | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | assigned | Resolution | open | ||
Product Version | SVN build / автосборка SVN | ||||
Target Version | SVN build / автосборка SVN | ||||
Summary | 0000153: NETSTAT could not apply the custom IP address settings - page fault or just nothing happens | ||||
Description | In example, the automatic DHCP settings failed and you would like to set up a static IP address for your KolibriOS PC. However, NETSTAT's Configure menu does not work: when you click "Apply" in the "IP settings" pop-up window, nothing changes and the new custom IP settings do not get applied. I either see a page fault on debug board, or simply nothing happens. How to reproduce: this happens if, instead of connecting a Kolibri OS PC's Ethernet to the domestic router, I connect it to another PC (for the purpose of sharing its' WiFi connection over Ethernet to KolibriOS laptop) - which probably doesn't have a DHCP configured properly at the moment. P.S. Also, the arrow left/right keyboard keys don't work, forcing you to use a mouse each time you need to move a text cursor without altering the text contents. | ||||
Tags | No tags attached. | ||||
SVN revision / ревизия SVN | r9675 | ||||
Type of distribution / Тип дистрибутива | any / любой | ||||
|
Luckily, the change in settings applies - but only after I disconnect the Ethernet cable and connect it again. This isn't obvious and might confuse a new user. If this has to be done, please show a notification asking a user to do this - or, better, please make it so the Ethernet connection is restarted by software and the settings are automatically applied, to avoid the need of reattaching a cable. |
|
Currently, IP addresses are managed by @zeroconf program. Netstat only changes the config file that is used by @zeroconf, but there is no mechanism in place to trigger it to apply the changes immediately yet. A current manual solution is to kill @zeroconf and restart it, but it is not how it should actually work. |