I shall try your suggestions tomorrow, but i see that there is a "pixelserv-tls" that does https.
I found the following links:
How-To: build pixelserv-tls for 32-bit x86 in 64-bit amd64 environment
Create and Import the CA Certificate
I am busy reading this for now, but you will probably have it implemented before i am done reading...
In the ad_poison.conf it is listed as - address=/doubleclick.net/192.168.88.1
I have checked both http:// and https:// and both give me the same "Connection has timed out"
Searching for "Doubleclick.net" i see that it is https://doubleclick.net.
Wgen i then click on the link to go to that page, i get the same "Connection has timed out"
netstat -npl | grep "84 "
tcp 0 0 192.168.2.1:84 0.0.0.0:* LISTEN 10679/perl
I checked ClearOS process viewer and pixelserv is running as 10679.
Yes, i updated ad-poison.conf to point to 192.168.88.1 then restart dnsmasq
It seems to be working as i don't get any ads on any mobile device apps anymore, this was woring even when i pointed to 192.168.2.0
The only part that has not been working it that i do not get the pixelserv page when i check with http://doubleclick.net, i just get a page timeout.
Now this might not be an issue, but it seems that this has intredused a delay in some pages loading
I have updated it as you have indicated.
iptables -nvL PREROUTING -t nat
Chain PREROUTING (policy ACCEPT 7105 packets, 1981K bytes)
pkts bytes target prot opt in out source destination
0 0 DNAT tcp -- eth1 * 0.0.0.0/0 220.127.116.11 to:192.168.2.1:84
Was ther eve a resolution for this one?
I have the same issue, when i don't have internet access, it takes a very long time to login to my ClerOS box.
Even using WinSCP, same issue.
When i have internet access, it is fast almost imedeate, but without internet access it takes forever and even timeout.
Thank you for all the help, but i am at the point where, so my data is gone... deal with it...
I am prepared to start from scratch, about 4TB will be lost, i think i can get most of it back over time from other sources, it might just take some time.
I still have the issue where on every reboot, the raid - /var/sd[abcefgijkl] is not the same as the next.
This is what seems to be the issue - we got side tracked trying to recover the data after the reboot and i loaded data on the drive.
Any idea how i resolve my original issue?
I created a mdadm.conf file, this is the content
ARRAY /dev/md/0 metadata=1.2 name=Zodiac.lan:0 UUID=785c89de:1d355c46:9b116951:21d6c4b3
And it booted into emergency mode again?