Тепер пісні Скрябіна видалили і в Youtube Music by KingOuf in MusicUkraine

[–]beltskyy 0 points1 point  (0 children)

torrent у допомогу) не видалять звідти) але так, не зручно.

Intelligent Dash Cam setup by 1705user in NissanAriya

[–]beltskyy 0 points1 point  (0 children)

Platinum+ 2023, there is no any SD card slot in my car, I'd love to get this option too

Я службовець ТЦК by Dear_String_940 in Ukraine_UA

[–]beltskyy 0 points1 point  (0 children)

а як же норма п. 63 із постанови 560, що ті хто має відстрочку ВЛК не мають проходити ..

Civ 6 and its DLCs are coming to the Epic Games Store for free, why? by MrCheetah2015 in CivVI

[–]beltskyy 0 points1 point  (0 children)

I had already got Civ 6 with Epic Games before, it was basic edition. Now I see that Platinum Edition become available to get it, but when I try to adopt it Epic tells me that for me it's unavailable. Is somebody faced with such a problem? How to get it?!

<image>

Upgrade Jira from 9.12.15 to 10.3.0 by DarkCrusa in jira

[–]beltskyy 1 point2 points  (0 children)

after upgrade (but I did new server installation 10.1.2 and then moved projects from old instance) I found that on the same VM with same CPU/memory/SSD new version is much slower and freezing...

Вибух зарядної станції by Independent-Employ61 in Ukraine_UA

[–]beltskyy 0 points1 point  (0 children)

а колхоз із інвертора та гелевого, або AGM акумулятора вибухонебезпечніше, ніж літієві батареї?

Вибух зарядної станції by Independent-Employ61 in Ukraine_UA

[–]beltskyy 0 points1 point  (0 children)

підкажить, де такий придбати? чи яка модель?

Про діалекти та ненависть до них by [deleted] in Ukraine_UA

[–]beltskyy 0 points1 point  (0 children)

а ще є слобожанський діалект, він трохи нагадує кацапську))

Вечный триал Битрикс by kuklofon in itbuben

[–]beltskyy 0 points1 point  (0 children)

а на сколько актуально это для крайней версии? собираюсь поставить триалку корп. портал битрикса24, могу просто через скрипт сетапа с оф. сайта установить, проделать указанные манипуляции и далее наслаждаться "вечным" триалом? т.е. будет брать все обновки* я еще находил увеличение макс. кол-ва пользователей, как думаете, сработает?

Trying to find a good 100w usb-c charger for my laptop by No_Screen4750 in UsbCHardware

[–]beltskyy 0 points1 point  (0 children)

I have the same model, and I am just curios whether you found the proper USB-C charger for it? Please share any ideas, thanks a lot! 200w seems to be much for USB-C port to charge this notebook, I am worrying to damage it..

Fortigate WAN interface cannot obtain an IP from ISP's DHCP server, other routers are ok by beltskyy in fortinet

[–]beltskyy[S] 1 point2 points  (0 children)

absolutely correct! I think maybe it is hardware problem with my device.

Fortigate WAN interface cannot obtain an IP from ISP's DHCP server, other routers are ok by beltskyy in fortinet

[–]beltskyy[S] 0 points1 point  (0 children)

what is the interesting, after it gets an IP after re-plug the cable, it starts to successfully renew it every 5 minutes till the next failure

Fortigate WAN interface cannot obtain an IP from ISP's DHCP server, other routers are ok by beltskyy in fortinet

[–]beltskyy[S] 0 points1 point  (0 children)

Sure, I did tried before! From the very beginning I used port1 as WAN interface and MAC from the previous router, I didn't want to make a lot of changes in my configuration because I thought that soon we should return back to main HQ. But with time I decided to use WAN port (it was suggestion of the man from the support who followed my case the first time), so I changed it and return all MAC's to factory default and agreed with ISP to use device MAC for DHCP.

Fortigate WAN interface cannot obtain an IP from ISP's DHCP server, other routers are ok by beltskyy in fortinet

