OPKG and NDMS relation

[SterhTG]

Could someone share details on how OPKG and KeeneticOS interact and how they work?
I saw in the configuration `opkg dns-override` - how does it work? Where does the traffic come from KeeneticOS  to OPKG  and how does it get toKeeneticOS  ?
Is this a docker inside the OS or a separate namespace?
I plan to run telegram service on OPKG side how would I allow connection to outside ?
If I plan to run web service on OPKG how can I allow connection from my internal network?

[Denis P]

1 час назад, SterhTG сказал:

Could someone share details on how OPKG and KeeneticOS interact and how they work?

https://github.com/ndmsystems/packages/wiki/Opkg-Component

1 час назад, SterhTG сказал:

`opkg dns-override` - how does it work?

this command disables system dns-proxy on port 53, its helpful if you want to use dnsmasq, bind9, adguardhome. etc on keenetic with default port
 

1 час назад, SterhTG сказал:

I plan to run telegram service on OPKG side how would I allow connection to outside ?
If I plan to run web service on OPKG how can I allow connection from my internal network?

by using firewall or port forwarding from web ui
 

Edited December 9, 2024 by Denis P

[Le ecureuil]

22 часа назад, SterhTG сказал:

Could someone share details on how OPKG and KeeneticOS interact and how they work?
I saw in the configuration `opkg dns-override` - how does it work? Where does the traffic come from KeeneticOS  to OPKG  and how does it get toKeeneticOS  ?
Is this a docker inside the OS or a separate namespace?
I plan to run telegram service on OPKG side how would I allow connection to outside ?
If I plan to run web service on OPKG how can I allow connection from my internal network?

opkg dns-override just releases the local resolver from the port 53 (because a user may want to bind their special service to the port 53).

No, it's not a docker, just a group of subprocesses (with optional chroot).

Connections to the outside are allowed by default (as, for example, for the download station).

Connections from the internal network are allowed by default too (as, for example, for the web-interface server).