List of things not working..

[Fire69]

So, having received my A+ friday, I haven't been able to use it for 1 second without problems.

I'll try to summarize the problems I've encountered so far:

- When setting the internet connections as PPPoE, I have to save the settings twice before the connection is made.
- On the LCDUI, the wan-port always displays <no_ip> even though internet is working. Sometimes after releasing and renewing the ip several times, it does finally show up.
- On the WebUI, sometimes the PPPoE IP isn't shown.  When changing connection to DHCP, it still shows the PPPoE IP.
- When changing the IP of the A+ to 192.168.1.1 DHCP stops working. Sometimes immediately, sometimes after a couple of hours. See: http://forum.securifi.com/index.php/topic,2033.0.html
- When DHCP does keep working for some time, I tried setting static leases, some work, some don't.  As said, after some time, everything just stops.
- LCDUI shows currently 21 devices connected, WebUI shows 10
- Since this morning, the app (Android) and connect.securifi.com show my A+ as offline (although I'm 'happily' typing this post while connected to the A+, so internet works ok now). I'm apparently not alone with this problem, see: http://forum.securifi.com/index.php/topic,2057.0.html
It started after I changed the internet from DHCP to PPPoE.  Changing it back doesn't change anything.
- When going to the site or app, it says it's connecting and then shows the sensors. You'd thing they are up-to-date, but they are not (because of the previous point). You don't get an error.  When it (incorrectly) says the router is offline, why don't you get this message for the sensors?
- ...

I probably forgot some things, the list is getting a little too long.

As you can understand, I'm not really what you would call a happy customer right now...

[edit]
Did another factory reset.  The A+ now appears online again in app and website.  So it was clearly a configuration-problem and not something cloud-based...

[edit2]
Static leases are not synchronized between NutsOS and OpenWRT:
When I set a static lease in NutsOS, spaces are allowed in the hostname.
When I set a static lease in OpenWRT, spaces are not allowed in the hostname.
Leases set in NutsOS are shown in OpenWRT.
Leases set in OpenWRT are not shown in NutsOS.

I just keep running into more and more problems/bugs...

[edit3]
Apparently you can set static leases in 2 different places in OpenWRT => Network/DHCP-DNS and Network/LAN Settings.
When you set the static lease through Lan Settings, it does become visible in NutsOS (and you can use spaces)

[edit4]
DHCP lease is not working correctly.
I already noticed some devices kept having remaining lease times close to 12 hours, they would never count down far before being reset to 12 hours.
Now I just saw some devices with a lease time over 12 hours!

[Fire69]

Does anyone actually read this forum??? 

[sorphin]

Does anyone actually read this forum??? 

Plenty of people do.. but there are threads for a lot of the various issues you mentioned already...

[Fire69]

Well, I searched around primarily for the DHCP problems and the only response I got was that there isn't a bug, just a translation-error.

What is the official response about these problems from Securifi then? Because I'm basically stuck with 400$ of useless equipment for the moment...

[eldaria]

- When setting the internet connections as PPPoE, I have to save the settings twice before the connection is made.
- On the WebUI, sometimes the PPPoE IP isn't shown.  When changing connection to DHCP, it still shows the PPPoE IP.

Don't have PPPoE so can't test, but on your last one, it might take a moment for the router to switch over, but as I said I can't test it.

- On the LCDUI, the wan-port always displays <no_ip> even though internet is working. Sometimes after releasing and renewing the ip several times, it does finally show up.

This is hardly a show stopper, and not something I have noticed on any of my Almond+ (I have two, one Dev and one Final)
But Is it always or not, in the first sentence you say it is always, and in the next it says after release and renew it shows up?

- LCDUI shows currently 21 devices connected, WebUI shows 10

This I have noticed also, however I'm not sure they show the same thing. On the LCD it shows connected devices, and on the Web it shows DHCP clients.
Although the Web shows the correct amount of devices that I have(They are all on DHCP), the LCD GUI is showing too many, i'm not sure what the LCD GUI is showing. Perhaps it is all devices that try to scan for example over WiFi?

- When changing the IP of the A+ to 192.168.1.1 DHCP stops working. Sometimes immediately, sometimes after a couple of hours. See: http://forum.securifi.com/index.php/topic,2033.0.html
- When DHCP does keep working for some time, I tried setting static leases, some work, some don't.  As said, after some time, everything just stops.

Nope, not a problem, as I mentioned in the other thread, I have this exact setup and it works perfectly I had it running for about a week now without any issues.

Static leases are not synchronized between NutsOS and OpenWRT:
Leases set in NutsOS are shown in OpenWRT.
Leases set in OpenWRT are not shown in NutsOS.
Apparently you can set static leases in 2 different places in OpenWRT => Network/DHCP-DNS and Network/LAN Settings.
When you set the static lease through Lan Settings, it does become visible in NutsOS (and you can use spaces)

Confirmed, setting them in NutsOS will have them show up in OpenWRT, setting them in DHCP will not make them show up in NutsOS, setting them in LAN settings in OpenWRT will show up in NutsOS.

When I set a static lease in NutsOS, spaces are allowed in the hostname.
When I set a static lease in OpenWRT, spaces are not allowed in the hostname.
Apparently you can set static leases in 2 different places in OpenWRT => Network/DHCP-DNS and Network/LAN Settings.
When you set the static lease through Lan Settings, it does become visible in NutsOS (and you can use spaces)

Confirmed, Space is not an allowed character in a hostname, so the fact that both NutsOS and OpenWRT Lan Settings allow this should be a bug.
Also if you are trying to use space in your hostname it could explain some of the other problems you have with dhcp, as dnsmasq might get troubles working properly then.

I already noticed some devices kept having remaining lease times close to 12 hours, they would never count down far before being reset to 12 hours.
Now I just saw some devices with a lease time over 12 hours!

The above 12 hours i'm unsure about, but that they do not count down all the way makes sense.

It will reset when the client send a new request, the lease time is how long the dhcp server will keep that address for that specific client.
So if the client does not renew within this time then there is no guarantee that it will get the same IP again.
Therefore most clients will have a much shorter renew time than what the dhcp server lease is so that it renews before it expires.

[LGNilsson]

Fixed the picture size in the post above.

We have PPPoE running in the office here and I haven't noticed any issues. What modem do you have?

The connected devices in the LCD UI, I'm not sure, I'll check with the software team, as it's been like this for a while, it just haven't been that important to fix it.
Never had a problem with the WAN port not showing the IP address straight away, might be related to the PPPoE issue.

We're aware of some of the issues between NutsOS and OpenWRT and we'll get those fixed. There are a few more you haven't spotted as yet 

As eldaria pointed out, the DHCP leases aren't cut off dead if the device is still connected at the end of the lease time, it just means that once it re-connects to the network, it'll be assigned a new IP address if it has been longer than the assigned period of time.

[Fire69]

Don't have PPPoE so can't test, but on your last one, it might take a moment for the router to switch over, but as I said I can't test it.

Max I've waited was 5 minutes I think. That should be enough, but I'll test again.

This is hardly a show stopper, and not something I have noticed on any of my Almond+ (I have two, one Dev and one Final)
But Is it always or not, in the first sentence you say it is always, and in the next it says after release and renew it shows up?

True, definitely not a show stopper, but since I also had the PPPoE not working, it's nice to know if it's connected or not.
The connection is always on, I just do the release and renew to try and make it show the IP.

This I have noticed also, however I'm not sure they show the same thing. On the LCD it shows connected devices, and on the Web it shows DHCP clients.
Although the Web shows the correct amount of devices that I have(They are all on DHCP), the LCD GUI is showing too many, i'm not sure what the LCD GUI is showing. Perhaps it is all devices that try to scan for example over WiFi?

It says 'xx connected devices', so I'm guessing it's not for example my neighbours devices trying to connect to my A+
Also, not a show shower ofcourse, but still a little confusing.

Nope, not a problem, as I mentioned in the other thread, I have this exact setup and it works perfectly I had it running for about a week now without any issues.

Your image is a little small (not clickable) to see what it says.
What is your DHCP range?

Confirmed, setting them in NutsOS will have them show up in OpenWRT, setting them in DHCP will not make them show up in NutsOS, setting them in LAN settings in OpenWRT will show up in NutsOS.

So this is an OpenWRT bug? Why should there be 2 places to define them...

Confirmed, Space is not an allowed character in a hostname, so the fact that both NutsOS and OpenWRT Lan Settings allow this should be a bug.
Also if you are trying to use space in your hostname it could explain some of the other problems you have with dhcp, as dnsmasq might get troubles working properly then.

I've used spaces in the hostnames for years with my ISP's router without problems.
Also, when you set them in OpenWRT, it clearly says they are symbolical names, I'm guessing just to be able to identify the devices in the list, which seems logical.
If you need to use the hostname specified by the device (ie. android-asd548q35), it gets a little hard knowing which device it is.

I'll try setting some static leases without spaces as a test to see what happens.

The above 12 hours i'm unsure about, but that they do not count down all the way makes sense.
It will reset when the client send a new request, the lease time is how long the dhcp server will keep that address for that specific client.
So if the client does not renew within this time then there is no guarantee that it will get the same IP again.
Therefore most clients will have a much shorter renew time than what the dhcp server lease is so that it renews before it expires.

I did not know that 
I have 2 Foscam-cameras that don't appear to go below 12h50min.  So that would mean they renew every 10 minutes?

Thanks for taking the time to reply! 

Fixed the picture size in the post above.

Thanks
That is quite helpful, because I have a problem with specifying exactly that range!
When I set 2 as start, and I leave 150 as end, I get a popup saying the DHCP limit address should be greater then the start address!
When I change it to 50, it's OK, but when I set it to 200, it also accepts it!? 

We have PPPoE running in the office here and I haven't noticed any issues. What modem do you have?

My ISP is Belgacom, I have a BBOX3.
I can use DHCP also, but I prefer PPPoE because I want my WAN-address to arrive directly at the A+, so I can bypass the modem entirely.
There's no problem once the connection is up, it just seems I have to set the username/password and then save it twice before it connects.
But as I've said, I'll try being a little more patient 

The connected devices in the LCD UI, I'm not sure, I'll check with the software team, as it's been like this for a while, it just haven't been that important to fix it.
Never had a problem with the WAN port not showing the IP address straight away, might be related to the PPPoE issue.

We'll wait this one out until the next firmware then 

We're aware of some of the issues between NutsOS and OpenWRT and we'll get those fixed. There are a few more you haven't spotted as yet 

Haven't gotten to test 'everything', I'm first trying to get the basics set 

As eldaria pointed out, the DHCP leases aren't cut off dead if the device is still connected at the end of the lease time, it just means that once it re-connects to the network, it'll be assigned a new IP address if it has been longer than the assigned period of time.

That's good to know.
Now just try explaining why they reset to over 12h 

[eldaria]

Your image is a little small (not clickable) to see what it says.
What is your DHCP range?

I originally did not put the big version, I accidentally linked the thumbnail, but I could click it at the bottom to get the big version, and Lars fixed it, is now big an nice.

Anyway:
IPv4 Address: 192.168.1.1
Netmask: 255.255.255.0
Start IP: 2
End IP: 200
Lease time: 12h

So this is an OpenWRT bug? Why should there be 2 places to define them...

No clue. But it would not be the first time you can configure something in two (or more) places.
You could also configure it through ssh and modify /etc/config/dhcp 

I've used spaces in the hostnames for years with my ISP's router without problems.
Also, when you set them in OpenWRT, it clearly says they are symbolical names, I'm guessing just to be able to identify the devices in the list, which seems logical.
If you need to use the hostname specified by the device (ie. android-asd548q35), it gets a little hard knowing which device it is.

Don't confuse DNS with DHCP, although they are often configured in the same place and are usually working together they are not the same thing.
A DHCP server does not assign a Hostname to a client, it can either retrieve it from the client as part of a DHCP IP request and then pass it to the internal DNS server, or a router can configure DNS name in the DNS server when you configure a static lease.

And a router allowing a hostname to have a space in it will not make the rest of the network know what you are trying to do, and is sure to give troubles eventually, especially if the router tries to resolve it.
I suspect that if a router allows a space, then it is not really a hostname but just a name of the Static lease, I wonder though what it would pass on to the internal dns server if you have a space in the configured hostname.

I did not know that 
I have 2 Foscam-cameras that don't appear to go below 12h50min.  So that would mean they renew every 10 minutes?

Likely, but I would say that is a bug in Foscams software, spamming the network with DHCP request every 10 minutes is unnecessary.

Thanks for taking the time to reply! 

You are welcome.

[Fire69]

No clue. But it would not be the first time you can configure something in two (or more) places.
You could also configure it through ssh and modify /etc/config/dhcp 

I tried doing it through /etc/config/dhcp, but by default only vi is installed as text editor, and that is just a horrible program 

Don't confuse DNS with DHCP, although they are often configured in the same place and are usually working together they are not the same thing.
A DHCP server does not assign a Hostname to a client, it can either retrieve it from the client as part of a DHCP IP request and then pass it to the internal DNS server, or a router can configure DNS name in the DNS server when you configure a static lease.

And a router allowing a hostname to have a space in it will not make the rest of the network know what you are trying to do, and is sure to give troubles eventually, especially if the router tries to resolve it.
I suspect that if a router allows a space, then it is not really a hostname but just a name of the Static lease, I wonder though what it would pass on to the internal dns server if you have a space in the configured hostname.

I'm not confusing the both.
I set my static leases with a comprehensive name, but that was, as you said, only for naming the lease.
For example, I could set my printer as 'Printer Samsung Wifi', but to ping it, you'd have to use the actual hostname, CLX-3185W.lan

I suspect the hostname you specify on the A+ is also just for information.

Likely, but I would say that is a bug in Foscams software, spamming the network with DHCP request every 10 minutes is unnecessary.

Very likely, that Chinese firmware has a few bugs in it too 

As a test, I changed the DHCP range to 2-200 and set my camera fixed to .7
Result, I can't contact the A+ anymore through my domain name.
I'm at work now, so I can't check the reason, but it's very likely DHCP stopped giving out addresses again.
Or it rebooted (which it has to do very often after saving a setting, is that normal??) and didn't connect my PPPoE... But I'm guessing it's the DHCP... 

[Fire69]

This thing is driving me crazier every day I try to get it working...

Yesterday, all of a sudden everything seemed to work.  I didn't know why, but hey, I was happy!
It didn't last long. 10 minutes later, my internet went down, I never managed to get it working again, although the LCDUI happily said internet was connected. I even tried reflashing R066, nothing...
So this morning I did a factory reset for the gazillionth time!
I left everything as it was, expect for the internet, which I changed through the LCDUI from DHCP to PPPoE.  It told me the internet was connected.  After that I had to leave home.
Now, about 5 hours later (it should have had more than enough time to connect, right?) I tried to connect through the app and the website.
It shows me the sensors, the router... offline.

I like playing with hardware, but this isn't fun anymore. 

[edit]
Got back home, checked the LCD, internet disconnected.
Went to Internet Settings, saved the existing settings a second time, internet is working...
Changed the SSID for 2.4 to Fire69 through the WebUI and pushed Save. Top of the page shows the files being modified, It gets stuck on /etc/config/firewall (for changing the SSID??)
After a couple of minutes I just clicked on the Home-icon to get out of the menu. Result, I had a router that sent out the SSID as Fire69, but in the menu still showed the default Almond-xxxxx.  Had to go into OpenWRT and save it there again to get this fixed...

Is there a date in sight for the next firmware release?

[Fire69]

Finally, after doing everything exactly the same for over a week now, my static leases and port forwards are working as expected.
I'm really hoping everything keeps working now!

I'm left with 1 question now.
I want to have port 80 forwarded to my server, but's it's being used by the A+ by default.
Can I somehow change this port?

[LGNilsson]

Not at the moment, no. It would be easier to forward something like say 8080 to the server.
Our office NAS is for example on 5000 as default.
That said, I've asked the software team to look into adding such an option in the future.