1
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
Russian - Русский / Re: Cant start configd
« on: February 26, 2018, 09:21:23 am »
Version 17.7
In syslog :" Failed to connect to configd socket: Connection refused while execution filter list count json"
In syslog :" Failed to connect to configd socket: Connection refused while execution filter list count json"
Quote
Have you also rebooted the server and does configd start when you do that?- Yes, I did it
Quote
If it does start, does it fail after a period of time?- After 3 days it does not start
Quote
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 ?
5
Russian - Русский / Cant start configd
« on: February 21, 2018, 04:19:42 pm »
Hello
opnsense worked normally.
A few days ago i got the problem with configd
opnsense worked normally.
A few days ago i got the problem with configd
6
17.7 Legacy Series / Re: Time to live exceeded
« on: September 04, 2017, 12:57:15 pm »
I mean: Do I need to make Firewall rules how u show it in tutorial or I can disable it and Ipsec will work?
7
17.7 Legacy Series / Re: Time to live exceeded
« on: September 04, 2017, 09:47:52 am »
Need I surely make Firewall Rules Site A & Site B for using Ipsec , or I can disable all packet filtering?
8
17.7 Legacy Series / Re: Time to live exceeded
« on: August 31, 2017, 01:18:50 pm »
Now I fix it. 
Problem was with ip address ob debian.
But now i got other one
I can ping remote opnsense's wan interface but cant ping lan ? any ideas how to tune it?
Problem was with ip address ob debian.But now i got other one
I can ping remote opnsense's wan interface but cant ping lan ? any ideas how to tune it?
9
17.7 Legacy Series / Re: Time to live exceeded
« on: August 30, 2017, 01:24:08 pm »
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?
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?
10
17.7 Legacy Series / Re: Time to live exceeded
« on: August 30, 2017, 12:31:59 pm »
Unlocked privates and bogon networks and disabled all packet filtring
11
17.7 Legacy Series / Re: Time to live exceeded
« on: August 30, 2017, 11:01:58 am »
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?
Mb u know where should I check something?
12
17.7 Legacy Series / Time to live exceeded
« on: August 29, 2017, 05:58:02 pm »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
13
17.7 Legacy Series / Missing origin.conf
« on: August 29, 2017, 10:29:42 am »
Hello ! When i try
# opnsense-update -ifu -r 17.7 -l /root
output : Missing origin.conf
# opnsense-update -ifu -r 17.7 -l /root
output : Missing origin.conf
14
17.7 Legacy Series / Re: incorrect display browser
« on: August 28, 2017, 04:16:57 pm »
GREAT! thx A ALOT
15
17.7 Legacy Series / Re: incorrect display browser
« on: August 28, 2017, 03:56:49 pm »
again doesnt work