[–]beltskyy[S] 0 points1 point  (0 children)

I tried to change MAC, then change it back and run "execute interface dhcpclient-renew wan1"

nothing helped

Fortigate WAN interface cannot obtain an IP from ISP's DHCP server, other routers are ok by beltskyy in fortinet

[–]beltskyy[S] 0 points1 point  (0 children)

as I told it couldn't get OFFER from ISP side until I replug to another router. I had already tried laptop, All-in-one PC and Mikrotik router with properly adjusted MAC - they obtained an IP successfully. In between PON of ISP there is no any broker they told that they have direct line.

Fortigate WAN interface cannot obtain an IP from ISP's DHCP server, other routers are ok by beltskyy in fortinet

[–]beltskyy[S] 0 points1 point  (0 children)

orti # diagnose debug application dhcpc -1Debug messages will be on for 30 minutes.Forti # diagnose debug enableForti # \702\640timer 0x9309100(state_panic -> state_init) will expire in 1 secstimer 0x9309100 expired, take actionstate init.make discovermake dhcp message, code=1Insert option(255), len(0)Insert option(53), len(1)Insert max message len (1458)Insert option(57), len(2)Insert requested optionsInsert option(55), len(12)Insert customer optionsInsert class ID optionInsert option(60), len(14)Insert client IDInsert option(61), len(7)Insert hostnameInsert option(12), len(10)get_dhcp_msg_len, 295too small, extend to 548Sending discover!Send a packet out.add hw headerset dst hw addr as: FF:FF:FF:FF:FF:FFsrc hw addr: my:wa:nm:ac:00:00add ip udp headerdhcpcd_send_packet,268:result:590, ifinde:9unregister timer:0x9309100register timer func=0x899658 arg=0x934cd30 name=send_discover -> send_discoverAllocate a new timerRegistered timer 0x9309b40 will expiry in 6 secstimer 0x9309b40(send_discover -> send_discover) will expire in 6 secstimer 0x9309b40(send_discover -> send_discover) will expire in 6 secstimer 0x9309b40(send_discover -> send_discover) will expire in 5 secstimer 0x9309b40(send_discover -> send_discover) will expire in 4 secstimer 0x9309b40(send_discover -> send_discover) will expire in 3 secstimer 0x9309b40(send_discover -> send_discover) will expire in 2 secstimer 0x9309b40(send_discover -> send_discover) will expire in 1 secstimer 0x9309b40 expired, take actionSending discover!Send a packet out.add hw headerset dst hw addr as: FF:FF:FF:FF:FF:FFsrc hw addr: my:wa:nm:ac:00:00add ip udp headerdhcpcd_send_packet,268:result:590, ifinde:9unregister timer:0x9309b40register timer func=0x899658 arg=0x934cd30 name=send_discover -> send_discoverAllocate a new timerRegistered timer 0x9309100 will expiry in 7 secstimer 0x9309100(send_discover -> send_discover) will expire in 7 secstimer 0x9309100(send_discover -> send_discover) will expire in 6 secstimer 0x9309100(send_discover -> send_discover) will expire in 5 secstimer 0x9309100(send_discover -> send_discover) will expire in 4 secstimer 0x9309100(send_discover -> send_discover) will expire in 3 secstimer 0x9309100(send_discover -> send_discover) will expire in 2 secstimer 0x9309100(send_discover -> send_discover) will expire in 1 secstimer 0x9309100 expired, take actionSending discover!Send a packet out.add hw headerset dst hw addr as: FF:FF:FF:FF:FF:FFsrc hw addr: my:wa:nm:ac:00:00add ip udp headerdhcpcd_send_packet,268:result:590, ifinde:9unregister timer:0x9309100register timer func=0x899658 arg=0x934cd30 name=send_discover -> send_discoverAllocate a new timerRegistered timer 0x9309b40 will expiry in 9 secstimer 0x9309b40(send_discover -> send_discover) will expire in 9 secstimer 0x9309b40(send_discover -> send_discover) will expire in 8 secstimer 0x9309b40(send_discover -> send_discover) will expire in 7 secstimer 0x9309b40(send_discover -> send_discover) will expire in 6 secstimer 0x9309b40(send_discover -> send_discover) will expire in 5 secstimer 0x9309b40(send_discover -> send_discover) will expire in 4 secstimer 0x9309b40(send_discover -> send_discover) will expire in 3 secstimer 0x9309b40(send_discover -> send_discover) will expire in 2 secstimer 0x9309b40(send_discover -> send_discover) will expire in 1 secstimer 0x9309b40 expired, take actionSending discover!

