Triode, Triode,
As soa-aur has now changed to using netctl alone, I thought I should re-test the functioning of the soa-web interface pages. I'm restricted to using QEMU so can only test the Ethernet Interface page. The sdcard create scripts sets up the system to default to a dhcp wired connection, e.g: '[image: http://s7.postimg.org/tv3pczd7b/soa29.jpg]' (http://postimg.org/image/tv3pczd7b/) Re-testing raises a number of questions/problems/errors. 1. -What useful function does the Interface Down button provide?- If you press this button the action triggered is to stop the netctl profile eth0. The ethernet connection is lost, as is access to soa-web, and if the user happens to have installed jivelite they have no way in even if they connect a monitor to their Wandboard. They must re-boot to re-establish the original dhcp wired connection. 2. - What useful function does the Interface Up button provide?- This action cannot be accessed if you have previously pressed the Interface Down button, and if the ethernet connection is already up it has no effect. 3. -Does the Interface Down/Interface Down button work as expected?- This is provided in order to change the ethernet setting, for example from dhcp to static, and restart the interface with new parameters without having to reboot the Wandboard, although you may have to re-connect to the soa-web. On testing this does not work., e.g changing from dhcp to static. User action enter valid static ip details and press Save button: The output from journalctl -f shows this: Code: -------------------- Jul 15 12:04:04 alarm soa-web.lua[235]: [I 2014/07/15 11:59:36] [web.lua] Added /usr/share/soa-web/static/network.png (4614 bytes) to static file cache. Jul 15 12:04:04 alarm sudo[299]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/cp /tmp/ifcfg.config-luagui /etc/netctl/eth0 Jul 15 12:04:04 alarm sudo[299]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 15 12:04:04 alarm sudo[299]: pam_unix(sudo:session): session closed for user root Jul 15 12:04:05 alarm sudo[304]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/systemctl disable [email protected] Jul 15 12:04:05 alarm sudo[304]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 15 12:04:05 alarm systemd[1]: Reloading. Jul 15 12:04:09 alarm sudo[304]: pam_unix(sudo:session): session closed for user root Jul 15 12:04:09 alarm sudo[316]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/netctl enable eth0 Jul 15 12:04:09 alarm sudo[316]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 15 12:04:09 alarm systemd[1]: Reloading. Jul 15 12:04:13 alarm sudo[316]: pam_unix(sudo:session): session closed for user root -------------------- file /etc/netctl/eth0: Code: -------------------- [root@alarm ~]# cat /etc/netctl/eth0 # created by soa-web Tue Jul 15 12:04:03 2014 Description='configuration for eth0' Interface=eth0 Connection=ethernet IP=static Address='192.168.0.111/255.255.255.0' Gateway='192.168.0.254' DNS=('192.168.0.254') -------------------- Press Interface Down/Interface Up button: Output from journalctl -f Code: -------------------- Jul 15 12:09:30 alarm sudo[347]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/netctl stop eth0 Jul 15 12:09:30 alarm sudo[347]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 15 12:09:31 alarm systemd[1]: Stopping configuration for eth0... Jul 15 12:09:32 alarm network[352]: Stopping network profile 'eth0'... Jul 15 12:09:34 alarm dhcpcd[233]: eth0: removing default route via 192.168.0.254 Jul 15 12:09:34 alarm dhcpcd[233]: eth0: removing route to 192.168.0.0/24 Jul 15 12:09:34 alarm dhcpcd[233]: eth0: removing IP address 192.168.0.204/24 Jul 15 12:09:34 alarm network[352]: Stopped network profile 'eth0' Jul 15 12:09:34 alarm systemd[1]: Stopped configuration for eth0. Jul 15 12:09:34 alarm sudo[347]: pam_unix(sudo:session): session closed for user root Jul 15 12:09:35 alarm sudo[396]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/netctl start eth0 Jul 15 12:09:35 alarm sudo[396]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 15 12:09:36 alarm ntpd[241]: Deleting interface #3 eth0, 192.168.0.204#123, interface stats: received=33, sent=33, dropped=0, active_time=716 secs Jul 15 12:09:36 alarm ntpd[241]: 87.117.251.3 local addr 192.168.0.204 -> <null> Jul 15 12:09:36 alarm ntpd[241]: 5.9.110.236 local addr 192.168.0.204 -> <null> Jul 15 12:09:36 alarm ntpd[241]: 178.63.83.2 local addr 192.168.0.204 -> <null> Jul 15 12:09:36 alarm ntpd[241]: Deleting interface #5 eth0, fe80::5054:ff:fe12:3456%2#123, interface stats: received=0, sent=0, dropped=0, active_time=716 secs Jul 15 12:09:36 alarm systemd[1]: Starting configuration for eth0... Jul 15 12:09:36 alarm dhcpcd[233]: eth0: carrier lost Jul 15 12:09:37 alarm network[428]: Starting network profile 'eth0'... Jul 15 12:09:37 alarm kernel: smsc911x smsc911x eth0: SMSC911x/921x identified at 0xc0880000, IRQ: 47 Jul 15 12:09:37 alarm kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 15 12:09:38 alarm kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jul 15 12:09:39 alarm dhcpcd[233]: eth0: carrier acquired Jul 15 12:09:40 alarm ntpd[241]: Listen normally on 6 eth0 192.168.0.111:123 Jul 15 12:09:40 alarm ntpd[241]: bind(21) AF_INET6 fe80::5054:ff:fe12:3456%2%2#123 flags 0x11 failed: Cannot assign requested address Jul 15 12:09:40 alarm ntpd[241]: unable to create socket on eth0 (7) for fe80::5054:ff:fe12:3456%2#123 Jul 15 12:09:40 alarm ntpd[241]: failed to init interface for address fe80::5054:ff:fe12:3456%2 Jul 15 12:09:40 alarm ntpd[241]: new interface(s) found: waking up resolver Jul 15 12:09:40 alarm sudo[396]: pam_unix(sudo:session): session closed for user root Jul 15 12:09:41 alarm network[428]: Started network profile 'eth0' Jul 15 12:09:41 alarm systemd[1]: Started configuration for eth0. Jul 15 12:09:42 alarm ntpd[241]: Listen normally on 8 eth0 [fe80::5054:ff:fe12:3456%2]:123 Jul 15 12:09:42 alarm ntpd[241]: new interface(s) found: waking up resolver Jul 15 12:09:42 alarm dhcpcd[233]: eth0: IAID 00:12:34:56 Jul 15 12:09:42 alarm dhcpcd[233]: eth0: rebinding lease of 192.168.0.204 Jul 15 12:09:47 alarm dhcpcd[233]: eth0: leased 192.168.0.204 for 86400 seconds Jul 15 12:09:47 alarm dhcpcd[233]: eth0: adding route to 192.168.0.0/24 Jul 15 12:09:47 alarm dhcpcd[233]: eth0: adding default route via 192.168.0.254 Jul 15 12:09:49 alarm ntpd[241]: Listen normally on 9 eth0 192.168.0.204:123 Jul 15 12:09:49 alarm ntpd[241]: new interface(s) found: waking up resolver -------------------- The ip addr is *not* changed the original dhcp is restarted but the soa-web Ethernet Interface page at http://192.168.0.204/network-wired.html shows this: '[image: http://s30.postimg.org/fuahumoxp/soa30.jpg]' (http://postimg.org/image/fuahumoxp/) I believe the fix is to flush the ip addr between stopping and starting the netctl profile after the file /etc/netctl/eth0 is changed,eg, use ip addr flush dev eth0 So you need to know the wired device name in use. 4. -Change to cope with cidr notation-. User Input - ip address of the form 192.168.0.100/24 This is accepted as valid. User Inut ip address of the form 192.168.0.100 and netmask 24 This is accepted a s valid. In both cases web page displays 255.255.255.0 as the netmask, and this value is used in file /etc/netctl/eth0. User Input - a netmask that passes validation, but doesn't match user's network, eg 25.255.255.0: Accepted by so-web interface, file /etc/netcl/eth0 re-written. Code: -------------------- [root@alarm ~]# cat /etc/netctl/eth0 # created by soa-web Tue Jul 15 12:24:29 2014 Description='configuration for eth0' Interface=eth0 Connection=ethernet IP=static Address='192.168.0.111/25.255.255.0' Gateway='192.168.0.254' DNS=('192.168.0.254') -------------------- Appears to be accepted, but because of point 3 above the change is not actioned until a reboot. On reboot, network connection fails: >From boot messages: Code: -------------------- [FAILED] Failed to start configuration for eth0. See 'systemctl status [email protected]' for details. -------------------- User now left without no internet connection and no way to fix it !!!!!! What is accpeted as valid, or rejected as invalid, netmask needs re-thinking. ------------------------------------------------------------------------ Krisbee's Profile: http://forums.slimdevices.com/member.php?userid=59080 View this thread: http://forums.slimdevices.com/showthread.php?t=101624
_______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
