Feature #446
closed
Enable ether interface to be reused (when used for PPPOE), like wireless clone
0%
Description
With ADSL modems with multiple ethernet ports (ie: switch and modem), it would be nice if the pfsense ethernet interface used for PPPOE (which would be connected to one of the ADSL ports) can be reused as a LAN interface. That vr* interface appears unused otherwise...
Typically, other hosts would be connected to the (ADSL modem) switch, and if the pfsense host was to be connected to the same LAN, then it would need another ethernet port on the pfsense host connected to another switch port (since the same vr* interface cant be used under interfaces). This is a waste, especially on 4 port switches where now 2 ports are connected to the pfsense host.
(I see you have wireless cloning - so its the same thing, but for ethernet...)
Updated by Chris Buechler about 14 years ago
Not sure it should be like wireless clone, but we do need some way to accommodate this in the future. It's also useful for accessing modems on their private IP, where you need to configure NAT and an alias on the parent interface for that, you're stuck with manual hacks right now.
Updated by Ermal Luçi about 14 years ago
This is doable only if you move PPPoE/PPTP to the interfaces->assign tabs.
This way there will be no problems doing this multiple assignment.
Updated by Marcus Brown about 14 years ago
The MLPPP tab I'm working on will allow it.
Updated by Nicholas Lee almost 14 years ago
Similarly it would be nice if two PPTP WAN connections could use the same physical interface.
If you have a couple ADSL modem that provides a PPTP<->PPPoA bridge it would be nice to either daisy-chain the modems via their own in-built switches or a separate switch off one ethernet port on the pfsense router.
Updated by Marcus Brown almost 14 years ago
This feature now exists. Builds after June 10th have the ability for accomodate multiple PPtP/PPPoE WAN connections over the same interface, and the ability to configure the same physical interface for DHCP or static IP etc.
Please test and close this ticket.
Updated by Nicholas Lee almost 14 years ago
Running "Jun 10 14:59" build and I had to add a floating "pass quick proto gre from subnet to internal IP". Otherwise some traffic was blocked by the default block rule.
Seems the pptp0 rule was set up, but not one for the underlying IP layer.
Updated by Nicholas Lee almost 14 years ago
It might be more useful to make the WAN and PPTP0 actual separate logical devices in the interface (assign) window. Something like WANand iWAN(vr0), all the other routing/firewall logic would then treat WAN and iWAN(vr0) normally.
Updated by Ermal Luçi almost 14 years ago
I am not sure what are you seeing here has any relevance to the underlying interface.
Can you post your configuration.
Updated by David Burgess almost 14 years ago
I am able to assign vr0 and vr1 to an mlppp interface, bring it up, then assign static IP addresses to parent interfaces vr0 and vr1. At this point I am able to communicate with my modems on vr0 and vr1 from pfsense. Up to this point things work as expected.
However, in trying to change the IP address of vr0 or vr1 after they are functioning, the address sometimes does not change after hitting the apply button.
Furthermore, there is a space of approximately 30 seconds or more where pfsense becomes unresponsive on the WAN interface after hitting the apply button. When I am again able to log into pfsense, the WAN address (mlppp) has changed. This behaviour regardless of whether the IP address of vr0 or vr1 is changed as expected.
Updated by Ermal Luçi over 13 years ago
This is expected behavior.
Since the vr1 or vr0 is part of the multilink when it goes down mpd will bring the link down and when it comes up again it will restart itself and come up again, possibly renegotiating the ip depending on ISP ppp config.