[HECnet] HECnet mapper -- request to backbone node operators

Hi Paul, i've upgraded A35RTR on 35.1023 to PyDECnet 526 and put in the logging line as requested. as per Keith, i also had to make the changes to TapEth so i could speak to /dev/net/tun. this is the same as i've done previously - but I actually had a recollection that this change had actually been rolled into one of the previous builds? perhaps i'm wrong. i have one query - i run PyDECnet as a daemon and normally my local log files show up/down route visibility. i assume with the "logging monitor" line that this functionality is changed? is there a way to set the logging so I can see the up/down in the network as i did previously? if it matters, i was on version 488 and did a fresh install of 526. many thanks, cheers, Wiz!! ________________________________ From: owner-hecnet at Update.UU.SE <owner-hecnet at Update.UU.SE> on behalf of Keith Halewood <Keith.Halewood at pitbulluk.org> Sent: Monday, 17 August 2020 2:46:41 AM To: hecnet at Update.UU.SE Subject: RE: [HECnet] HECnet mapper -- request to backbone node operators When I do svn checkout svn://akdesign.dyndns.org/pydecnet/trunk/pydecnet pydecnet.latest it says I've checked out 524. I had to make the modification for the native TAP device support in ethernet.py but other than that, it's fine. Keith -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Paul Koning Sent: 16 August 2020 17:40 To: Bob Armstrong <bob at jfcl.com> Cc: <hecnet at update.uu.se> <hecnet at Update.UU.SE> Subject: Re: [HECnet] HECnet mapper -- request to backbone node operators Yes, sorry. Sometimes I get mixed up about revs. The remote sink stuff was added in 520 and corrected in 521. Strange. Can you enable TRACE logging and email me the resulting log? paul