You may need to set up "Hairpin NAT" or "NAT Reflection" to translate IP
addresses from internal users into seeming to be from outside. I ran
into this with a BeShare server, and a BitTorrent tracker. Story at
http://web.ncf.ca/au829/WeekendReports/20180812.html
Or if you have your own DNS server, you could make those names connect
to internal LAN IP addresses instead.
- Alex
On 2018-11-05 3:03 p.m., Alexander von Gluck IV wrote:
November 5, 2018 11:38 AM, "Andrew Lindesay" <apl@xxxxxxxxxxxxxx> wrote:
External repositories such as your one unfortunately won't be updating inThat's not all all what is happening.
HDS until Alex
is able to find a way for HDS to communicate with the internet.
HDS can't communicate to repositories on the same server externally.
HDS -> google.com OK!
HDS -> billshpkgrepo.com OK!
HDS -> haiku_internal_repo OK!
HDS -> eu.hpkg.haiku-os.org -> haiku_internal_repo not ok.
Pretty much you can't go out the ingress and come back in the same ingress.
-- Alex
