Issues with set-up, Satellite connection

Hi All
Just a shot in the dark to see if anybody is using a High Latency Internet connection. The first configuration I tried was this:
1. Hook Vera to my own router (Linksys WRT54G)
- I was able to talk to Vera but Vera complained that it could not connect to “FindVera.com” when I was registering for my installation.
- I was able to set-up devices and create scenes.
- I sent an e-mail about my problem to Micasaverde and their reply was that I had a high lag time issue and dropped packets when performing pings. The lag issue is explained by my satellite connection and I told them that. The dropped packets is new.
- Micasaverde said to take my Linksys router out of the loop and try that.

  1. Use Vera as the router (Linksys router out of the net.)
  • Vera box seems happy (“ON” light is steady)
  • When I use Findvera.com it does not see my Vera box even though I have a internet connection going through it. (I get the gray box on the web page saying it does not see Vera on my net.
  • I tried local.findvera.com but I can’t get a connection. I tried the suggested IP address but again failed.

My equipment: windows XP pro SP3, IE8, satellite eq: WildBlue

Any ideas? Anybody else have a similar set-up?

Randy

Hi again
more info
Vera firmware: was .602 now .608 same issues.

Randy

I think my Ticket # is 768

Ouch…
The fact findvera can’t see Vera behind your router most likely means SPI firewall expires connection before findvera connects to Vera. I remember similar issues in VoIP, with good router you can tune your TCP and/or UDP timeout values to keep connection alive for more time.

If I had to deal with such internet connection I’d first of all get a decent router that can be flashed with Tomato, or dd-wrt. Since you’re on G speed Asus 520GU would be my first choice. Putting Vera instead your router is fine as long as you feel comfortable with Kamikaze UI and dealing with the rest in CLI mode… I don’t.

Update…

I found the IP address of the Vera box ( 70.41.196.1 ) when in configuration 2 (see previous messages) but I could not get a connection using IE8 or Firefox. So now I’m back to Config 1 with the Linksys box. At least I can talk to the Vera box locally but I wish I had known about the limitations with Findvera.com and high latency before buying the box. Still don’t know why it is dropping packets when it talks to the internet. No dropped packets when comunicating locally.

Hopefully Micasaverde is working on this.

The vera box is now updated with the latest firmware. -Randy

Update…

I’m now connecting to Vera as the router in my net. I had to configure the firewall and DNS on Vera to fix the issue and assign the right net IP address to Vera. But the original issue remains in that I can’t get a SSH connection from Vera to findvera.com possibly due to the max packet size of 1500 bytes limitation of my satellite ISP and possibly the high latency.

It’s curious that I can get a SSH connection from my PC to MCV’s tech support to create a support ticket.

-Randy

[quote=“randy345, post:6, topic:164571”]It’s curious that I can get a SSH connection from my PC to MCV’s tech support to create a support ticket.

-Randy[/quote]
It’s made through a POST, not through an ssh connection. Your Vera access fine through https our servers, only the tunnels are affected.