xxxxxxx kernel: [103550.155950] Shorewall:net2fw:DROP:IN=eth0 OUT= MAC= SRC=22.214.171.124 DST=xx.xx.xx.xx LEN=92 TOS=0x00 PREC=0x20 TTL=47 ID=0 DF PROTO=UDP SPT=3480 DPT=49085 LEN=72
The list below is per Dennis Peng 6/17/09:
I think we have compiled a comprehensive list or ports split by inbound and outbound.
53, 123, 514, 1194, 3480, 10000-20000
note: port 1194 is both in and outbound UDP.
If you don't have at least these ports open, I doubt everything would work. Also, I'm not so sure that I don't also get a regular entry in my firewall log because that's just the way it works; I quit worrying about it when ooma started to work and it didn't mess up my internet connection.
I believe an option to opening these ports for ooma is to put ooma in the router's DMZ.
I have my Ooma inside a pfSense firewall/router. Currently have outbound connections from the LAN to the WAN default allowed. The Ooma takes a minute or so to boot, and when finished, it shows a successful connection and I can make and receive calls.
However, I noticed that my firewall is rejecting some inbound packets from one of the ooma VPN servers to my gateway. The source port is 1194 and the destination is a high number.
I'm not sure why there are inbound connection attempts outside of a normal response to the outgoing connections. The Ooma documentation only explicitly mentions outbound ports here: ( https://www.ooma.com/app/support/advanc ... vice-ports ).
Should I configure my firewall to allow this inbound connection for optimal service?
I'll probably call Ooma support tomorrow about it, but I suspect it will take a while to get someone to break script and understand what I'm asking and get an answer so I decided to post here too.