<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Problem with replacing BT Hub in Archive</title>
    <link>https://business.forums.bt.com/t5/Archive/Problem-with-replacing-BT-Hub/m-p/82096#M26402</link>
    <description>&lt;P&gt;I'm replacing a BT hub with a dedicated PC running OPNSense (a fork of pfsense). I've set up quite a few of these on non BT customers connections and had no problems.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I get everything to connect, using an HG612 modem with a PPPoE connection set up on the OPNSense box. It gets internet and everything seemed to work correctly. However, when I opened Outlook, I received a message from the exchange email set up on it that is the similar to the one described here&amp;nbsp;&lt;A href="https://support.microsoft.com/en-gb/help/2772058/the-name-on-the-security-certificate-is-invalid-or-does-not-match-the" target="_self"&gt;https://support.microsoft.com/en-gb/help/2772058/the-name-on-the-security-certificate-is-invalid-or-does-not-match-the&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Except the last line of text says the problem lies with Cloudflare rejecting the certificate. The OPNSense box is not configured to use Cloudflare for DNS. I asked the provider of the exchange email and they said they could not help. I am wondering if I need any particular DNS setting applied at the PPPoE connection.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried adding a new email address and the same message appeared rejecting the autodiscover info because of Cloudflare. It happens on every computer connected to the network when the OPNSense box is used.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone shed any light on this?&lt;/P&gt;</description>
    <pubDate>Tue, 09 Jul 2019 07:30:22 GMT</pubDate>
    <dc:creator>AngusStewart</dc:creator>
    <dc:date>2019-07-09T07:30:22Z</dc:date>
    <item>
      <title>Problem with replacing BT Hub</title>
      <link>https://business.forums.bt.com/t5/Archive/Problem-with-replacing-BT-Hub/m-p/82096#M26402</link>
      <description>&lt;P&gt;I'm replacing a BT hub with a dedicated PC running OPNSense (a fork of pfsense). I've set up quite a few of these on non BT customers connections and had no problems.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I get everything to connect, using an HG612 modem with a PPPoE connection set up on the OPNSense box. It gets internet and everything seemed to work correctly. However, when I opened Outlook, I received a message from the exchange email set up on it that is the similar to the one described here&amp;nbsp;&lt;A href="https://support.microsoft.com/en-gb/help/2772058/the-name-on-the-security-certificate-is-invalid-or-does-not-match-the" target="_self"&gt;https://support.microsoft.com/en-gb/help/2772058/the-name-on-the-security-certificate-is-invalid-or-does-not-match-the&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Except the last line of text says the problem lies with Cloudflare rejecting the certificate. The OPNSense box is not configured to use Cloudflare for DNS. I asked the provider of the exchange email and they said they could not help. I am wondering if I need any particular DNS setting applied at the PPPoE connection.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried adding a new email address and the same message appeared rejecting the autodiscover info because of Cloudflare. It happens on every computer connected to the network when the OPNSense box is used.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone shed any light on this?&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jul 2019 07:30:22 GMT</pubDate>
      <guid>https://business.forums.bt.com/t5/Archive/Problem-with-replacing-BT-Hub/m-p/82096#M26402</guid>
      <dc:creator>AngusStewart</dc:creator>
      <dc:date>2019-07-09T07:30:22Z</dc:date>
    </item>
  </channel>
</rss>

