add netcup ipv6 fbsd post

ponderings/ms-exchange-room-calendar-title-replaced-by-organiser/index.html

@@ -120,27 +120,27 @@ This may well be a desirable feature, but in the case it isn't, this is how it c
 <h3 id="powershell-to-the-rescue">Powershell to the rescue!</h3>
 <p>A single Powershell command can be used to set some options on a calendar to change the way that calendars processing works.<br />
 First, connect to Exchange Online:</p>
-<pre data-lang="pwsh" style="background-color:#212121;color:#eeffff;" class="language-pwsh "><code class="language-pwsh" data-lang="pwsh"><span>Connect-ExchangeOnline
+<pre data-lang="powershell" style="background-color:#212121;color:#eeffff;" class="language-powershell "><code class="language-powershell" data-lang="powershell"><span style="color:#82aaff;">Connect-ExchangeOnline
 </span></code></pre>
 <p>Once connected, you can issue the following command to show the current options for a particular calendar's processing:</p>
-<pre data-lang="pwsh" style="background-color:#212121;color:#eeffff;" class="language-pwsh "><code class="language-pwsh" data-lang="pwsh"><span>Get-CalendarProcessing - Identity &quot;{The Calendar Name}&quot; | fl
+<pre data-lang="powershell" style="background-color:#212121;color:#eeffff;" class="language-powershell "><code class="language-powershell" data-lang="powershell"><span style="color:#82aaff;">Get-CalendarProcessing </span><span style="color:#89ddff;">-</span><span> Identity </span><span style="color:#89ddff;">&quot;</span><span style="color:#c3e88d;">{The Calendar Name}</span><span style="color:#89ddff;">&quot; |</span><span> fl
 </span></code></pre>
 <p>Which should show something like the below:</p>
-<pre data-lang="pwsh" style="background-color:#212121;color:#eeffff;" class="language-pwsh "><code class="language-pwsh" data-lang="pwsh"><span>AutomateProcessing                   : AutoAccept
+<pre data-lang="powershell" style="background-color:#212121;color:#eeffff;" class="language-powershell "><code class="language-powershell" data-lang="powershell"><span>AutomateProcessing                   : AutoAccept
 </span><span>AllowConflicts                       : False
 </span><span>AllowDistributionGroup               : True
 </span><span>AllowMultipleResources               : True
 </span><span>BookingType                          : Standard
-</span><span>BookingWindowInDays                  : 180
+</span><span>BookingWindowInDays                  : </span><span style="color:#f78c6c;">180
-</span><span>MaximumDurationInMinutes             : 1440
+</span><span>MaximumDurationInMinutes             : </span><span style="color:#f78c6c;">1440
-</span><span>MinimumDurationInMinutes             : 0
+</span><span>MinimumDurationInMinutes             : </span><span style="color:#f78c6c;">0
 </span><span>AllowRecurringMeetings               : True
 </span><span>EnforceAdjacencyAsOverlap            : False
 </span><span>EnforceCapacity                      : False
 </span><span>EnforceSchedulingHorizon             : True
 </span><span>ScheduleOnlyDuringWorkHours          : False
-</span><span>ConflictPercentageAllowed            : 0
+</span><span>ConflictPercentageAllowed            : </span><span style="color:#f78c6c;">0
-</span><span>MaximumConflictInstances             : 0
+</span><span>MaximumConflictInstances             : </span><span style="color:#f78c6c;">0
 </span><span>ForwardRequestsToDelegates           : True
 </span><span>DeleteAttachments                    : True
 </span><span>DeleteComments                       : True
@@ -151,12 +151,12 @@ First, connect to Exchange Online:</p>
 </span><span>TentativePendingApproval             : True
 </span><span>EnableResponseDetails                : True
 </span><span>OrganizerInfo                        : True
-</span><span>ResourceDelegates                    : {**Names of delegates are here**}
+</span><span>ResourceDelegates                    : </span><span style="color:#89ddff;">{**</span><span>Names of delegates are here</span><span style="color:#89ddff;">**}
-</span><span>RequestOutOfPolicy                   : {}
+</span><span>RequestOutOfPolicy                   : </span><span style="color:#89ddff;">{}
 </span><span>AllRequestOutOfPolicy                : False
-</span><span>BookInPolicy                         : {}
+</span><span>BookInPolicy                         : </span><span style="color:#89ddff;">{}
 </span><span>AllBookInPolicy                      : False
-</span><span>RequestInPolicy                      : {}
+</span><span>RequestInPolicy                      : </span><span style="color:#89ddff;">{}
 </span><span>AllRequestInPolicy                   : True
 </span><span>AddAdditionalResponse                : False
 </span><span>AdditionalResponse                   :
@@ -167,7 +167,7 @@ First, connect to Exchange Online:</p>
 </span><span>AutoRSVPConfiguration                : Microsoft.Exchange.Data.Storage.AutoRSVPConfiguration
 </span><span>RemoveCanceledMeetings               : False
 </span><span>EnableAutoRelease                    : False
