ektus wrote:
I want to prevent 192.168.0.13 from having any internet access (except DNS and NTP, if I can't redirect the latter to my local time server).
If you want IP 192.168.0.13 to only have access to DNS and NTP, the rule should look like this:
The firewall works well, but it's an OpenWrt firewall.
I'll give you the type. The router itself acts as an NTP server, just enter the router's IP address into the client.
Turris Omnia with OpenWrt 21.02 - Tested
Linksys WRT3200ACM with Gargoyle 1.13.x
TL-WR1043ND v2 with Gargoyle 1.10.0
http://gargoyle.romanhk.cz custom builds by gargoyle users
ektus wrote:
I want to prevent 192.168.0.13 from having any internet access (except DNS and NTP, if I can't redirect the latter to my local time server).
If you want IP 192.168.0.13 to only have access to DNS and NTP, the rule should look like this:
The firewall works well, but it's an OpenWrt firewall.
I've yet to understand how the values are evaluated. If I say "no host", will the other rules do anything? Or should it be "any host" AND "port=52,123"?
In other words: Have all of the rules to be met to gain access, or has just one rule to be met?
RomanHK wrote:
I'll give you the type. The router itself acts as an NTP server, just enter the router's IP address into the client.
I'd like to, but this client (and at least two or three others, different ones) doesn't offer much in ways of configurability. I do have a local time server (some NAS) running anyway. But that doesn't help with clients that have external time servers hard-coded. So I could either just let that traffic through, or would have to dig deeper into firewall and routing to redirect it to the internal server.
ektus wrote:
In other words: Have all of the rules to be met to gain access, or has just one rule to be met?
Just one rule is enough - the rest is like default.
ektus wrote:
I'd like to, but this client (and at least two or three others, different ones) doesn't offer much in ways of configurability. I do have a local time server (some NAS) running anyway. But that doesn't help with clients that have external time servers hard-coded. So I could either just let that traffic through, or would have to dig deeper into firewall and routing to redirect it to the internal server.
Yes, I understand it.
P.S. Beware of a typo. No port 52 but port 53 for DNS and port 123 for NTP.
Turris Omnia with OpenWrt 21.02 - Tested
Linksys WRT3200ACM with Gargoyle 1.13.x
TL-WR1043ND v2 with Gargoyle 1.10.0
http://gargoyle.romanhk.cz custom builds by gargoyle users
ektus wrote:In language manager, when a second language is installed, the default language (english) can be selected, but the name isn't displayed in the list.
I've fixed this for future versions here: https://github.com/ericpaulbishop/gargo ... 00a333bbab
I had actually tried to fix this a while ago but must not have done a good job the first time. It looks like it works a little better now.
This will also improve the way the plugins page looks too (similar issue).
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Edit:
Tested many direct cables. (I dont have any cross cable, i will make a new one.)
Tested a new modem, i m sure its have gigabit port.
Still Amber.
I'll give you the type. The router itself acts as an NTP server, just enter the router's IP address into the client.
