[quote=“vespaman, post:20, topic:172361”]OK, I tried this, and … It actually works pretty well: Sonos works, and I can access my Samba server from wifi, and I can surf the web on my mobile devices.
However Vera3 itself does not know how to reach internet.
Do you have any suggestion how to solve that?
I have now the following settings:
Firewall off
WAN (disconnected)
Static IP 10.1.202.3
Netmask 255.255.255.0
Gateway 10.1.200.2 ← My main router ip
DNS 10.1.200.8 ← My linux DNS server
LAN (connected to my LAN)
Static IP 10.1.200.3
DHCP srv off.
Netmask 255.255.255.0[/quote]
I am assuming there is a typo? 10.1.202.3? If not… that is your problem no route to host.
OK, tried both. When I cleared all the fields, staying at static, I got issues with luup engine (wouldn’t start).
Pushing to DHCP, at least it started fine, but still no internet for Vera3 itself.
Edit:Almost lost Vera when attempting to revert back to WAN, got the same luup engine issue, two thousand times before being able to get back into the UI.
No, this is not a typo, I did this to try to force Vera onto the 10.1.200.0 network on the lan side. Remember: the WAN port is disconnected…[/quote]
Ok I am confused ??? As far as I know the WAN side is what VERA considers is outbound. I have this configured and connected to my LAN. The LAN settings are for when VERA is directly connected to your PC and the network it creates. SO in you example you would set your PC to either DHCP from Vera (assuming that is still on) or statically define a 10.1.200.x address.
So I think you should have
WAN
10.1.200.3
255.255.255.0
10.1.200.2
10.1.200.8
LAN
I would leave it default so you always know what is even even after a factory refresh: 192.168.81.1
255.255.255.0
DHCP server on.
Can someone please post their /etc/config/network and /etc/config/wireless files from a Vera3 set it Automatic mode with Wireless on?
Here’s my reasoning: These two files control all of OpenWrt’s networking settings. It should be possible to hand-edit these files, then run /etc/init.d/wireless restart to reconfigure the network based on the edited settings. Once there’s a proof of concept we can hand the correct config files to MCV and ask them to make their GUI produce them.
Take any sensitive information out of /etc/config/wireless first, such as the wireless password.
[ul][li]Set Net/WIFI to Automatic[/li]
[li]Vera connnected to LAN via WAN port[/li]
[li]No connection on LAN Ports[/li][/ul]
Outcome:
[ul][li]Required both changes to be committed; otherwise it would assign a private IP address.[/li]
[li]Once committed and network restarted, I was able to see all LAN connections [/li]
[li]N.B. Changing back to Automatic was defaulting the WIFI Passkey. [/li]
[li]N.B. Remove LAN bridge. [/li][/ul]
Next test (tomorrow/Saturday) reassign ports 2,3 and 4 to VLAN 2 leaving Port 5 as local.
In addition, for other members of the forum, we are still testing and this has not been fully tested and therefore, you may wish to hold off until other testing is completed.
@futzle, Re: my last PM, “Remove LAN bridge” resolved refresh that I had identified.
[quote=“aschwalb, post:25, topic:172361”]Ok I am confused ??? As far as I know the WAN side is what VERA considers is outbound. I have this configured and connected to my LAN. The LAN settings are for when VERA is directly connected to your PC and the network it creates. SO in you example you would set your PC to either DHCP from Vera (assuming that is still on) or statically define a 10.1.200.x address.
So I think you should have
WAN
10.1.200.3
255.255.255.0
10.1.200.2
10.1.200.8
LAN
I would leave it default so you always know what is even even after a factory refresh: 192.168.81.1
255.255.255.0
DHCP server on.[/quote]
aschwalb, this is my settings, yes! But they will not allow me to fully access my network when being on the wlan side. Therefore the suggestions are dropping in how to fix things. Among other things, this will not let me control my Sonos.
[quote=“futzle, post:28, topic:172361”]Thanks Brientim. Those look pretty bog-standard. Here’s what I think should change:
[…][/quote]
futzle, Thank You!
Everything now works as one would have expected from scratch. I can now ping wlan devices on the vera wlan side, Sonos works just as good as it does in every other network, and I can fully access my samba server.
With thees settings, the Vera3 is a keeper, yeay!
You have rightfully earned the virtual Gold medal for support by the Swedish Vera user community!
Glad it’s working. Next step is to stress-test the hell out of it and make sure that the Vera3 hardware is happy with the configuration. There are countless discussions on the OpenWrt forums about hardware (not Vera) that works only for a day or two in a given wireless configuration.
Then I think we can safely create a shell script to automate the edits, that users can run at bootup time (the edited files don’t survive a reboot). That should be enough until MCV puts a configuration option into the Vera web UI.
Edit: @Brientim, I’d be thrilled if your VLAN testing worked, but surprised. In this case it isn’t about config files, but support for the switch model that is supposedly inside Vera3. My understanding is that you’d have to update the OpenWrt firmware to a trunk version newer than about January 2012.
Am I understanding correctly that this testing may eventually lead to Vera3 operating as a switch?
Thanks!
[quote=“futzle, post:32, topic:172361”]Glad it’s working. Next step is to stress-test the hell out of it and make sure that the Vera3 hardware is happy with the configuration. There are countless discussions on the OpenWrt forums about hardware (not Vera) that works only for a day or two in a given wireless configuration.
Then I think we can safely create a shell script to automate the edits, that users can run at bootup time (the edited files don’t survive a reboot). That should be enough until MCV puts a configuration option into the Vera web UI.
Edit: @Brientim, I’d be thrilled if your VLAN testing worked, but surprised. In this case it isn’t about config files, but support for the switch model that is supposedly inside Vera3. My understanding is that you’d have to update the OpenWrt firmware to a trunk version newer than about January 2012.[/quote]
Right now they can get the wifi network of Vera to operate on the same network as the rest of your home network and not be on a separate subnet (network). However, utilizing the additional ports on the Vera 3 to have access to the same network may not work due to support for the switch model used in the unit and the current version of openwrt on the Vera unit. It might require a newer firmware version that futzle mentioned in the post above.
Just a quick update as I have been busy with my normal work and other commitments.
After an initial error (human), I reset and this has now been fully functional as an AP to WAN (WAN port on Vera connected to existing LAN) since Saturday.
The changes below were implemented as identified by @futzlehere
Vera 3 DNS disabled as identified in this thread Veralite DNS server?
No other test has been performed. There has been intermittent connection by various other devices and no degradation of service has been identified to date.
Edit /etc/config/wireless:
config 'wifi-iface'
option 'device' 'radio0'
option 'network' 'wan' <-- change this from lan to wan
option 'mode' 'ap'
Edit /etc/config/network:
[code]
config ‘interface’ ‘lan’
option ‘ifname’ ‘eth0.1’
option ‘type’ ‘bridge’ <— delete line (N.B. No other ports are being utilised during testing)
It sounds like this should allow me to use Vera3 as a switch (specifically a Wireless Access Point).
Could you tell me where the network and wireless files are found?
Thank you.
[quote=“Brientim, post:35, topic:172361”]Just a quick update as I have been busy with my normal work and other commitments.
After an initial error (human), I reset and this has now been fully functional as an AP to WAN (WAN port on Vera connected to existing LAN) since Saturday.
The changes below were implemented as identified by @futzlehere
Vera 3 DNS disabled as identified in this thread Veralite DNS server?
No other test has been performed. There has been intermittent connection by various other devices and no degradation of service has been identified to date.
Edit /etc/config/wireless:
config 'wifi-iface'
option 'device' 'radio0'
option 'network' 'wan' <-- change this from lan to wan
option 'mode' 'ap'
Edit /etc/config/network:
[code]
config ‘interface’ ‘lan’
option ‘ifname’ ‘eth0.1’
option ‘type’ ‘bridge’ <— delete line (N.B. No other ports are being utilised during testing)
This will only allow you to use wireless devices connected to Vera’s wireless network to access the rest of your network. It will not allow you to utilize the ports on vera to allow access to your local network.