-</span><span>PostReservationMaxClaimTimeInMinutes : 10
+</span><span>PostReservationMaxClaimTimeInMinutes : </span><span style="color:#f78c6c;">10
 </span><span>MailboxOwnerId                       : Room Calendar Name
 </span><span>Identity                             : Room Calendar Name
 </span><span>IsValid                              : True
@@ -175,11 +175,11 @@ First, connect to Exchange Online:</p>
 </span></code></pre>
 <p>You'll see there are a few options set to "True" which could be toggled - <code>Delete Subject</code>, <code>Delete Comments</code> and <code>Delete Attachments</code> - they should be fairly self explanitory.
 You can toggle these options by issuing the following command:</p>
-<pre data-lang="pwsh" style="background-color:#212121;color:#eeffff;" class="language-pwsh "><code class="language-pwsh" data-lang="pwsh"><span>Set-CalendarProcessing -Identity &quot;Room Calendar Name&quot; -DeleteComments $false -DeleteSubject $false -DeleteAttachments $false
+<pre data-lang="powershell" style="background-color:#212121;color:#eeffff;" class="language-powershell "><code class="language-powershell" data-lang="powershell"><span style="color:#82aaff;">Set-CalendarProcessing </span><span style="color:#89ddff;">-</span><span>Identity </span><span style="color:#89ddff;">&quot;</span><span style="color:#c3e88d;">Room Calendar Name</span><span style="color:#89ddff;">&quot; -</span><span>DeleteComments </span><span style="color:#89ddff;">$</span><span style="color:#f78c6c;">false </span><span style="color:#89ddff;">-</span><span>DeleteSubject </span><span style="color:#89ddff;">$</span><span style="color:#f78c6c;">false </span><span style="color:#89ddff;">-</span><span>DeleteAttachments </span><span style="color:#89ddff;">$</span><span style="color:#f78c6c;">false
 </span></code></pre>
 <p>This simply disables those options, so now the subject, comments and attachments will not be deleted when the calendar processes the event.<br />
 There is one further options which may, or may not, be helpful to disable - <code>AddOrganizerToSubject</code>. This option adds the organizer's name to the start of the Subject. This may be useful, but my client also wanted this switched off which can be done with the following command (or, indeed, adding the flag to the previous command).</p>
-<pre data-lang="pwsh" style="background-color:#212121;color:#eeffff;" class="language-pwsh "><code class="language-pwsh" data-lang="pwsh"><span>Set-CalendarProcessing -Identity &quot;Room Calendar Name&quot; -AddOrganizerToSubject $false
+<pre data-lang="powershell" style="background-color:#212121;color:#eeffff;" class="language-powershell "><code class="language-powershell" data-lang="powershell"><span style="color:#82aaff;">Set-CalendarProcessing </span><span style="color:#89ddff;">-</span><span>Identity </span><span style="color:#89ddff;">&quot;</span><span style="color:#c3e88d;">Room Calendar Name</span><span style="color:#89ddff;">&quot; -</span><span>AddOrganizerToSubject </span><span style="color:#89ddff;">$</span><span style="color:#f78c6c;">false
 </span></code></pre>
 <p>And there we are, new events now will appear in the calendar as desired - with full Subject, Comments and Attachments.<br />
 Previous entries will not update automatically, the organizer must go into each one and re-send it (no need to change anything, just re-send it and press "Send Anyway") which will update the event in the room calendar as desired.</p>

ponderings/my-battles-with-netcup-ipv6-on-freebsd/index.html

@@ -135,7 +135,7 @@ they have provided, but they also sent one via email, so I'll just use that for
 </span></code></pre>
 <p><code>2a03:4000</code> is Netcup's network I believe with <code>AAAA</code> defining a certain part of that network.<br />
 <code>BBBB</code> is the subnet provided to me with <code>cccc:dddd:eeee:ffff</code> being the range of address I can use in that subnet.</p>
-<p>Netcup's IPv6 network is switched, not routed, I'm sure there's a reason for this, and I'm sure it's sensible, but for now the important bit is that the IPv6 gateway should always be <code>fe80::1%vtnet0</code> (where <code>vtnet0</code> is the external interface name) rather than another <code>2a03:4000::AAAA:BBBB</code> IPv6 address. I pop that into my <code>rc.conf</code> as well.</p>
+<p>Netcup's IPv6 network is switched, not routed, I'm sure there's a reason for this, and I'm sure it's sensible, but for now the important bit is that the IPv6 gateway should always be <code>fe80::1%vtnet0</code> (where <code>vtnet0</code> is the external interface name) rather than another <code>2a03:4000:AAAA:BBBB</code> IPv6 address. I pop that into my <code>rc.conf</code> as well.</p>
 <pre data-lang="conf" style="background-color:#212121;color:#eeffff;" class="language-conf "><code class="language-conf" data-lang="conf"><span style="color:#89ddff;">...
 </span><span style="color:#f78c6c;">ipv6_defaultrouter</span><span style="color:#89ddff;">=</span><span style="color:#c3e88d;">&quot;fe80::1%vtnet0&quot;
 </span><span style="color:#89ddff;">...