<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[PPPoE Server doesn&#x27;t have &quot;service name&quot; entry]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">I am planning on using PfSense as a PPPoE server for multiple clients. Due to the nature of my setup, there will be 4x separate PfSense boxes running on the same physical wire (through a managed switch). When using PfSense as a server, the entry of the "service name" is not available, meaning that when a client tries to connect, it will connect to the first PfSense box that responds to the discovery command.</p>
<p dir="auto"><img src="/assets/uploads/files/1562061640846-67938bd0-e4d8-410e-8b72-b12300051338-image.png" alt="67938bd0-e4d8-410e-8b72-b12300051338-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">However....</p>
<p dir="auto">When using a PfSense to connect to a PPPoE server on it's wan connection, there is an option to enter a "service name" field, which would tell this connection which server it needs to connect to.</p>
<p dir="auto"><img src="/assets/uploads/files/1562061567200-43a3be54-1c27-41af-b1d6-b151b854dd6f-image.png" alt="43a3be54-1c27-41af-b1d6-b151b854dd6f-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">Am i missing something? It seems as PfSense supports the "service name" field when connecting into a PPPoE server, however when acting a PPPoE server, it cannot support "Service Names"</p>
<p dir="auto">Thanks,</p>
<p dir="auto">Russell.</p>
]]></description><link>https://forum.netgate.com/topic/144603/pppoe-server-doesn-t-have-service-name-entry</link><generator>RSS for Node</generator><lastBuildDate>Thu, 18 Jun 2026 05:21:55 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/144603.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 02 Jul 2019 10:04:48 GMT</pubDate><ttl>60</ttl></channel></rss>