So I'm kind of following up on some conversations had in these threads:
https://www.arednmesh.org/content/two-host-names-same-node
https://www.arednmesh.org/content/subdomains-mesh
Main goal I'm trying to work with is handling web request routing based on host headers, not sub directories, not all software plays nice and it's not always the most user-friendly.
I've looked into subdomains, but from what I understand this was a desired feature that never got implemented, so not supported.
I've also attempted to basically register a "ghost host", this works... sort of. I can drop a custom entry into /etc/hosts.user and push a service directly into config.mesh -> setup -> services -> service, I got a script in Lua that'll do that, but I get weird artifacts. First the DNS duplication seems to upset OSLR, my 2nd host is reported as "unreachable" from my panel.
Secondly my service is only listed on my babel mesh, but not the wider mesh, not exactly sure what the difference is yet (I'm faily new to hacking around on this).
My other option is to just continue dropping more interfaces or something on the network of my Pi and eating IPs and dedicating an IP per service, but this seems wasteful.
---
So I got a few questions here:
1) Is subdomain support somewhere on the roadmap still?
2) Outside of creating reporting issues, is creating fake hosts going to cause some issues to the wider network due to how OSLR works? (basically under no condition will two host names with the same IP result in anything but bad propagation of my configuration?)
3) Is there any less-than-official way this is supported or am I mostly going to end up chasing dead-ends?
4) Would eating IPs on a handful of services not really be that bad of a compromise, sure having up to 29 hosts probably provides more than enough for me, but also why eat 29 when I can use 2 (my node and my server handling all traffic proxying)?
https://www.arednmesh.org/content/two-host-names-same-node
https://www.arednmesh.org/content/subdomains-mesh
Main goal I'm trying to work with is handling web request routing based on host headers, not sub directories, not all software plays nice and it's not always the most user-friendly.
I've looked into subdomains, but from what I understand this was a desired feature that never got implemented, so not supported.
I've also attempted to basically register a "ghost host", this works... sort of. I can drop a custom entry into /etc/hosts.user and push a service directly into config.mesh -> setup -> services -> service, I got a script in Lua that'll do that, but I get weird artifacts. First the DNS duplication seems to upset OSLR, my 2nd host is reported as "unreachable" from my panel.
Secondly my service is only listed on my babel mesh, but not the wider mesh, not exactly sure what the difference is yet (I'm faily new to hacking around on this).
My other option is to just continue dropping more interfaces or something on the network of my Pi and eating IPs and dedicating an IP per service, but this seems wasteful.
---
So I got a few questions here:
1) Is subdomain support somewhere on the roadmap still?
2) Outside of creating reporting issues, is creating fake hosts going to cause some issues to the wider network due to how OSLR works? (basically under no condition will two host names with the same IP result in anything but bad propagation of my configuration?)
3) Is there any less-than-official way this is supported or am I mostly going to end up chasing dead-ends?
4) Would eating IPs on a handful of services not really be that bad of a compromise, sure having up to 29 hosts probably provides more than enough for me, but also why eat 29 when I can use 2 (my node and my server handling all traffic proxying)?