Announce: new OPNsense community repository

Started by mimugmail, January 09, 2021, 10:39:06 AM

Previous topic - Next topic
You can also ask the Guys from AdGuardHome via GitHub If its even supported on BSD. We use their stock binary

Thanks for this. I am having an issue with the UniFi Controller software though. The UniFi Controller GUI is inaccessible after a fresh install.

I actually had it working fine on a test install on a different device, but with permanent device I tried fresh install of it and even with rebooting OPNsense, restarting and stopping service and daemon over and over, I cannot access the GUI at either 8080 or 8443 at all. I don't see any issues in logs, service appears started in status. Port scan shows 8080 in use.


Thanks. After doing that, I just checked to see if I could access before going further and it started working, so not sure why after several days it just worked, but it's good. WebRTC cloud access says 'connection failed" though, but I am used to seeing that on Windows based controller installs if 64-bit Java isn't installed, so perhaps this plugin is missing something that requires that to work, but I can work around that if need be.

Firstly, thank you for the repo and plugins, great idea.
I'm struggling to get Adguard working.
I'm on opnsense  21.1.3
I have:

  • Added the custom repo
  • Installed the plugin: os-adguardhome-maxit (misconfigured)
  • Enabled the plugin
When I browse to https://192.168.1.1:3000/ I get nothing. Any tips for things to check?

Thanks


Quote from: Walnut on March 13, 2021, 12:15:46 PM
Firstly, thank you for the repo and plugins, great idea.
I'm struggling to get Adguard working.
I'm on opnsense  21.1.3
I have:

  • Added the custom repo
  • Installed the plugin: os-adguardhome-maxit (misconfigured)
  • Enabled the plugin
When I browse to https://192.168.1.1:3000/ I get nothing. Any tips for things to check?

Thanks
Remove the S in HTTPS.

First of all, thx for the good work, i also owe you boobs and beer :)
I also have a problem with unifi. I guess in my case is because i use Sensei with Mongodb backend. After Unifi installation neither Sensei or Unifi works. I guess i will need more memory to install Sensei with Elasticsearch...
Proxmox enthusiast @home, bare metal @work.

Hm, I'd guess Sensei uses a different Mongo Version than unifi requires. Did I list Sensei as a limitation on my page?

March 14, 2021, 07:40:45 AM #54 Last Edit: March 14, 2021, 07:53:31 AM by Antaris
I can't see such limitation on https://www.routerperformance.net/opnsense-repo/
Anyway. Without Sensei i still can't access https://192.168.48.1:8080/ or http://192.168.48.1:8080/ either.
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
root     sshd       53839 4  tcp4   192.168.48.1:22       192.168.48.10:3039
root     ntpd       6828  21 udp4   *:123                 *:*
root     ntpd       6828  22 udp4   192.168.48.1:123      *:*
root     ntpd       6828  25 udp4   127.0.0.1:123         *:*
root     lighttpd   57208 4  tcp4   127.0.0.1:43580       *:*
_flowd   flowd      96034 3  udp4   127.0.0.1:2056        *:*
mongodb  mongod     45710 11 tcp4   127.0.0.1:27017       *:*
nobody   samplicate 8023  3  udp4   127.0.0.1:2055        *:*
nobody   samplicate 8023  4  udp4   *:38383               *:*
unifi    java       73302 146 tcp46 *:8080                *:*
unifi    java       73302 150 tcp46 *:8880                *:*
unifi    java       73302 157 tcp4  127.0.0.1:37396       127.0.0.1:27117
unifi    java       73302 158 tcp4  127.0.0.1:35726       127.0.0.1:27117
unifi    java       73302 159 tcp4  127.0.0.1:12523       127.0.0.1:27117
unifi    java       73302 160 tcp4  127.0.0.1:20690       127.0.0.1:27117
unifi    java       73302 161 tcp4  127.0.0.1:14841       127.0.0.1:27117
unifi    java       73302 162 tcp4  127.0.0.1:18784       127.0.0.1:27117
unbound  unbound    44697 3  udp4   *:53                  *:*
unbound  unbound    44697 4  tcp4   *:53                  *:*
unbound  unbound    44697 5  udp4   *:53                  *:*
unbound  unbound    44697 6  tcp4   *:53                  *:*
unbound  unbound    44697 7  udp4   *:53                  *:*
unbound  unbound    44697 8  tcp4   *:53                  *:*
unbound  unbound    44697 9  udp4   *:53                  *:*
unbound  unbound    44697 10 tcp4   *:53                  *:*
unbound  unbound    44697 11 tcp4   127.0.0.1:953         *:*
root     miniupnpd  26603 7  tcp4   *:2189                *:*
root     miniupnpd  26603 8  udp4   *:1900                *:*
root     miniupnpd  26603 9  udp4   192.168.48.1:47200    *:*
root     miniupnpd  26603 11 udp4   192.168.48.1:5351     *:*
dhcpd    dhcpd      72841 9  udp4   *:67                  *:*
root     lighttpd   84624 5  tcp4   127.0.0.1:443         *:*
root     lighttpd   84624 7  tcp4   192.168.48.1:443      *:*
root     lighttpd   84624 8  tcp4   127.0.0.1:80          *:*
root     lighttpd   84624 10 tcp4   192.168.48.1:80       *:*
root     sshd       74266 4  tcp4   127.0.0.1:22          *:*
root     sshd       74266 5  tcp4   192.168.48.1:22       *:*
?        ?          ?     ?  udp4   127.0.0.1:4671        127.0.0.1:2055
?        ?          ?     ?  udp4   127.0.0.1:60588       127.0.0.1:2055
?        ?          ?     ?  tcp4   192.168.48.1:8080     192.168.48.10:3046
?        ?          ?     ?  tcp4   192.168.48.1:8080     192.168.48.10:3078

How can i help further?
Proxmox enthusiast @home, bare metal @work.

As you can see the port is open and running. Did you allow access via Firewall rules?

Just added them, but i think the default rule that allows LAN to LAN address solves this by default. Still no go.
Proxmox enthusiast @home, bare metal @work.

March 14, 2021, 01:37:40 PM #57 Last Edit: March 14, 2021, 01:48:04 PM by Walnut
Quote from: mimugmail on March 06, 2021, 07:15:12 AM
Via cli:

sockstat -4

root     AdGuardHom 11694 8  tcp46  *:3000                *:*

OKAAAAAY! I just understood. I needed to open a firewall rule to allow access from the LAN. I know that seems basic to you, but I'm still learning!

A line explaining that (with an example rule) in your installation instructions would help beginners like me.

Thank you!

Quote from: Walnut on March 14, 2021, 01:37:40 PM
Quote from: mimugmail on March 06, 2021, 07:15:12 AM
Via cli:

sockstat -4

root     AdGuardHom 11694 8  tcp46  *:3000                *:*

OKAAAAAY! I just understood. I needed to open a firewall rule to allow access from the LAN. I know that seems basic to you, but I'm still learning!

A line explaining that (with an example rule) in your installation instructions would help beginners like me.

Thank you!
By default, there is no rule required to access it. Access any LAN covers that. I've never had to make any rule to access anything on a default setup LAN.

Can someone help me with the best/most correct way to get AdGuard to serve DNS?
Is there a good setup guide somewhere to show how to link it correctly?