Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pppoe, allow configuring pppoe on a carp interface so its only active on the master #3830

Closed
wants to merge 1 commit into from

Conversation

PiBa-NL
Copy link
Contributor

@PiBa-NL PiBa-NL commented Sep 24, 2017

pppoe, allow configuring pppoe on a carp interface so its only active on the master

https://redmine.pfsense.org/issues/8184

@rbgarga
Copy link
Member

rbgarga commented Nov 1, 2017

@PiBa-NL please rebase your fork

Copy link
Contributor

@jim-p jim-p left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems OK, though I am very hesitant to encourage any kind of dynamic WAN use with HA/CARP VIPs as it will always break connectivity on one box, and give users unrealistic expectations about what will work in a proper HA setup.

@PiBa-NL PiBa-NL force-pushed the 20170925-pppoe-on-carpmaster branch from 4ea67d7 to 920c5f8 Compare November 1, 2017 23:02
@PiBa-NL
Copy link
Contributor Author

PiBa-NL commented Nov 1, 2017

@jim-p
broken connectivity on 1 box is indeed expected, there are probably workarounds possible around that though it gets complicated fast. kinda similar though where you would have wan-interfaces on a private ip while having a carp-ip for the public ip's to reduce overhead there (i used to run past years with 5 carp-ips on the our isp /29 subnet.. and private addresses on the interfaces). My goal is to have 2 pfSense boxes where if 1 fails or needs maintenance it can be turned off without much extra effort internal routing between vlans continues, and though it does break connectivity to the internet for a minute for the ppp to connect back.. then does restore connectivity.

In my current/new situation we have got 1 static pppoe IP and a routed /29 subnet from our new ISP, sofar this change seems to work for us.. not sure if this falls under your 'dynamic wan' criteria? but i don't have a better idea on how to have 2 pfSense boxes 'share' the single pppoe connection. they cant both actively connect as only 1 will receive the traffic.
i hope it is oke for merging like this.

@rbgarga
commit is rebased.

@jim-p
Copy link
Contributor

jim-p commented Nov 2, 2017

@PiBa-NL In that instance, you'd have the CPE perform PPPoE and expose the /29 directly on its back end (firewall WAN subnet), otherwise you get into a weird mess of broken connectivity and other complications. We are probably better off having this support in the tree, but I wouldn't encourage anyone to use it because of all the downsides. If they have no other choice, perhaps.

@rbgarga rbgarga removed the Conflicts label Nov 2, 2017
@PiBa-NL
Copy link
Contributor Author

PiBa-NL commented Nov 2, 2017

@jim-p, i'm not sure about your CPE proposal.. our fiber-provider installed a https://genexis.eu/product/fibertwist/ in the building and they 'manage' that device remotely, they provides a vlan for our internet-provider. The internet-provider then provides the internet service over the vlan. And we need to plug in a rj45 cable to and use pppoe over that. I suppose it would probably be possible to put a gateway device like small draytek in between to do the pppoe connection. But it seemed 'cleaner' to do it straight from pfSense itself. Maybe indeed it shouldn't be encourage'd to do it like this, but it seems like a nice possibility to have.. Now the pfSense box has 9 usable public IP's instead of just 5.

@jim-p
Copy link
Contributor

jim-p commented Dec 11, 2017

In an effort to improve the tracking of changes and bug/feature requests, we have decided to require an entry on the pfSense Redmine issue tracker associated with every pull request, and likewise the Redmine entry should also have a link back to the pull request.

If you could, please associate this PR to a Redmine issue either by locating an existing issue at https://redmine.pfsense.org or by creating a new issue. Add a link to the Redmine issue that points to this PR, and also add a link on the PR to the Redmine issue.

For more information, see https://doc.pfsense.org/index.php/Submitting_a_Pull_Request_via_Github

Thanks!

@mikes-gh
Copy link

What happened with this. I am guessing its a common senario?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants