[GH-ISSUE #59] Limiting network access by network and host #43

New issue

Closed

opened 2026-02-26 05:31:08 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 05:31:08 +03:00

Owner

Originally created by @peterfroehlich on GitHub (Mar 28, 2013).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/59

This tool is really awesome, I would love to use it in the production environment of my company.
Whats holding me back is the lack of encrypted messaging (other ticket -> https) and being unable to configure defined networks and hosts that are allowed to connect as client or viewer. This goes above the simple ability of choosing which address to listen to.

Maybe something like that in the web_server.conf:
access : [ "192.168.0.0/24", "10.10.0.0/16, "8.8.8.8/32" ]

Originally created by @peterfroehlich on GitHub (Mar 28, 2013). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/59 This tool is really awesome, I would love to use it in the production environment of my company. Whats holding me back is the lack of encrypted messaging (other ticket -> https) and being unable to configure defined networks and hosts that are allowed to connect as client or viewer. This goes above the simple ability of choosing which address to listen to. Maybe something like that in the web_server.conf: access : [ "192.168.0.0/24", "10.10.0.0/16, "8.8.8.8/32" ]

kerem closed this issue

2026-02-26 05:31:09 +03:00

kerem commented

2026-02-26 05:31:09 +03:00

Author

Owner

@msmathers commented on GitHub (Mar 29, 2013):

v0.3.3 now supports IP whitelisting in web_server.conf, like so:

restrictHTTP: [
  "192.168.34.34",
  "10.0.1.*",
  "234.*"
]

That IP list is converted directly into a regular expression, which is applied to the inbound request's IP address. So while you can't use subnet masks, any valid regular expression will do.

Feel free to reopen this issue if that doesn't suffice.

@msmathers commented on GitHub (Mar 29, 2013): v0.3.3 now supports IP whitelisting in web_server.conf, like so: ``` restrictHTTP: [ "192.168.34.34", "10.0.1.*", "234.*" ] ``` That IP list is converted directly into a regular expression, which is applied to the inbound request's IP address. So while you can't use subnet masks, any valid regular expression will do. Feel free to reopen this issue if that doesn't suffice.

kerem commented

2026-02-26 05:31:09 +03:00

Author

Owner

@peterfroehlich commented on GitHub (Apr 5, 2013):

Awesome, thanks! :)

@peterfroehlich commented on GitHub (Apr 5, 2013): Awesome, thanks! :)