Messages

Now i fixed it

http://itsecforu.ru/2018/02/26/opnsense-%d0%be%d1%88%d0%b8%d0%b1%d0%ba%d0%b0-%d0%b7%d0%b0%d0%bf%d1%83%d1%81%d0%ba%d0%b0-configd/

Version 17.7

In syslog :" Failed to connect to configd socket: Connection refused while  execution filter list count json"

Have you also rebooted the server and does configd start when you do that?

- Yes, I did it

If it does start, does it fail after a period of time?

- After 3 days it does not start

BTW, as you've posted in English I'd suggest this may have been better posted in the English language section as not many English speakers are likely to visit the Russian forum.

How can I replace this topic ?

any ideas?

Hello

opnsense worked normally.

A few days ago i got the problem with configd

I mean: Do I need to make Firewall rules how u show it in tutorial or I can disable it and Ipsec will work?

Need  I surely make Firewall Rules Site A & Site B for using Ipsec , or I can disable all packet filtering?

Now I fix it. :D Problem was with ip address ob debian.

But now i got other one :D

I can ping remote opnsense's wan interface but cant ping lan ? any ideas how to tune it?

Will it works, if I use opnsenses without Internet connection? I connect them through gw ( debian ):




and I use gw for WAN interfaces 192.168.2.150 and 10.8.10.5 ip-adresses respectively. Would it work correct ?



in file /etc/defaults/rc.conf :

gateway_enable = "NO"

Is it ok?

Unlocked privates and bogon networks and disabled all packet filtring

from arm2 i can ping Wan interface of Opnsense2 10.8.10.6/30, but cant ping 10.8.10.5/30 interface of gw.

Mb u know where should I check something?

I got :

arm1 - Opnsense1 - gw - Opnsense2 - arm2

when i try ping from arm1 to arm2 i see messages about loss packets: Time to live exceeded

Hello ! When i try
# opnsense-update -ifu -r 17.7 -l /root

output : Missing origin.conf

GREAT! thx A ALOT
8) 8) 8) 8)

again doesnt work  :(