<div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">FTTC NCDs and DPUs are known to be pretty weak and die easily during storms. <div>A. Ensure your legacy phone line was cut out of the CIU in the pit/pole - and also the other three neighbors connected to the DPU. </div><div>B. Put your NCD and phone line on a surge protector. </div><div>C. Try and get the more hardy Adtrans version of the NCD as they are/were meant to replace the Netcomms as the thousands of them get replaced every-time there is a storm. </div><div>D. Get a spare/backup NCD. </div><div>E. If budget allows, get on an eSLA via your provider - so you get priority techs.<div class="mb_sig"></div>
</div><blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">On 3/01/2022 8:56:55 PM, ausnog-request@lists.ausnog.net <ausnog-request@lists.ausnog.net> wrote:</p><div style="font-family:Arial,Helvetica,sans-serif">Send AusNOG mailing list submissions to
<br> ausnog@lists.ausnog.net
<br>
<br>To subscribe or unsubscribe via the World Wide Web, visit
<br> http://lists.ausnog.net/mailman/listinfo/ausnog
<br>or, via email, send a message with subject or body 'help' to
<br> ausnog-request@lists.ausnog.net
<br>
<br>You can reach the person managing the list at
<br> ausnog-owner@lists.ausnog.net
<br>
<br>When replying, please edit your Subject line so it is more specific
<br>than "Re: Contents of AusNOG digest..."
<br>
<br>
<br>Today's Topics:
<br>
<br> 1. On Prem Exchange issues - y2k22 bug. (Mark Dignam)
<br> 2. Re: On Prem Exchange issues - y2k22 bug. (DaZZa)
<br> 3. Telstra NBN Outage NSW (Simon Pearce)
<br> 4. NBN FTTC services and power hits (Chris Chaundy)
<br> 5. Re: NBN FTTC services and power hits (Julien Goodwin)
<br> 6. Re: NBN FTTC services and power hits (Andy Blume)
<br> 7. Re: NBN FTTC services and power hits (Greg Lipschitz)
<br> 8. Re: NBN FTTC services and power hits (Chris Chaundy)
<br>
<br>
<br>----------------------------------------------------------------------
<br>
<br>Message: 1
<br>Date: Sat, 1 Jan 2022 15:20:25 +0800
<br>From: "Mark Dignam" <mark@innaloo.net>
<br>To: <ausnog@ausnog.net>
<br>Subject: [AusNOG] On Prem Exchange issues - y2k22 bug.
<br>Message-ID: <000b01d7fee0$0bb61250$232236f0$@innaloo.net>
<br>Content-Type: text/plain; charset="us-ascii"
<br>
<br>People.
<br>
<br>
<br>
<br>There appears to a y2k22 bug in Exchange servers - and its fairly nasty. As
<br>of midnight UTC, the Filtering Service stopped passing emails, email goes in
<br>- and never gets delivered to the mailbox. Easiest thing to look for in the
<br>event logs:
<br>
<br>The FIP-FS Filtering Management Service was unable to acquire a scanner
<br>within the specified timeout.
<br>
<br>or
<br>
<br>The FIP-FS "Microsoft" Scan Engine failed to load. PID: 12348, Error Code:
<br>0x80004005. Error Description: Can't convert "2201010001" to long.
<br>
<br>
<br>
<br>Office365 appears NOT affected at this stage. (as expected, with MS's
<br>current "move to our cloud" strategy)
<br>
<br>https://twitter.com/JRoosen/status/1477120097747677184
<br>
<br>
<br>
<br>Quick fix for a 2016 system, open a Exchange Management Power Shell screen.
<br>
<br>
<br>
<br>cd $exscripts
<br>
<br>.\Disable-AntimalwareScanning.ps1
<br>
<br>Restart-Service MSExchangeTRansport
<br>
<br>
<br>
<br>And anything waiting in the submission will get delivered in the next few
<br>mins.
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>-------------- next part --------------
<br>An HTML attachment was scrubbed...
<br>URL: <http: lists.ausnog.net="" pipermail="" ausnog="" attachments="" 20220101="" 86fb516a="" attachment-0001.htm="">
<br>
<br>------------------------------
<br>
<br>Message: 2
<br>Date: Sat, 1 Jan 2022 18:52:32 +1100
<br>From: DaZZa <dazzagibbs@gmail.com>
<br>To: Mark Dignam <mark@innaloo.net>
<br>Cc: AusNOG Mailing List <ausnog@ausnog.net>
<br>Subject: Re: [AusNOG] On Prem Exchange issues - y2k22 bug.
<br>Message-ID:
<br> <campv8mqcn+bbzm6t=e7mqoeh+i7hyx8bw28lpv0lji4fmxhffa@mail.gmail.com>
<br>Content-Type: text/plain; charset="utf-8"
<br>
<br>Probably related Reddit thread
<br>
<br>https://www.reddit.com/r/sysadmin/comments/rt91z6/exchange_2019_antimalware_bad_update
<br>
<br>Appears to be related to the long signed integer value for version numbers
<br>allowing values only up to 2,147,483,647 - so when version numbers for the
<br>malware/inline virus scanner were in 2021 - the first two numbers were "21"
<br>and it worked.
<br>
<br>Now it's 2022 - the first two numbers are "22", and it b0rks the update
<br>
<br>It's almost comical that a company as big as Microsoft - especially after
<br>the hype around Y2K bugs all those years ago - has missed this so blatantly
<br>- but I suppose the company that we should be used to that by now.
<br>
<br>
<br>
<br>DaZZa
<br>
<br>On Sat, 1 Jan 2022, 6:20 pm Mark Dignam, <mark@innaloo.net> wrote:
<br>
<br>> People.
<br>>
<br>>
<br>>
<br>> There appears to a y2k22 bug in Exchange servers - and its fairly nasty.
<br>> As of midnight UTC, the Filtering Service stopped passing emails, email
<br>> goes in - and never gets delivered to the mailbox. Easiest thing to look
<br>> for in the event logs:
<br>>
<br>> *The FIP-FS Filtering Management Service was unable to acquire a scanner
<br>> within the specified timeout.*
<br>>
<br>> or
<br>>
<br>> *The FIP-FS "Microsoft" Scan Engine failed to load. PID: 12348, Error
<br>> Code: 0x80004005. Error Description: Can't convert "2201010001" to long.*
<br>>
<br>>
<br>>
<br>> Office365 appears NOT affected at this stage. (as expected, with MS's
<br>> current "move to our cloud" strategy)
<br>>
<br>> https://twitter.com/JRoosen/status/1477120097747677184
<br>>
<br>>
<br>>
<br>> Quick fix for a 2016 system, open a Exchange Management Power Shell
<br>> screen?
<br>>
<br>>
<br>>
<br>> cd $exscripts
<br>>
<br>> .\Disable-AntimalwareScanning.ps1
<br>>
<br>> Restart-Service MSExchangeTRansport
<br>>
<br>>
<br>>
<br>> And anything waiting in the submission will get delivered in the next few
<br>> mins.
<br>>
<br>>
<br>>
<br>>
<br>>
<br>>
<br>>
<br>>
<br>>
<br>>
<br>> _______________________________________________
<br>> AusNOG mailing list
<br>> AusNOG@lists.ausnog.net
<br>> http://lists.ausnog.net/mailman/listinfo/ausnog
<br>>
<br>-------------- next part --------------
<br>An HTML attachment was scrubbed...
<br>URL: <http: lists.ausnog.net="" pipermail="" ausnog="" attachments="" 20220101="" 09a163dc="" attachment-0001.htm="">
<br>
<br>------------------------------
<br>
<br>Message: 3
<br>Date: Sun, 2 Jan 2022 18:01:23 +1100
<br>From: Simon Pearce <simon275@gmail.com>
<br>To: ausnog@lists.ausnog.net
<br>Subject: [AusNOG] Telstra NBN Outage NSW
<br>Message-ID:
<br> <cao6obbh5xhh59e+v4pb-hlgeuets=qze0bdyu5pduvhdedaffq@mail.gmail.com>
<br>Content-Type: text/plain; charset="utf-8"
<br>
<br>Hi all
<br>
<br>Apologies for the noise. We saw multiple Telstra backed NBN services go
<br>offline in NSW and ACT around an hour ago. The Call centres seem backed up
<br>with long wait times.
<br>
<br>Cheers
<br>Simon
<br>
<br>AS146963
<br>-------------- next part --------------
<br>An HTML attachment was scrubbed...
<br>URL: <http: lists.ausnog.net="" pipermail="" ausnog="" attachments="" 20220102="" 82f33cd7="" attachment-0001.htm="">
<br>
<br>------------------------------
<br>
<br>Message: 4
<br>Date: Mon, 3 Jan 2022 09:26:00 +1100
<br>From: Chris Chaundy <chris.chaundy@gmail.com>
<br>To: "ausnog@ausnog.net" <ausnog@lists.ausnog.net>
<br>Subject: [AusNOG] NBN FTTC services and power hits
<br>Message-ID: <da321e92-48ca-424e-9471-a50e1ac412a0@gmail.com>
<br>Content-Type: text/plain; charset=utf-8
<br>
<br>Is there anyone from NBNco on this list willing to discuss this with me?
<br>
<br>It seems that every time there is a power hit in our locality (which with Ausnet is pretty regularly), the FTTC services die and don?t come back until you log a fault through the provider (in my case, Telstra) and then wait for them to go through the hoops of dealing with NBNco.
<br>
<br>This has happened four times in the last couple of months (thankfully I have 4G backup). There must be some aggregator kit that has no power backup or cannot recover from power outages - pretty crap really. :-|
<br>
<br>Sorry if this is a little OT for the list but I?d be interested if other FTTC areas see the same problem.
<br>
<br>Sent from my iPhone
<br>
<br>------------------------------
<br>
<br>Message: 5
<br>Date: Mon, 3 Jan 2022 18:13:04 +1100
<br>From: Julien Goodwin <ausnog@studio442.com.au>
<br>To: "ausnog@ausnog.net" <ausnog@lists.ausnog.net>
<br>Subject: Re: [AusNOG] NBN FTTC services and power hits
<br>Message-ID: <c36d807a-5e82-455d-d664-d97d14cb1b56@studio442.com.au>
<br>Content-Type: text/plain; charset=UTF-8; format=flowed
<br>
<br>On 3/1/22 9:26 am, Chris Chaundy wrote:
<br>> It seems that every time there is a power hit in our locality (which with Ausnet is pretty regularly), the FTTC services die and don?t come back until you log a fault through the provider (in my case, Telstra) and then wait for them to go through the hoops of dealing with NBNco.
<br>
<br>For *my* FTTC I've had occasional cases where an NTD reboot was needed
<br>(~1/year), however much more frequent appears to be cases where one of
<br>my neighbours bounce their NTD (for whatever reason) the micro-DSLAM
<br>seems to reboot for a multi-minute outage.
<br>
<br>I'm seriously right about at the point where I might put in an order to
<br>get someone else to dig fibre in[1] since there's enough evidence that
<br>NBN simply choose not to care about multiple multi-minute outages a day
<br>so I've not even bothered trying to call a fault on it.
<br>
<br>1: Hi sales people, no I'm not interested in talking to you, I know who
<br>has fibre near me, I'll reach out to contacts I already have if I end up
<br>deciding to try.
<br>
<br>
<br>------------------------------
<br>
<br>Message: 6
<br>Date: Mon, 3 Jan 2022 08:13:42 +0000
<br>From: Andy Blume <andy@andyblu.me>
<br>Cc: "ausnog@ausnog.net" <ausnog@lists.ausnog.net>
<br>Subject: Re: [AusNOG] NBN FTTC services and power hits
<br>Message-ID: <6FA9015A-CB3C-40F0-AF59-0F5637B3FF94@andyblu.me>
<br>Content-Type: text/plain; charset="utf-8"
<br>
<br>
<br>On 3 Jan 2022, at 09:26, Chris Chaundy <><mailto:chris.chaundy@gmail.com>> wrote:
<br>
<br>It seems that every time there is a power hit in our locality (which with Ausnet is pretty regularly), the FTTC services die and don?t come back until you log a fault through the provider
<br>
<br>Happened twice here; first in July and second just two weeks ago. Both involved a call to Aussie Broadband to organise an NBN tech to come out. Thankfully in both cases someone was able to come out very quickly, however I am concerned that every time there's a power outage or interruption this is going to be the standard procedure.
<br>
<br>
<br>-------------- next part --------------
<br>An HTML attachment was scrubbed...
<br>URL: <http: lists.ausnog.net="" pipermail="" ausnog="" attachments="" 20220103="" d8076717="" attachment-0001.htm="">
<br>
<br>------------------------------
<br>
<br>Message: 7
<br>Date: Mon, 3 Jan 2022 08:54:58 +0000
<br>From: Greg Lipschitz <glipschitz@summitinternet.com.au>
<br>To: Chris Chaundy <chris.chaundy@gmail.com>, "ausnog@ausnog.net"
<br> <ausnog@lists.ausnog.net>
<br>Subject: Re: [AusNOG] NBN FTTC services and power hits
<br>Message-ID:
<br> <meyp282mb259749bec4880e7dc9f3993c82499@meyp282mb2597.ausp282.prod.outlook.com>
<br>
<br>Content-Type: text/plain; charset="utf-8"
<br>
<br>Hi Chris,
<br>
<br>The nbn DPU (the "mini-vdsl/gfast dslam" which lives in the pit) is reverse powered (about 6-14W) from the NCD (the nbn box inside your house). nbn use a mix of Netcomm and more recently Nokia DPU's. The DPU only needs 1 customer NCD connected to it to supply the power.
<br>
<br>The DPU can connect up to 4 premises and the interesting thing is that any of the RSP's who have a customer connected to the DPU can initiate a DPU reset via the nbn API.
<br>
<br>So, you might be with Telstra, and your neighbours with Aussie Broadband, TPG and Optus and any one of them can essentially cause your service to drop momentarily if they contact their RSP who initiates the DPU reset as part of the troubleshooting.
<br>
<br>We've found that the DPU's often suffer the same fate as the old ADSL copper services when the pit fills up with water, the DPU goes off to la-la land (who would have thunk power and water didn't mix!) or the copper between the DPU and the customer gets corroded and needs to be cleaned up or replaced.
<br>
<br>I've not heard of power issues causing the DPU to have issues. It sounds like the DPU is perhaps losing its config when there's a power interruption (we've certainly seen that with the Telstra EA MRV OS904 NTU's over the years).
<br>
<br>If you're interested how it all comes together, nbn publish their design docs - https://www.nbnco.com.au/content/dam/nbn/documents/sell/sau/network-design-rules-20210630.pdf
<br>
<br>Cheers
<br>Greg
<br>
<br>
<br>
<br>________________________________
<br>
<br>Greg Lipschitz | Founder & CEO | Summit Internet
<br>glipschitz@summitinternet.com.au
<br>summitinternet.com.au
<br>1300 049 749
<br>Unit 2, 31-39 Norcal Road, Nunawading VIC 3131
<br>Summit Internet
<br>From: AusNOG <ausnog-bounces@lists.ausnog.net> on behalf of Chris Chaundy <chris.chaundy@gmail.com>
<br>Sent: 03 January 2022 09:26
<br>To: ausnog@ausnog.net <ausnog@lists.ausnog.net>
<br>Subject: [AusNOG] NBN FTTC services and power hits
<br>
<br>Is there anyone from NBNco on this list willing to discuss this with me?
<br>
<br>It seems that every time there is a power hit in our locality (which with Ausnet is pretty regularly), the FTTC services die and don?t come back until you log a fault through the provider (in my case, Telstra) and then wait for them to go through the hoops of dealing with NBNco.
<br>
<br>This has happened four times in the last couple of months (thankfully I have 4G backup). There must be some aggregator kit that has no power backup or cannot recover from power outages - pretty crap really. :-|
<br>
<br>Sorry if this is a little OT for the list but I?d be interested if other FTTC areas see the same problem.
<br>
<br>Sent from my iPhone
<br>_______________________________________________
<br>AusNOG mailing list
<br>AusNOG@lists.ausnog.net
<br>https://aus01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.ausnog.net%2Fmailman%2Flistinfo%2Fausnog&data=04%7C01%7Cglipschitz%40summitinternet.com.au%7C7d3675defb8a4be9a6ab08d9ce3ef1a0%7C0838a12f226e43dfa6e4bb63d2643a7e%7C1%7C0%7C637767592012923616%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=eaYK8fpeVKh%2FCKcTW5KgKBQOB32TYug2Q5GLkCN7xLo%3D&reserved=0
<br>-------------- next part --------------
<br>An HTML attachment was scrubbed...
<br>URL: <http: lists.ausnog.net="" pipermail="" ausnog="" attachments="" 20220103="" b974b022="" attachment-0001.htm="">
<br>-------------- next part --------------
<br>A non-text attachment was scrubbed...
<br>Name: image793377.png
<br>Type: image/png
<br>Size: 984 bytes
<br>Desc: image793377.png
<br>URL: <http: lists.ausnog.net="" pipermail="" ausnog="" attachments="" 20220103="" b974b022="" attachment-0004.png="">
<br>-------------- next part --------------
<br>A non-text attachment was scrubbed...
<br>Name: image192808.png
<br>Type: image/png
<br>Size: 10728 bytes
<br>Desc: image192808.png
<br>URL: <http: lists.ausnog.net="" pipermail="" ausnog="" attachments="" 20220103="" b974b022="" attachment-0005.png="">
<br>-------------- next part --------------
<br>A non-text attachment was scrubbed...
<br>Name: image042550.png
<br>Type: image/png
<br>Size: 1930 bytes
<br>Desc: image042550.png
<br>URL: <http: lists.ausnog.net="" pipermail="" ausnog="" attachments="" 20220103="" b974b022="" attachment-0006.png="">
<br>-------------- next part --------------
<br>A non-text attachment was scrubbed...
<br>Name: image612353.png
<br>Type: image/png
<br>Size: 3004 bytes
<br>Desc: image612353.png
<br>URL: <http: lists.ausnog.net="" pipermail="" ausnog="" attachments="" 20220103="" b974b022="" attachment-0007.png="">
<br>
<br>------------------------------
<br>
<br>Message: 8
<br>Date: Mon, 3 Jan 2022 20:55:38 +1100
<br>From: Chris Chaundy <chris.chaundy@gmail.com>
<br>To: Greg Lipschitz <glipschitz@summitinternet.com.au>
<br>Cc: "ausnog@ausnog.net" <ausnog@lists.ausnog.net>
<br>Subject: Re: [AusNOG] NBN FTTC services and power hits
<br>Message-ID:
<br> <caborm94wbaso8g7h4cvpnh5ks8yuzjf8ylw6vc6hcuzearnc=a@mail.gmail.com>
<br>Content-Type: text/plain; charset="utf-8"
<br>
<br>Hi Greg,
<br>
<br>Thanks for the info (a fair bit I was already aware of though) but up where
<br>I am, pretty much everyone has their own DPU (big properties along a dirt
<br>road. No concern with pits full of water though - everything is on power
<br>poles including the DPUs and the fibre that connects them back to the
<br>network (plus the copper feed into my house)! It does go underground
<br>further down the mountain near the township but I'm not sure where the next
<br>'active' kit is located (there is a lot of reading in the document the link
<br>you sent :-).
<br>
<br>These are not brief hits but outages that have lasted for days. Your
<br>comment about the DPU losing its configuration is interesting though and
<br>may well be the issue. I hope they replace it when NBNco visits me
<br>tomorrow!
<br>
<br>Cheers, Chris
<br>
<br>Sent from my iPhone
<br>
<br>On 3 Jan 2022, at 19:55, Greg Lipschitz <glipschitz@summitinternet.com.au>
<br>wrote:
<br>
<br>?
<br>Hi Chris,
<br>
<br>The nbn DPU (the "mini-vdsl/gfast dslam" which lives in the pit) is reverse
<br>powered (about 6-14W) from the NCD (the nbn box inside your house). nbn use
<br>a mix of Netcomm and more recently Nokia DPU's. The DPU only needs 1
<br>customer NCD connected to it to supply the power.
<br>
<br>The DPU can connect up to 4 premises and the interesting thing is that any
<br>of the RSP's who have a customer connected to the DPU can initiate a DPU
<br>reset via the nbn API.
<br>
<br>So, you might be with Telstra, and your neighbours with Aussie Broadband,
<br>TPG and Optus and any one of them can essentially cause your service to
<br>drop momentarily if they contact their RSP who initiates the DPU reset as
<br>part of the troubleshooting.
<br>
<br>We've found that the DPU's often suffer the same fate as the old ADSL
<br>copper services when the pit fills up with water, the DPU goes off to la-la
<br>land (who would have thunk power and water didn't mix!) or the copper
<br>between the DPU and the customer gets corroded and needs to be cleaned up
<br>or replaced.
<br>
<br>I've not heard of power issues causing the DPU to have issues. It sounds
<br>like the DPU is perhaps losing its config when there's a power interruption
<br>(we've certainly seen that with the Telstra EA MRV OS904 NTU's over the
<br>years).
<br>
<br>If you're interested how it all comes together, nbn publish their design
<br>docs -
<br>https://www.nbnco.com.au/content/dam/nbn/documents/sell/sau/network-design-rules-20210630.pdf
<br>
<br>Cheers
<br>Greg
<br>
<br>
<br>
<br>
<br>Greg Lipschitz | Founder & CEO | Summit Internet
<br>*glipschitz@summitinternet.com.au* <glipschitz@summitinternet.com.au>
<br>*summitinternet.com.au* <http: summitinternet.com.au="">
<br>*1300 049 749* <1300%20049%20749>
<br>*Unit 2, 31-39 Norcal Road, Nunawading VIC 3131*
<br><https: www.google.com="" maps?cid="12522583051503623677&_ga=2.149009334.1057584350.1554770858-1081443428.1554770858">
<br>[image: Summit Internet] <http: summitinternet.com.au="">
<br>------------------------------
<br>*From:* AusNOG <ausnog-bounces@lists.ausnog.net> on behalf of Chris Chaundy
<br><chris.chaundy@gmail.com>
<br>*Sent:* 03 January 2022 09:26
<br>*To:* ausnog@ausnog.net <ausnog@lists.ausnog.net>
<br>*Subject:* [AusNOG] NBN FTTC services and power hits
<br>
<br>Is there anyone from NBNco on this list willing to discuss this with me?
<br>
<br>It seems that every time there is a power hit in our locality (which with
<br>Ausnet is pretty regularly), the FTTC services die and don?t come back
<br>until you log a fault through the provider (in my case, Telstra) and then
<br>wait for them to go through the hoops of dealing with NBNco.
<br>
<br>This has happened four times in the last couple of months (thankfully I
<br>have 4G backup). There must be some aggregator kit that has no power
<br>backup or cannot recover from power outages - pretty crap really. :-|
<br>
<br>Sorry if this is a little OT for the list but I?d be interested if other
<br>FTTC areas see the same problem.
<br>
<br>Sent from my iPhone
<br>_______________________________________________
<br>AusNOG mailing list
<br>AusNOG@lists.ausnog.net
<br>https://aus01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.ausnog.net%2Fmailman%2Flistinfo%2Fausnog&data=04%7C01%7Cglipschitz%40summitinternet.com.au%7C7d3675defb8a4be9a6ab08d9ce3ef1a0%7C0838a12f226e43dfa6e4bb63d2643a7e%7C1%7C0%7C637767592012923616%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=eaYK8fpeVKh%2FCKcTW5KgKBQOB32TYug2Q5GLkCN7xLo%3D&reserved=0
<br>-------------- next part --------------
<br>An HTML attachment was scrubbed...
<br>URL: <http: lists.ausnog.net="" pipermail="" ausnog="" attachments="" 20220103="" f7d5e968="" attachment.htm="">
<br>-------------- next part --------------
<br>A non-text attachment was scrubbed...
<br>Name: image192808.png
<br>Type: image/png
<br>Size: 10728 bytes
<br>Desc: not available
<br>URL: <http: lists.ausnog.net="" pipermail="" ausnog="" attachments="" 20220103="" f7d5e968="" attachment.png="">
<br>-------------- next part --------------
<br>A non-text attachment was scrubbed...
<br>Name: image612353.png
<br>Type: image/png
<br>Size: 3004 bytes
<br>Desc: not available
<br>URL: <http: lists.ausnog.net="" pipermail="" ausnog="" attachments="" 20220103="" f7d5e968="" attachment-0001.png="">
<br>-------------- next part --------------
<br>A non-text attachment was scrubbed...
<br>Name: image793377.png
<br>Type: image/png
<br>Size: 984 bytes
<br>Desc: not available
<br>URL: <http: lists.ausnog.net="" pipermail="" ausnog="" attachments="" 20220103="" f7d5e968="" attachment-0002.png="">
<br>-------------- next part --------------
<br>A non-text attachment was scrubbed...
<br>Name: image042550.png
<br>Type: image/png
<br>Size: 1930 bytes
<br>Desc: not available
<br>URL: <http: lists.ausnog.net="" pipermail="" ausnog="" attachments="" 20220103="" f7d5e968="" attachment-0003.png="">
<br>
<br>------------------------------
<br>
<br>Subject: Digest Footer
<br>
<br>_______________________________________________
<br>AusNOG mailing list
<br>AusNOG@lists.ausnog.net
<br>http://lists.ausnog.net/mailman/listinfo/ausnog
<br>
<br>
<br>------------------------------
<br>
<br>End of AusNOG Digest, Vol 119, Issue 2
<br>**************************************
<br></http:></http:></http:></http:></http:></ausnog@lists.ausnog.net></chris.chaundy@gmail.com></ausnog-bounces@lists.ausnog.net></http:></https:></http:></glipschitz@summitinternet.com.au></glipschitz@summitinternet.com.au></caborm94wbaso8g7h4cvpnh5ks8yuzjf8ylw6vc6hcuzearnc=a@mail.gmail.com></ausnog@lists.ausnog.net></glipschitz@summitinternet.com.au></chris.chaundy@gmail.com></http:></http:></http:></http:></http:></ausnog@lists.ausnog.net></chris.chaundy@gmail.com></ausnog-bounces@lists.ausnog.net></meyp282mb259749bec4880e7dc9f3993c82499@meyp282mb2597.ausp282.prod.outlook.com></ausnog@lists.ausnog.net></chris.chaundy@gmail.com></glipschitz@summitinternet.com.au></http:></mailto:chris.chaundy@gmail.com></ausnog@lists.ausnog.net></andy@andyblu.me></c36d807a-5e82-455d-d664-d97d14cb1b56@studio442.com.au></ausnog@lists.ausnog.net></ausnog@studio442.com.au></da321e92-48ca-424e-9471-a50e1ac412a0@gmail.com></ausnog@lists.ausnog.net></chris.chaundy@gmail.com></http:></cao6obbh5xhh59e+v4pb-hlgeuets=qze0bdyu5pduvhdedaffq@mail.gmail.com></simon275@gmail.com></http:></mark@innaloo.net></campv8mqcn+bbzm6t=e7mqoeh+i7hyx8bw28lpv0lji4fmxhffa@mail.gmail.com></ausnog@ausnog.net></mark@innaloo.net></dazzagibbs@gmail.com></http:></ausnog@ausnog.net></mark@innaloo.net></div></blockquote></div><img class="mailbird" width="1" height="1" style="border:0; width:1; height:1; display: none;" src="https://tracking.getmailbird.com/OpenTrackingPixel/?messageId=Mailbird-8b9ec398-6b26-4652-9a8e-6c0e6ea9bb13@10mates.com.au&senderHash=D0BC42A052E9E265CFF8A4AE5C2236067125263828677B7CE7F613CAE75477D4&recipientHash=73EB0A03692E8CB83746BB625CB4E2D6945D459D2357D9C621174C7183266C32&internalId=63db56ed-017d-4377-8bdb-2e07655ee0f9" alt="074055ca-183a-4963-a3b4-493d89700511">