Score:0

expose local nginx to wifi clients on connect

us flag

I have a router that I configered it's primary DNS to unbound (docker container)

Also have nginx container accessible from the router as a reverse proxy for some local catalog servers,

  • company.lan - main site
  • catalog1.lan
  • catalog2.lan
  • coffee.lan

I now need the default site to be exposed to any client connects to the router either via WIFI or LAN

router captive portal is restricted by the internet provider configuration and I need the client to also access internet so I can't use default router captive portal

any way to expose my sites to my clients the same way mikerotik exposes it's login page either via DNS, NGINX or anything externally of router that could override its behavoir ?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.