Mlppp hack for pfsense 2.0
-
I suppose the implicated php files will not get overwritten on an upgraded once your package is integrated into the base release.
Yes, you're right. Once these files are integrated you won't see this behavior.
The other thing I noticed before and after my firmware update is that instead of seeing interface names on the Status>Interfaces page, such as "LAN interface (vr2_vlan1)", I see no name, ie, "LAN interface ()". This is true for all interfaces.
I'm not sure about the cause of this. The code that displays the interface info was modified recently by other devs. I'm running an image from May 12th on my two test boxes with my new changes and those "()" parentheses are displaying all the proper interface names. I'll check the newer code behind Status -> Interfaces soon.
GB
-
vmware 2.0 only works well with firefox 2.0… sigh. ah well, i'll test this sunday.
-
I suspect that the WAN traffic graph is reporting approximately double the actual traffic being passed, for outbound traffic only.
-
Hi,
Is this going to be in the 2.0 release? I can definitely use this with TekSavvy and stop thinking about moving to Tomato because of this shortcoming. However, I don't have the luxury to test this and it should be a 100% stable feature before I can get to it.
Thanks
-
Seeing that it's in the betas I can't see why it would get pulled.
I've been using it since it before it was in the builds (with TekSavvy) and haven't had any issue with it.
pfsense 2.0 isn't quite release-ready yet, but it's getting there, and the mlppp component is not really in question, as far as I can tell.
-
1- Sorry, I didn't get what you said. "It's not in question" ??? Is it going to BE or NOT TO BE in the 2.0 stable release?
I am assuming you are using this with a beta of 2.0 right as it's not supported in 1.2.3.2- Doesn't TekSavvy send you another router which takes two Rj-11 jacks? or do they send you two DSL modem for mlpp? If one mode only, do you put it in Bridge mode? If two modems, do you put both in bridge mode to use pfsense?
Thanks
-
I'm using 2.0 betas, and as far as I know I was the first one using the mlppp functionality from before it went into the snapshots. I haven't had a single problem with it and it's been in the snapshots for months now. I would be surprised if it was taken out at this point. There's no reason to. You may as well take out the traffic shaper or openvpn.
You will need a modem for every DSL connection. I don't buy my modems from TekSavvy, although you can if you want. They're cheaper through ncix.com, speedtouch.ca, and some other retailers.
Each modem then has to plug into pfsense, so your pfsense box needs either a physical port for each line, or you use a vlan-capable switch between the modems and your WAN port. This is what I do, as when adding more lines, you reach a point where having a whole bunch of NICs in your firewall box gets silly.
-
Thanks a lot for the clarification. I hope they do not take it out as I have read from a lot of people that the feature is working. Or at least leave an easy way to put it back in if need be.
I am using Alix board with three NIC ports. So, I should be fine.
-
We're not taking it out. :)
-
i'm using the built in mlppp in the latest version. i go to ppps and put 2 interfaces in. it connects, gets the right ip and everything. small packets like voip and online gaming UDP stuff is great. TCP like web browsing doesn't work properly. pages load part way and then stop.
i've tried the default mru/mtu/mrru values as well as ones that worked for me before: 1486/1486/1592. same result. any ideas? logs look ok:
Sep 6 00:17:47 ppp: [opt1] Bundle: Status update: up 2 links, total bandwidth 1011200 bps
Sep 6 00:17:47 ppp: [opt1_link1] Link: Join bundle "opt1"
Sep 6 00:17:47 ppp: [opt1_link1] LCP: authorization successful
Sep 6 00:17:47 ppp: [opt1_link1] PAP: rec'd ACK #1 len: 5
Sep 6 00:17:47 ppp: [opt1_link1] LCP: LayerUp
Sep 6 00:17:47 ppp: [opt1_link1] PAP: sending REQUEST #1 len: 49
Sep 6 00:17:47 ppp: [opt1_link1] PAP: using authname "removed"
Sep 6 00:17:47 ppp: [opt1_link1] LCP: auth: peer wants PAP, I want nothing
Sep 6 00:17:47 ppp: [opt1_link1] LCP: state change Ack-Sent –> Opened
Sep 6 00:17:47 ppp: [opt1_link1] ENDPOINTDISC [802.1] 00 0c 29 31 f8 8c
Sep 6 00:17:47 ppp: [opt1_link1] MP MRRU 1592
Sep 6 00:17:47 ppp: [opt1_link1] MAGICNUM e4720d58
Sep 6 00:17:47 ppp: [opt1_link1] MRU 1486
Sep 6 00:17:47 ppp: [opt1_link1] LCP: rec'd Configure Ack #4 (Ack-Sent)
Sep 6 00:17:47 ppp: [opt1_link1] ENDPOINTDISC [802.1] 00 0c 29 31 f8 8c
Sep 6 00:17:47 ppp: [opt1_link1] MP MRRU 1592
Sep 6 00:17:47 ppp: [opt1_link1] MAGICNUM e4720d58
Sep 6 00:17:47 ppp: [opt1_link1] MRU 1486
Sep 6 00:17:47 ppp: [opt1_link1] LCP: SendConfigReq #4
Sep 6 00:17:47 ppp: [opt1_link1] ENDPOINTDISC [NULL]
Sep 6 00:17:47 ppp: [opt1_link1] MP MRRU 32719
Sep 6 00:17:47 ppp: [opt1_link1] LCP: rec'd Configure Nak #3 (Ack-Sent)
Sep 6 00:17:47 ppp: [opt1_link1] LCP: state change Opened –> Ack-Sent
Sep 6 00:17:47 ppp: [opt1_link1] MAGICNUM 29958a83
Sep 6 00:17:47 ppp: [opt1_link1] AUTHPROTO PAP
Sep 6 00:17:47 ppp: [opt1_link1] ENDPOINTDISC [LOCAL] 34 36 30 37 32 33 30 30 39 39 00 00 00 00 00
Sep 6 00:17:47 ppp: [opt1_link1] MP MRRU 32719
Sep 6 00:17:47 ppp: [opt1_link1] MRU 1492
Sep 6 00:17:47 ppp: [opt1_link1] LCP: SendConfigAck #210
Sep 6 00:17:47 ppp: [opt1_link1] MAGICNUM e4720d58
Sep 6 00:17:47 ppp: [opt1_link1] MRU 1486
Sep 6 00:17:47 ppp: [opt1_link1] LCP: SendConfigReq #3
Sep 6 00:17:47 ppp: [opt1_link1] LCP: LayerDown
Sep 6 00:17:47 ppp: [opt1_link1] MAGICNUM 29958a83
Sep 6 00:17:47 ppp: [opt1_link1] AUTHPROTO PAP
Sep 6 00:17:47 ppp: [opt1_link1] ENDPOINTDISC [LOCAL] 34 36 30 37 32 33 30 30 39 39 00 00 00 00 00
Sep 6 00:17:47 ppp: [opt1_link1] MP MRRU 32719 -
Can you please show /tmp/rules.debug.
Possibly the scrub rules might be causing this.Also the /var/etc/mpd* contents.
-
ok it's not pfsense, same behavior with straight freebsd8. good job in adding mlppp though!