Logo
 
Upper Toolbar Picture
HOME      ISP PPPoE      SUBSCRIBER PPPoE      TR-069 FAQs      CONTACT      SEARCH      FORUMS      SEARCH ENGINE OPTIMIZATION
Lower Toolbar Picture

Ethernet Picture

  What is PPPoE?
  Why PPPoE?
  PPPoE vs PPPoA
  PPPoE vs PPTP
  PPPoE Client
  PPPoE Server
  Offloading PPPoE
  RFC 2516
  Windows PPPoE
  Windows XP PPPoE
  Windows Vista PPPoE
  MAC PPPoE
  MAC OS X PPPoE
  Sony PSP PPPoE
  Networking with PPPoE
  Tweaking
  Broadband Links
  Download Limits
  Search Optimization

PPPoE Picture PPPoE Part 2 PPPoE Spacer


Why would an ISP want to deploy 3rd party software on Mac OS X / 10 instead of just letting their customers use the native PPPoE

Brand Management
When ever 3rd party applications are launched the customer is “forced” to see the ISPs branding on the connect screen of, MacPoET, for example
With, MacPoET, for example by default upon install you can force the browser to launch after connect and force the user to go to your web site again reinforcing brand management

Reduce Support Costs
Since OS X is the only Mac OS to have native PPPoE a client needs to be rolled out anyway, so why trouble shoot two clients instead of just one? If the provider supports 1 application and Mac OS X native the provider must train it’s call center to support both, if the Provider only supports 1 application training costs are less, as well as training time, as well as support time since only one “client” needs to be supported.

I need help with Mac OS X Native PPPoE
See our Mac OS X Native XP PPPoE help page