vellanix Posted July 29, 2016 Report Share Posted July 29, 2016 Hello, I had my agent running on raspberry and appearing on the web portal on the ip 10.212.1.22. Then I added the VLAN (I have a couple of network appliance on the VLAN with the ip 10.212.2.xx) setup to the raspberry, configured the switch and everything is running. Now I see also the other ip appliance on the VLAN. The only problem is that on the web portal the raspberry agent now appears with the IP address of the VLAN (10.212.2.22) instead of the main ip (10.212.1.22). Here's the setup of /etc/network/interfaces: ------------------------------ source-directory /etc/network/interfaces.d auto lo iface lo inet loopback auto eth0 allow-hotplug eth0 iface eth0 inet dhcp post-up ifup eth0.102 iface eth0.102 inet static address 10.212.2.22 netmask 255.255.255.0 ------------------------------------------------------------------------- any idea? thank you Link to comment Share on other sites More sharing options...
Giancarlo Posted July 30, 2016 Report Share Posted July 30, 2016 unfortunately, this is a known small issue (just from a front-end point of view). We have in our roadmap to fix, so that the Raspberry Pi will appear with all the IP addresses, starting from the one on the main VLAN. Link to comment Share on other sites More sharing options...
insurroundsound Posted August 12, 2016 Report Share Posted August 12, 2016 i think I'm having the same issue on my Domotz B box. Can you confirm, Giancarlo, that this problem also exists there on the front-end? I just added 5 VLANS to a B box, and now the Domotz box is showing up with the static IP address of the last VLAN instead of the primary internal IP address it had previously. Link to comment Share on other sites More sharing options...
Giancarlo Posted August 12, 2016 Report Share Posted August 12, 2016 2 hours ago, insurroundsound said: i think I'm having the same issue on my Domotz B box. Can you confirm, Giancarlo, that this problem also exists there on the front-end? I just added 5 VLANS to a B box, and now the Domotz box is showing up with the static IP address of the last VLAN instead of the primary internal IP address it had previously. Yes, that's the same issue. Just a front-end one, showing the last VLAN IP instead of all of them (and the primary in the list). Link to comment Share on other sites More sharing options...
vellanix Posted August 13, 2016 Author Report Share Posted August 13, 2016 it's since 5 days that the raspebbry agent appear on the main vlan (on the gui) and all the devices on the vlan 2 are marked offline, but they re online! I didnt change anything on the raspberry configuration, was the agent updated in the last days (like the app) and the problem it's related on the update? thank you Link to comment Share on other sites More sharing options...
Giancarlo Posted August 14, 2016 Report Share Posted August 14, 2016 17 hours ago, vellanix said: it's since 5 days that the raspebbry agent appear on the main vlan (on the gui) and all the devices on the vlan 2 are marked offline, but they re online! I didnt change anything on the raspberry configuration, was the agent updated in the last days (like the app) and the problem it's related on the update? thank you No update of the Agent in the last 2 weeks. The issue might be something else. Did you check if the switch port connecting the Raspberry has changed something? It seems like the Agent hosted on the Raspberry cannot scan devices on the VLAN 2. Link to comment Share on other sites More sharing options...
vellanix Posted August 14, 2016 Author Report Share Posted August 14, 2016 No changes to the switch. Now i restarted the raspberry: it appears on the vlan 2 in the web interface and both devices on main vlan and vlan 2 are online. So it seems that if the agent appears on the main vlan you can see only devices on the main vlan but if appear on the vlan 2 can see both vlan. Sound possible? thank you carlo Link to comment Share on other sites More sharing options...
vellanix Posted August 15, 2016 Author Report Share Posted August 15, 2016 A short and strange update... I didnt change anything, no reboot, nothing and now the raspberry is on main vlan and all device on vlan 2 are offline (in the userf interface of course) Whats going on?!?!?! Link to comment Share on other sites More sharing options...
Giancarlo Posted August 16, 2016 Report Share Posted August 16, 2016 12 hours ago, vellanix said: A short and strange update... I didnt change anything, no reboot, nothing and now the raspberry is on main vlan and all device on vlan 2 are offline (in the userf interface of course) Whats going on?!?!?! Hi Carlo, is it possible that something has changed on the port of the switch? Can you provide the output of the ifconfig when connected to the Raspberry Pi? Link to comment Share on other sites More sharing options...
vellanix Posted August 16, 2016 Author Report Share Posted August 16, 2016 Hi Giancarlo, no nothing changer in the switch port. Here's the actual ifconfig: ~ $ ifconfig eth0 Link encap:Ethernet HWaddr b8:27:eb:f3:c5:43 inet addr:10.212.1.22 Bcast:10.212.1.255 Mask:255.255.255.0 inet6 addr: fe80::dd48:b469:5f77:54f6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1701995 errors:0 dropped:0 overruns:0 frame:0 TX packets:6913017 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1713683153 (1.5 GiB) TX bytes:567682472 (541.3 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:63664 errors:0 dropped:0 overruns:0 frame:0 TX packets:63664 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:4420182 (4.2 MiB) TX bytes:4420182 (4.2 MiB) wlan0 Link encap:Ethernet HWaddr b8:27:eb:a6:90:16 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:2 errors:0 dropped:2 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:123 (123.0 B) TX bytes:0 (0.0 B) ----- it'a strange that only the main lan is visible. So I just rebooted and the ifconfig after reboot is: $ ifconfig eth0 Link encap:Ethernet HWaddr b8:27:eb:f3:c5:43 inet addr:10.212.1.22 Bcast:10.212.1.255 Mask:255.255.255.0 inet6 addr: fe80::ba27:ebff:fef3:c543/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2434 errors:0 dropped:0 overruns:0 frame:0 TX packets:8183 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2360969 (2.2 MiB) TX bytes:531188 (518.7 KiB) eth0.102 Link encap:Ethernet HWaddr b8:27:eb:f3:c5:43 inet addr:10.212.2.22 Bcast:10.212.2.255 Mask:255.255.255.0 inet6 addr: fe80::ba27:ebff:fef3:c543/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:41 errors:0 dropped:0 overruns:0 frame:0 TX packets:3134 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1993 (1.9 KiB) TX bytes:137719 (134.4 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:273 errors:0 dropped:0 overruns:0 frame:0 TX packets:273 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:18385 (17.9 KiB) TX bytes:18385 (17.9 KiB) wlan0 Link encap:Ethernet HWaddr b8:27:eb:a6:90:16 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:3 errors:0 dropped:3 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:259 (259.0 B) TX bytes:0 (0.0 B) -------- with the vlan 2... only with reboot and without changes on the raspberry or on the switch... and here's the interfaces config: auto lo iface lo inet loopback auto eth0 allow-hotplug eth0 iface eth0 inet dhcp post-up ifup eth0.102 iface eth0.102 inet static address 10.212.2.22 netmask 255.255.255.0 allow-hotplug wlan0 iface wlan0 inet manual wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf allow-hotplug wlan1 iface wlan1 inet manual wpa-conf /etc/wpa_supplicant/wpa_supplicant.confpi@raspberry ----- any idea? thank you carlo Link to comment Share on other sites More sharing options...
(1)(1)(1)(1)(1)(1).jpg.7dcdeb3fb90919aa2df390a4f448ac4b.thumb.jpg.77bf24b1396f1fd80d63b164713f41ff.jpg)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now