[DiscordArchive] it doesnt work with my external ip in 'address' because it insists on using that instead of 'localAd
[DiscordArchive] it doesnt work with my external ip in 'address' because it insists on using that instead of 'localAd
Original source
it doesnt work with my external ip in 'address' because it insists on using that instead of 'localAddress' even though im on the lan. not sure how it decides what to use. is docker mucking with it?
rektbyfaith
07-02-2024, 10:38 AM #1Archived author: jasondove • Posted: 2024-07-02T10:38:22.696000+00:00
Original source
it doesnt work with my external ip in 'address' because it insists on using that instead of 'localAddress' even though im on the lan. not sure how it decides what to use. is docker mucking with it?
Original source
I don't think docker does anything with direct ip addresses. only hostnames get resolved to the current network
rektbyfaith
07-02-2024, 10:41 AM #2Archived author: 3138720606 • Posted: 2024-07-02T10:41:39.214000+00:00
Original source
I don't think docker does anything with direct ip addresses. only hostnames get resolved to the current network
Original source
i just meant because it would see its ip as 172 something instead of 192 something ♂️ . ill look at the code i guess
rektbyfaith
07-02-2024, 10:42 AM #3Archived author: jasondove • Posted: 2024-07-02T10:42:11.978000+00:00
Original source
i just meant because it would see its ip as 172 something instead of 192 something ♂️ . ill look at the code i guess
Original source
isn't the realmlist ip just to report to the client? so the client knows where to connect to world? then it should be fine
rektbyfaith
07-02-2024, 10:47 AM #4Archived author: 3138720606 • Posted: 2024-07-02T10:47:41.463000+00:00
Original source
isn't the realmlist ip just to report to the client? so the client knows where to connect to world? then it should be fine
Original source
just like with other cores that work fine, i have external ip in address and internal ip in localAddress so i can access internally and externally. with this core specifically, it seems to always send the client 'address' (external ip) so it fails to login locally
rektbyfaith
07-02-2024, 10:49 AM #5Archived author: jasondove • Posted: 2024-07-02T10:49:39.419000+00:00
Original source
just like with other cores that work fine, i have external ip in address and internal ip in localAddress so i can access internally and externally. with this core specifically, it seems to always send the client 'address' (external ip) so it fails to login locally
Original source
okay yeah that's strange. with other cores I also had no issue there
rektbyfaith
07-02-2024, 10:50 AM #6Archived author: 3138720606 • Posted: 2024-07-02T10:50:03.157000+00:00
Original source
okay yeah that's strange. with other cores I also had no issue there
Original source
but also the first time ive had to use bnetserver so idk how that changes things
rektbyfaith
07-02-2024, 10:50 AM #7Archived author: jasondove • Posted: 2024-07-02T10:50:31.270000+00:00
Original source
but also the first time ive had to use bnetserver so idk how that changes things
Original source
ill just build and debug a separate bnetserver instance
rektbyfaith
07-02-2024, 10:51 AM #8Archived author: jasondove • Posted: 2024-07-02T10:51:11.628000+00:00
Original source
ill just build and debug a separate bnetserver instance
Original source
yeah me neither
rektbyfaith
07-02-2024, 11:00 AM #9Archived author: 3138720606 • Posted: 2024-07-02T11:00:06.085000+00:00
Original source
yeah me neither
1 Guest(s)
1 Guest(s)