Vera Firewall Ports to Leave Open

I’m using my Vera as a WAN router/firewall and noticed that while no ports are open, with the vera firewall on, a lot of ports remain closed and reject traffic, but I would rather they drop all packets and perform in stealth mode. So I’m adding some firewall rules in to block all traffic from ports 0-65535, except one random port which I will SSH in and tunnel to other addresses on my LAN.

Does anybody know what ports I need to leave open as to not interfere with the findvera service, or any other ports Vera may need that I’m not aware of?

I also want to disable ping replies, anyone know how to do that, and will that screw interfere with any findvera stuff?

I found some service port numbers on the wiki, but I assume they are for the internal LAN.

For the findvera service to work with your box you don’t need to open any ports on it, just leave the box to make outbound connection to our servers.

Not all users allow any kind of outbound connections if you have any sense. I have been dealing with the same problem with Vera-2 insofar it trying to communicate out on a number of out bound ports, for those that are interested I have discovered Vera-2 communicates on the following ports.

37-TCP Outbound Time sync, if you don['t have this open then the unit defaults to year 2000 1 Jan, you can SSH to the uinit and manually set the time and date but this is a pain to have to do each time your box is restarted for any reason, I allowed outbound only connection on this port which solved my problem.

TCP Port 232 & 80. Vera appears to do most of its main secure communications on port 232, looking through the server config files I see that if it can’t open a connection on port 232 it may try port 23 instead, but I’ve not actully seen it try this in my wireshark logs.

I also opened outbound ports TCP/UDP ports on 10123 because I read someone said the time setter try’s to use this port , but I found no evidence that it did and it did not resolve my problem with the clocks not being reset correctly until I opened a outbound TCP connection on port 37.

Well this has been my experience so far, I hope it helps others.