[HECnet] *** Very important information ***

Just so we're clear, I'm not talking about anything to do about getting the node list via TCP/IP. I'm talking about using DAP to fetch it from MIM, viz, NFT>*Copy MIM::FIX.T20;0 SYSTEM:NODE-DATA.TXT That's not changing, right? On 11/22/21 11:02 AM, Johnny Billquist wrote: > Hi. MIM will continue to be the source. And now Mim.Update.UU.SE is a > CNAME to Mim.Stupi.NET, so hopefully nothing needs to change anywhere. > > ? Johnny > > On 2021-11-22 16:58, Thomas DeBellis wrote: >> Hi Johhny, >> >> Will MIM continue to be the online source of record for the T20.CMD >> node list?? Or should I go elsewhere to fetch it? >> >> --T >> >> On 11/22/21 10:52 AM, Johnny Billquist wrote: >>> On 2021-11-22 16:51, Robert Armstrong wrote: >>>>> Peter Lothberg <roll at stupi.com> wrote: >>>>> hecnet-1023, 192.108.202.70? is UP but I drop all packets towards >>>>> it that >>>>> are not HECnet tunnels in one or the other form.. (linux.....) >>>> >>>> ?? Did you include Multinet in your rules? >>>> >>>> ?? A2RTR used to have a Multinet tunnel to MIM (Johnny's RSX TCP/IP >>>> stack supports that), and when I change it to >>>> >>>> ????circuit MUL-1 Multinet hecnet-1-1023.stupi.net:700:connect >>>> --cost=12 >>>> >>>> it doesn't connect.? FWIW, the previous connection was >>>> >>>> ????#circuit MUL-1 Multinet mim.update.uu.se:700:connect --cost=12 >>> >>> Sorry, that would be my fault. I saw that Peter had some comments >>> about links to you in the config, so I didn't do anything. Let me >>> set you up as with Mim before then, but to hecnet-1-1023. In a sec... >>> >>> ? Johnny >>> >