Everything posted by ZappyZap
-
[Support] devzwf - Postfix-Relay
i dont really get you quetsion. you can use that with what ever you want as you configure your relay. and what is quite finicky ?
-
[Support] devzwf - Pihole Sync
Thanks for the report , i will take a look and fix Edit : This has been fixed
-
[Support] devzwf - Pihole Sync
You are correct this is used when you have 2 pihole server and you want to keep them in sync
-
[Support] devzwf - Postfix-Relay
@ksarnelli template updated to match the new Env variable added in v 1.3.0 Let me know
-
[Support] devzwf - Postfix-Relay
@ksarnelli Nice i saw you raise an issue and the developer said he will take it... https://github.com/loganmarchione/docker-postfixrelay/issues/8 as soon as he modify it i will update the template. remind me if i forgot. thanks
-
[Support] devzwf - Postfix-Relay
I am using https://github.com/loganmarchione/docker-postfixrelay i could probably do that , but it would require me to build the conatiner myself. I always priviledge the official container when it exist you could ask on the project see if he is willing to do so.
-
not able to have a clean shutdown since 6.11
well thanks for the update. I still have the same issue , sadly i cannot rebuild everything with new HW like you did
-
[Support] devzwf - CUPS-Airprint
I am using https://github.com/chuckcharlie/cups-avahi-airprint container in this template and it do not seem to be build to expose this dir. this dir (/user/lib/cups/filter/) do not exist in the conatiner , did you mean : /usr/lib/cups/filter if it is the latter , you can put you file in the container to test , but be aware that anytime the container will rerun you will have to reupload the file. or ask on https://github.com/chuckcharlie/cups-avahi-airprint for the inclusion of this file
-
[Support] devzwf - pihole DoT/DoH
I do not touch this part i am building on top of pihole official container who is setting this. perhaps better place to request this is : https://github.com/pi-hole/docker-pi-hole but i am fairly positive it is already random # Pi-hole: Update the ad sources once a week on Sunday at a random time in the # early morning.
-
[Support] [Depreciated] FlippinTurt PiHole DoT-DoH
Saw the template disapear from CA so i create one.... the support thread is : https://forums.unraid.net/topic/132037-support-devzwf-pihole-dotdoh/
-
[Support] devzwf - pihole DoT/DoH
Reserved
-
[Support] devzwf - pihole DoT/DoH
This repo was created to update the piHole DoT/DoH by flippinturt https://forums.unraid.net/topic/101615-support-depreciated-flippinturt-pihole-dot-doh/ Official pihole docker with added DNS-over-TLS (DoT) and DNS-over-HTTPS (DoH). DoH uses cloudflare (1.1.1.1/1.0.0.1) and DoT uses google (8.8.8.8/8.8.4.4). Config files are exposed so you can modify them as you wish e.g. to add more services. Application: https://hub.docker.com/r/devzwf/pihole-dot-doh Make sure to look at the complete documentation Please make sure you set a static IP for this docker, as DHCP will not work! FAQ: Q: Can this be installed on top of flippinturt's current pihole DoT-DoH? A: Yes, this can be installed over, without any problems Q: How do I change the hostname? A: Use the '--hostname namehere' parameter, under 'extra parameters' in the containers settings Please post any questions/issues relating to this template you have in this thread.
-
Monitoring réseau pour voir tout ce qui passe & FireWall...
la plupart de switch managed (enterprise grade) ont cette fontion. de maniere simplifie : ton server est connecter sur le port 5 ton host qui log et inspecte sur le port 12 tu "mirror" le port 5 sur le port 12 ce qui fait que tout ce qui passe par le port 5 est vu par le port 12..... de cette maniere le port 5 n'a aucun moyen de savoir qu'il est ecouter....
-
Monitoring réseau pour voir tout ce qui passe & FireWall...
1 - utilise une switch avec la methode de "taping" avec un ips/ids ou tout autre packet inspector 2 - un pfsense / opnsense
-
[Support] [Depreciated] FlippinTurt PiHole DoT-DoH
perhaps would be better for me to just create a new template.... will see
-
[Support] [Depreciated] FlippinTurt PiHole DoT-DoH
edit your actual flippinturt template (by left clicking on the container and go to edit) then replace the image as shown bellow and the docker hub url as well : https://hub.docker.com/r/devzwf/pihole-dot-doh
-
not able to have a clean shutdown since 6.11
i did boot with a fresh 6.11.5 and same issue
-
[Support] [Depreciated] FlippinTurt PiHole DoT-DoH
the github in on the readme if you want to check what i did thanks for confirming i have my 2 pi-hole instance working on this image since a week
-
[Support] [Depreciated] FlippinTurt PiHole DoT-DoH
yes actually , i did not yet bother to redo a template, i edit edit the flippinturt i had and change the image and woila. registry link : https://hub.docker.com/r/devzwf/pihole-dot-doh nothing fancy all the credit go to testdasi
-
[Support] [Depreciated] FlippinTurt PiHole DoT-DoH
I could not found the github repo for the rigth one to be honest. the docker hub repository is just the container , no readme, nothing else. No support forum etc... I was tempted t use that , but ..... because all the point above i did not Nothing against it , but i always tried to understand and know as much as i can what i am using
-
[Support] [Depreciated] FlippinTurt PiHole DoT-DoH
I have fix this issue, i create a image with the fix and plan to keep updating the image when new pihole version realease , but i am not sure what to do, create an other template or else... anyway using this for my own need so let me know
-
[Support] devzwf - Pihole Sync
Ok No problem I will still make a receiver i think just in case
-
[Support] devzwf - Pihole Sync
Ho this is the sender so for the primary i can creater a receiver template if you need ....
-
not able to have a clean shutdown since 6.11
i hope this is your backup and not your main storage.... If it is i hope you have a Good Backup ...... just in case
-
not able to have a clean shutdown since 6.11
Some update , I stop the array , so docker and VM are down .... same issue. Next , i will boot a fresh install of 6.11.x on a new stick and try to reboot i will try this week-end if i can and have time