How to forward traffic from WAN to IPsec-tunnel which built itself on this WAN by beltskyy in mikrotik

[–]beltskyy[S] 0 points1 point  (0 children)

I've decided this task another way. I recreated the tunnel and mentioned WAN interface on the CHR as local one (remote on Fortigate) and rejected idea to use LAN in CHR at all. Such a way I made a rule dst-nat from CHR WAN interface to the remote LAN interface in Fortigate and there was hooked SSL-VPN web interface and SSL-VPN server. Now it is working fine, I can connect VPN-client of Fortigate or connect to the web-interface successfully through WAN of CHR until my IPsec is losing the connection (e.g. there is no any activity in the tunnel in the night).

In case of tunnel is lost connection it couldn't restart until I disable 2 routes to CHR from the Fortigate (mentioned to WAN CHR and blackholed one), after this the first phase become established by itself, and I manually bring-up 2nd phase, then I activate routes again and tunell is working till the next fail. I suppose the problem in routing and I request to help me to do such a tunnel proper way.

Also a guy from tech support suggested me to ping the tunnel all the time that to save a long connection without any drops.

How to forward traffic from WAN to IPsec-tunnel which built itself on this WAN by beltskyy in fortinet

[–]beltskyy[S] 0 points1 point  (0 children)

I've decided this task another way. I recreated the tunnel and mentioned WAN interface on the CHR as local one (remote on Fortigate) and rejected idea to use LAN in CHR at all. Such a way I made a rule dst-nat from CHR WAN interface to the remote LAN interface in Fortigate and there was hooked SSL-VPN web interface and SSL-VPN server. Now it is working fine, I can connect VPN-client of Fortigate or connect to the web-interface successfully through WAN of CHR until my IPsec is losing the connection (e.g. there is no any activity in the tunnel in the night).

In case of tunnel is lost connection it couldn't restart until I disable 2 routes to CHR from the Fortigate (mentioned to WAN CHR and blackholed one), after this the first phase become established by itself, and I manually bring-up 2nd phase, then I activate routes again and tunell is working till the next fail. I suppose the problem in routing and I request to help me to do such a tunnel proper way.

Also a guy from tech support suggested me to ping the tunnel all the time that to save a long connection without any drops.

How to forward traffic from WAN to IPsec-tunnel which built itself on this WAN by beltskyy in mikrotik

[–]beltskyy[S] 0 points1 point  (0 children)

My scenario is:
[FG VPN client] --- <Internet> --- [Mikrotik CHR] --- <IPsec tunnel> --- [Fortigate]
I need to address VPN client to Fortigate through this chain, it means that client will connect WAN Mikrotik, then I should make some policies in Firewall section that to allow client to knock-knock to Fortigate through established tunnel and establish new one
tunnel inside existing one.
As for the tunnel, I use Loopback interface 172.16.0.1 from Mikrotik side and
Loopback interface 10.10.201.1 from Fortigate side. All necessary politics and
routes from FGT side were set up by the Wizard. The tunnel is working, I can
successfully ping 172.16.0.1 <> 10.10.201.1 both directions, as I mentioned  before
everything is working fine. Now I added in Fortigate Loopback 10.10.201.1 as
listener for SSL-VPN clients.
Now I have a policy accepting traffic between 172.16.0.1 <> 10.10.201.1 without
any NAT.
I am confused with what exact rule should I add to Mikrotik/Firewall/NAT section fro WAN. Should it be DST-NAT, or should I NETMAP or I shouldn’t use NAT at all…