Moblie IPSec Status
-
I just went ahead and committed the changes to a new dashboard package, 0.7.6. Go to System > Packages, click the Installed Packages tab, then click the reinstall button (says "pkg") next to the Dashboard entry.
Let me know if that is any different.
It still works fine for me.
-
here is the latest scoop! It's now works. I see two moblie connections. The count is right now but there is one that is showing up disconnected; but it is actually one fo the 2 moblie connections. One of them is a DDNS entry and that one is showing up as moblie instead of static connection.
The othe item is that is is not pull the correct description. Last but not least I can't ping anything accross the tunnel. I will reboot my laptop later today and will test again.
Again I will state there is nothing like PF-Sense on the market. It is one of the best products around. I just look forward until they get 2.0 finalized. the current product is great but 2.0 is going to be incredible.
Thanks to the entire team
RC -
Ah… I bet that dynamic dns will put a kink in the status no matter what, since the status looks for an IP Address and not a hostname.
I'll see if I can find a way to work around that one.
-
Ok. I think I have this fixed. I made a host-based tunnel and it worked for me.
I committed Dashboard 0.7.6.1 which should show up in a few minutes. Reinstall it and try one more time.
-
Jimp,
Everthing is working like a charming. ;D It is reporting all the connections correctly. It is awesome! ;DI like the fact that is now reporting moblie client, If I setup say 5 to 8 people using Shrew clients my status is going to report 8 moblie clients. Is there a way to add description or use the identifier to show up in the status tab.
My intend now is to get a few people I know to start using secure VPN connections back to my site for data storage. I just would like to be able to look at a glance to see whom is connected.
This is just a thought. The new widget is working like a charm.
Many thanks to all the developers whom are working on this product. It only seems like it is getting better and better.
RC
-
I don't think it can use the identifier, just the endpoint IP addresses. There may be another way to extract tunnel information that I'm not aware of, but the commands I'm aware of only print out IP addresses and some other related info, but no identifier.
You can look at the output of:
setkey -Dand
setkey -D -PThere is plenty of info there, but none of it is the identifier :)
Good to hear that it's working well for you otherwise!
-
Many thanks and great job.
RC -
Like a charm, nice job!
-
It would be nice if you removed the "Note: You can configure your IPSEC here." message. If you didn't know where to configure IPSEC you'd probably not be interested in that particular widget anyway.
Been using it for a couple of days now and I still like it :)
-
It would be nice if you removed the "Note: You can configure your IPSEC here." message. If you didn't know where to configure IPSEC you'd probably not be interested in that particular widget anyway.
Been using it for a couple of days now and I still like it :)
I'll consider that for the next update. I can't say I've ever clicked that link, but some people may find it useful…
-
It would be nice if you removed the "Note: You can configure your IPSEC here." message. If you didn't know where to configure IPSEC you'd probably not be interested in that particular widget anyway.
Been using it for a couple of days now and I still like it :)
I'll consider that for the next update. I can't say I've ever clicked that link, but some people may find it useful…
I removed that link (actually, moved it to the widget title) in the current version, which should be up now.
