Hello All!
is it verified ?
is it verified ?is it running on CP/M ?
-+- GoldED+/EMX 1.1.4.7
is it verified ?Verified!
... File not found. Should I fake it? (Y/N)
-+- GoldED+/EMX 1.1.4.7
not latest GoldED
-+- GoldED+/EMX 1.1.4.7
not latest GoldEDany new features in the new version?
Hello Daniel!
20 Mar 2021 20:53, Daniel PATH wrote to Benny Pedersen:
-+- GoldED+/EMX 1.1.4.7
not latest GoldED
any new features in the new version?
incorrect question
Re: ipv6 live testing ?
By: Daniel Path to Benny Pedersen on Sun Mar 21 2021 11:02:28
(long story short: i've tried 1.1.5.1 as well, but it core dumps
me when i try to enter a message,
what is the width of the window you're trying to run GED in? it has problems with widths wider than 132 so set that width to 132 or less
and GED should be ok...
Re: ipv6 live testing ?
By: Daniel Path to mark lewis on Sun Mar 21 2021 15:43:11
(long story short: i've tried 1.1.5.1 as well, but it core
dumps me when i try to enter a message,
what is the width of the window you're trying to run GED in?
it has problems with widths wider than 132 so set that width
to 132 or less and GED should be ok...
i don't know, i use mostly 80x24 via telnet,
i don't understand what telnet has to do with running GED... it is a
local sysop editor... not one generally run from a BBS over a telnet connection... perhaps you should explain your usage scenario a bit
more? probably over in the golded support echo would be better, too...
but the older version do not have this problem, so still don't
understand why to force upgrade? security? (haha)
i would imagine mainly for the bug fixes... see you over in the golded support area! ;)
===
proxy privoxy.localnet:8118
===
Ah, now I get it. You use the http proxy feature of binkd! I never thought about that. I always skipped that section in the docs, thinking "I will most
likely never need that". I never realised it could be used for a 4to6 proxy as
well. And the reason for that in turn is because I do not need a 4to6 proxy for
my binkd. It handles IPv6 natively...
Of course this trick only works for binkd. We see two "IO" flags in
the list of
IPv6 nodes. It is my understanding that they use a 6to4 relay for incoming.
They have no outgoing IPv6 for their binkd client. They both run Radius. Your
trick won't work for them...
Radius can use http proxy as well. I have tested it. The only problem with it is that it tries
to resolve the address and it does not understand IPv6 address. I can poll you with Radius
later when I get back home. :)
25 Mar 21 15:38, Tommi Koivula wrote to Michiel van der Vlist:
Radius can use http proxy as well. I have tested it. The only
problem with it is that it tries to resolve the address and it
does not understand IPv6 address. I can poll you with Radius
later when I get back home. :)
Please check your log. :)
- 25 Mar 18:47:13 [208] incoming from 2a01:4f9:c011:1ec5::1 (52356)
+ 25 Mar 18:47:13 [1844] incoming session with mxo.tkk.iki.fi [2a01:4f9:c011:1ec5::1]
- 25 Mar 18:44:52 [208] incoming from 135.181.90.166 (36544)
+ 25 Mar 18:44:52 [2648] incoming session with mxo.tkk.iki.fi [135.181.90.166]
So you first made an IPv4 connect and then manually entered an override to use fido6.vlist.eu
instead of fido.vlist.eu?
So you first made an IPv4 connect and then manually entered an
override to use fido6.vlist.eu instead of fido.vlist.eu?
Exactly.
Two questions:
1) Where does the fido6.vlist.eu come from? It exists in the DNS but it is only for local use
and not advertised in the nodelist. It is not advertised anywhere AFAIK. Maybe I mentioned it
somewhere and forgot? Or maybe you just happened to make the right guess?
That happens because Radius resolves the hostname and uses the ipv4
address, even when connecting via proxy.
2) So this manual override works only for my node and to connect to another node you have to
make another override? IOW manually enter a new line in the config for each node that is to be
connected via IPv6?
Port 8118 is the default port of privoxy.
===
proxy privoxy.localnet:8118
===
And that hostname resolves:
===
tommi@pin:~$ host privoxy.localnet
privoxy.localnet has address 192.168.1.24
privoxy.localnet has address 192.168.1.15
===
So there is also some fault tolerancy and load balancing between my
two ISP's. ;D
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 140:21:05 |
Calls: | 166 |
Files: | 5,389 |
Messages: | 223,236 |