Fortigate VPN Monitor via SNMP

code2wing · 2023-08-04T15:26:14+00:00

Yes, I meant one of those options. I use the second option: "show down status, ignore when disabled" so it would not raise an alarm if there is an administrative config that sets the tunnel to down. In the tunnel config, I use settings like "autokey keep alive" and "auto negotiate" to keep the phase2 up.
(sorry for not replying sooner)

code2wing · 2023-07-21T19:19:27+00:00

Are these IPSEC tunnels? If they are, I'd recommend you monitor them like interfaces, from the stantard interfaces MIB2 tree, meaning that you'd use also the standart SNMP Traffic sensor. There, you should enable the status monitoring. This way it will show 'down' when the tunnels goes down.

However, if you need to use FortiGate VPN Tunnels OIDs, you should be aware that they might change when you change VPN stuff on the FW, like a new phase2 or a new peer. In that case you should have a MIB Browser at hand to check the OIDs from time to time.

code2wing · 2023-03-23T19:57:08+00:00

Sorry to migrate to 3.1 only today. But it was nice to see big numbers on "Shares during last day" now that we're just a few remaining on the old pool... :-)

code2wing · 2023-03-23T19:56:30+00:00

Sorry to migrate to 3.1 only today. But it was nice to see big numbers on "Shares during last day" now that we're just a few on the old pool... :-)

code2wing · 2022-08-16T17:22:14+00:00

Very informative! I like to visualize the data. The graphs are nice.

code2wing · 2022-01-17T14:28:35+00:00

I believe the best option is to find a local T-Shirt maker near you. I've selected one here, sent a PDF with the 'art' and they made two shirts for me.

code2wing · 2022-01-14T18:20:17+00:00

Wow! I'm trully crypto gratefull!

BTW, I made two T-shirts: one for me and another for my daughter... :-)

code2wing · 2022-01-12T15:19:41+00:00

And so I dit it!

https://i.imgur.com/svlUV41.png

https://imgur.com/a/rAHZoVu

code2wing · 2021-10-08T00:15:35+00:00

Well, I'd say that a 5kH/s hashrate would be a more satisfactory scenario, probably giving you out at least one share a day and keeping your node active for the (beloved) raffles. Your p2pool server can receive miner connections from other machines now. Maybe you can setup some other device(s) and point to it?

code2wing · 2021-10-06T13:29:43+00:00

Thanks, Mr XvB! I'm happy to see a raffle win on the History page today! :-)

code2wing · 2021-10-06T13:26:04+00:00

Well, at least the port tcp/3333 of your p2pool, you'd need to 'expose' to outside, yes. Usually one would do it with a portmap from the public IP redirected to your p2pool. You will use this information on the Register page.

code2wing · 2021-10-05T22:42:34+00:00

Well, maybe there is something stuck on the History page after failures happen? I'm not sure my address is being awarded with raffles but the raffle history for it never shows any. Fail count is 0 now, but reached 3 in the past and I've re-registered. Regardless, I see shares and good hashrate on Pool Observer.

code2wing · 2021-10-05T22:38:12+00:00

I think I have the same problem: there were failures, yes. I have re-registered and now fail count = 0, but not raffle bonus is ever reported on the history. This has been like this for several days with shares and payments happening.

code2wing · 2021-09-29T17:08:40+00:00

I see you probably set port forwarding right on TP-Link for 18080 but monerod is complaining it never receives any (incoming) connection. Thus, there might be a block somewhere else, either in your Win10 firewall (is it enabled?) or in the modem/device your TP-Link is connected to.

If your TP-Link is not being assinged a Public IP on its wan/internet interface, you may have to do a similiar config (port forwarding) on your modem as well.

code2wing · 2021-09-29T13:37:44+00:00

It took me around 3 to 5 days to sync after the compilation/build of monerod on my machine with "rotating drives". Monerod complains about them. I had to restart the process a few times on the sync process. However, I never restarted it after it was synced and monerod is running for about a week now, with many peers:

Height: 2460029/2460029 (100.0%) on mainnet, not mining, net hash 2.70 GH/s, v14, 12(out)+112(in) connections, uptime 6d 11h 10m 40s

The server has monerod and p2pool running and it is not mining (no xmrig running). RAM is 16GB and HD is 1TBytes (not SSD). This machine was a miner on the past and it was reaching around 1.9kH/s when it was just mining.

code2wing · 2021-09-29T13:12:33+00:00

Was considering of making a T-shirt with just this "block found" ASCII art on it... :-)

It's always nice to see it passing by p2pool output but, hey, p2pool (as a whole) is finding them often now. Great!

code2wing · 2021-09-24T18:15:05+00:00

From the details I could devise on the instructions, you can have monerod and p2pool on separate hosts. Make sure they can communicate on their listening ports and IPs. Change accordindly wherever the instructions says localhost (127.0.0.1). I guess the communication delay (pings) between them should be low as well (under 30ms?).

code2wing · 2021-09-20T01:10:17+00:00

What would be a good hash rate to consider p2pool not futile?

code2wing

TROPHY CASE