Mlppp hack for pfsense 2.0
-
I do not think yo uneed this:
new -i pppoe0 pppoeclient pppoeclientTo integrate this into pfSense gui it is simple enough to just copy paste the vlan config pages.
interface_vlan.php and interface_vlan_edit.php from there on is just adding removing pppoe settings.
After you have those pages ok you just need to add the multilink pppoe type to the interfaces assign page and
copy the interface_pppoe_configure() in interfaces.inc to interface_multilink_configure() and add the neccessary settings.
It is not too much work once you get to it. -
i removed that line from the config and reconnected. seems fine.
i'll also work on those config pages you mentioned.
-
rsingh, I'm mlppp-enabled on teksavvy, and getting my second ADSL line Friday. I'm using 1.2.3-Release currently and would like to test what you've got. Does the procedure you posted at the dlsr forum work for you in 1.2.3 or do you have any recommended modifications?
edit: I tried your 2.0 instructions on 1.2.3 and got a missing library error when trying to run mpd5 in the shell. I'll try it on 2.0 as soon as I can get PFS to boot up.
-
I'm working on getting this functionality into the pfSense code base.
I need to know, do the two DSL lines have different usernames and passwords, or are they the same?Thanks,
GNB -
rsingh, I'm mlppp-enabled on teksavvy, and getting my second ADSL line Friday. I'm using 1.2.3-Release currently and would like to test what you've got. Does the procedure you posted at the dlsr forum work for you in 1.2.3 or do you have any recommended modifications?
edit: I tried your 2.0 instructions on 1.2.3 and got a missing library error when trying to run mpd5 in the shell. I'll try it on 2.0 as soon as I can get PFS to boot up.
these instructions will not work for 1.2.3. You need to recompile mpd5 in freebsd 7.1 (i think 1.2.3 uses this) and then copy all of the libraries from your 7.1 system to 1.2.3. I did this, i found it didn't work well and abandonned it.
-
I'm working on getting this functionality into the pfSense code base.
I need to know, do the two DSL lines have different usernames and passwords, or are they the same?Thanks,
GNBin my case, the usernames are the same. people on the ISP i'm on and many other canadian ISPs that run mlppp will have just one account but the provider allows that one account to log in twice for the purposes of mlppp. this may not be true for everyone though.
if this is to be implemented in the code base, it may be simpler to ask the user to edit the config file manually. the mss, mru, mrru, mtu settings i use in my conf file may not be optimal for everyone.
-
I need to know, do the two DSL lines have different usernames and passwords, or are they the same?
I don't know the answer for sure, but rsingh indicated at the top of this thread that he is on the same ISP as me, so I'm going to go with him and say they are the same.
-
My ISP is looking at implementing mlppp on their network in the near future as well and I would also be grateful for any work done to make this a simple thing to enable from the web interface.
Thanks for all the work that has gone into this so far. -
Anything new to report here? Some clarification would be good too: are you still working on mlppp functionality at this point, or is that a wrap and you're just packaging it now?
-
It's ready.
I'm now just making the existing PPPoE and PPtP code store the config data the same way the new code does it, and writing functions to upgrade existing config to the new data structures.
GB
-
I've got a 2-link mlppp connection at home right now, running on mlppp-enabled Tomato firmware. I'll be happy to test pfsense on the connection when you get to that point with it.
-
Here's a .tar file with updated files. The brave and skilled can test them out.
Instructions
1. Delete existing PPP, PPPoE, and PPtP configurations.
2. Unpack (tar -xzf mlppp.tgz.txt) the files in the attached archive into the proper directories on pfsense host. If you save the archive in your / directory and then extract it every file should end up in its proper place. If you're running nanobsd image, don't forget to do /etc/rc.conf_mount_rw first to make the file system writeable.
3. Create new PPP, PPPoE, and PPtP configurations in the GUI. (Use the "PPPs" tab to make advanced configurations for multilink.)Good Luck. Let me know how it goes.
Disclaimer: This is not committed yet. It may change later.Gabriel
-
Very cool. I'll have a look in the next couple days and post my experience here.
db
-
File I attached doesn't extract properly. PM your email address to me if you want to help test this stuff.
GB
-
Success here on the nano image. 8)
Some bugginess in the setup, which may be in the mlppp files, or it could just be the pfsense beta.
-
Can you give me details of bugginess, and post your mpd_wan.conf file (located in /var/etc/ directory)?
Thanks,
GB -
Two or three times while setting things up I was not able to get any IP functionality into or through pfsense, other than dhcp. I could ping LAN and internet hosts from pfsense (on the console) and get a response–with one exception, where I couldn't get any ping response even from the console--but when pinging pfsense from a LAN client I got no response, even though arp resolution was happening. I hadn't touched the firewall rules, so the antilockout rule definitely should have been in effect. I think this happened after changing the IP address of an interface from the webUI, but I'm not sure. The only way I found to correct this situation was to use the console option to restore default settings. I did this 2 or 3 times.
The other thing I noticed is that sometimes on the interfaces_assign.php page the network port for LAN and OPT1 would show up as "()" instead of vr2 or vr2_vlan1 as the case may be. Despite this, I was still able to interact with pfsense on the webUI.
And finally, on the interfaces_ppps.php page, before adding any entry, there was already a blank entry, which when I tried to delete it I got some message, like I can't delete it because it's in use. After I created an mlppp entry on this page and assiged it to the WAN I was then able to delete the blank entry. I think deleting the blank entry may have corrected the () issue I described in the previous paragraph, as I'm not seeing it now.
I've attached the file you requested, although I'm not seeing any of these problems at the moment.
-
I'm not sure what was happening with respect to the pinging issues.
You're guess is correct. The network port showing up as "()" was related to the blank entry on interfaces_ppps.php. That blank entry was an empty tag in your config.xml file that resulted from bugs that should be fixed in that latest file set I just emailed you. You were still able to interact with the box when seeing these because the error was in the GUI, and the actual configuration of the LAN port hadn't changed.
GB
-
i was all set to try this out tonight but ran into some problems: vmware server no longer gives me console access to any of my VMs (pfsense is running in vmware). i have to carefully fix this first without screwing up anything (otherwise i won't be able to fix it) before the pfsense 2.0 testing.
-
I'm not sure what was happening with respect to the pinging issues.
I think I may have been trying to do setup on the WAN using the standard interfaces.php?if=wan page before creating my multilink pppoe interface on interfaces_ppps.php. I had to play with it a bit and set it up a few times to really grok the new pages. It seems to me the interfaces.php?if=wan page is redundant (except for the RFC1918 and Bogon buttons) and potentially dangerous if settings there could conflict with or overwrite settings made to the ppps page.
I'll try the updated files and report back. Thanks for the quick response.