Re: [pfSense Support] PPTP User Error 1.2 CF
Mmmm Haven't managed it so far, will keep an eye out for it. Log entries appended, if that is any help? Also is there a minimum no of characters for the password, a 5 digit one was input. Kind regards David Hingston > I got the following when adding a PPTP user: > > Fatal error: Cannot create references to/from string offsets nor overloaded > objects in /etc/inc/xmlparse.inc on line 57 > > It then reloaded a backup of the XML, and it seems the user was added, yet > to be confirmed. > > Is this any help to know? Is it something you can replicate? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] May 22 21:07:42 mpd: [pt15] using interface ng16 May 22 21:07:42 mpd: [pt15] ppp node is "mpd14078-pt15" May 22 21:07:42 mpd: [pt14] using interface ng15 May 22 21:07:42 mpd: [pt14] ppp node is "mpd14078-pt14" May 22 21:07:42 mpd: [pt13] using interface ng14 May 22 21:07:42 mpd: [pt13] ppp node is "mpd14078-pt13" May 22 21:07:42 mpd: [pt12] using interface ng13 May 22 21:07:42 mpd: [pt12] ppp node is "mpd14078-pt12" May 22 21:07:42 mpd: [pt11] using interface ng12 May 22 21:07:42 mpd: [pt11] ppp node is "mpd14078-pt11" May 22 21:07:42 mpd: [pt10] using interface ng11 May 22 21:07:42 mpd: [pt10] ppp node is "mpd14078-pt10" May 22 21:07:42 mpd: [pt9] using interface ng10 May 22 21:07:42 mpd: [pt9] ppp node is "mpd14078-pt9" May 22 21:07:42 mpd: [pt8] using interface ng9 May 22 21:07:42 mpd: [pt8] ppp node is "mpd14078-pt8" May 22 21:07:42 mpd: [pt7] using interface ng8 May 22 21:07:42 mpd: [pt7] ppp node is "mpd14078-pt7" May 22 21:07:42 mpd: [pt6] using interface ng7 May 22 21:07:42 mpd: [pt6] ppp node is "mpd14078-pt6" May 22 21:07:42 mpd: [pt5] using interface ng6 May 22 21:07:42 mpd: [pt5] ppp node is "mpd14078-pt5" May 22 21:07:42 mpd: [pt4] using interface ng5 May 22 21:07:42 mpd: [pt4] ppp node is "mpd14078-pt4" May 22 21:07:42 mpd: [pt3] using interface ng4 May 22 21:07:42 mpd: [pt3] ppp node is "mpd14078-pt3" May 22 21:07:42 mpd: [pt2] using interface ng3 May 22 21:07:42 mpd: [pt2] ppp node is "mpd14078-pt2" May 22 21:07:42 mpd: [pt1] using interface ng2 May 22 21:07:42 mpd: [pt1] ppp node is "mpd14078-pt1" May 22 21:07:41 mpd: [pt0] using interface ng1 May 22 21:07:41 mpd: mpd: local IP address for PPTP is 0.0.0.0 May 22 21:07:41 mpd: [pt0] ppp node is "mpd14078-pt0" May 22 21:07:41 mpd: mpd: pid 14078, version 3.18 ([EMAIL PROTECTED] 12:32 6-Jan-2008) May 22 21:07:40 mpd: mpd: process 577 terminated May 22 21:07:38 mpd: [pt15] IFACE: Close event May 22 21:07:38 mpd: [pt15] IPCP: Down event May 22 21:07:38 mpd: [pt14] IFACE: Close event May 22 21:07:38 mpd: [pt14] IPCP: Down event May 22 21:07:38 mpd: [pt13] IFACE: Close event May 22 21:07:38 mpd: [pt13] IPCP: Down event May 22 21:07:38 mpd: [pt12] IFACE: Close event May 22 21:07:38 mpd: [pt12] IPCP: Down event May 22 21:07:38 mpd: [pt11] IFACE: Close event May 22 21:07:38 mpd: [pt11] IPCP: Down event May 22 21:07:38 mpd: [pt10] IFACE: Close event May 22 21:07:38 mpd: [pt10] IPCP: Down event May 22 21:07:38 mpd: [pt9] IFACE: Close event May 22 21:07:38 mpd: [pt9] IPCP: Down event May 22 21:07:38 mpd: [pt8] IFACE: Close event May 22 21:07:38 mpd: [pt8] IPCP: Down event May 22 21:07:38 mpd: [pt7] IFACE: Close event May 22 21:07:38 mpd: [pt7] IPCP: Down event May 22 21:07:38 mpd: [pt6] IFACE: Close event May 22 21:07:38 mpd: [pt6] IPCP: Down event May 22 21:07:38 mpd: [pt5] IFACE: Close event May 22 21:07:38 mpd: [pt5] IPCP: Down event May 22 21:07:38 mpd: [pt4] IFACE: Close event May 22 21:07:38 mpd: [pt4] IPCP: Down event May 22 21:07:38 mpd: [pt3] IFACE: Close event May 22 21:07:38 mpd: [pt3] IPCP: Down event May 22 21:07:38 mpd: [pt2] IFACE: Close event May 22 21:07:38 mpd: [pt2] IPCP: Down event May 22 21:07:38 mpd: [pt1] IFACE: Close event May 22 21:07:38 mpd: [pt1] IPCP: Down event May 22 21:07:38 mpd: [pt0] IFACE: Close event May 22 21:07:38 mpd: [pt0] IPCP: Down event May 22 21:07:38 mpd: mpd: caught fatal signal term May 22 21:05:17 php: /sajax/index.sajax.php: New alert found: pfSense is restoring the configuration /conf/backup/config-1209343754.xml May 22 21:05:17 php: /sajax/index.sajax.php: pfSense is restoring the configuration /conf/backup/config-1209343754.xml May 22 21:05:14 php: /sajax/index.sajax.php: New alert found: No config.xml found, attempting last known config restore. May 22 21:05:14 php: /sajax/index.sajax.php: No config.xml found, attempting last known config restore. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] PPTP User Error 1.2 CF
Maybe spoke too soon, This is also logged following adding and taking away a new PPTP user: May 25 20:23:24 last message repeated 2 times May 25 20:23:39 php: /sajax/index.sajax.php: [DEBUG] Lock recursion detected. Kind regards David Hingston > I got the following when adding a PPTP user: > > Fatal error: Cannot create references to/from string offsets nor overloaded > objects in /etc/inc/xmlparse.inc on line 57 > > It then reloaded a backup of the XML, and it seems the user was added, yet > to be confirmed. > > Is this any help to know? Is it something you can replicate? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] PPTP User Error 1.2 CF
On Sun, May 25, 2008 at 4:31 AM, Tortise <[EMAIL PROTECTED]> wrote: > Maybe spoke too soon, > This is also logged following adding and taking away a new PPTP user: > > May 25 20:23:24 last message repeated 2 times > May 25 20:23:39 php: /sajax/index.sajax.php: [DEBUG] Lock recursion detected. > That's what I suspected, a lock issue. We have some locking fixes in 1.2.1 which may resolve this. Are there multiple users logged into the admin interface simultaneously? That seems to be the primary thing that causes locking issues. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] VLAN Help
This newbie wants to setup a pfsense box with dual wan connections and 2 vlans to separate 2 networks. I created the virual ips as CARP with the VHID set to the vlan # I need and then added an interface on that Vlan. This connects to a Dell PowerConnect 3024 switch. When a test computer hooks into the switch port that I designate for vlan2 it receives an ip thats just of the regular lan dhcp and not the vlan network. In the switch I have tried to have both the uplink port as tagged and untagged but no go. I set the port to be on vlan2 and untagged same nothing. I tag the uplink port and then can't get an ip or ping the pfsense box until I untag it. If someone could point me in the right direction with this I would be most thankful. We are a computer shop and I want to separate the office network from the clients computers and when our phone system gets upgraded later this year to an asterisk based system it will have qos ready to setup. Even with a static ip set on the computer unable to ping. Wan1 - DSL | Wan2- Cable Modem LAN1-pfsense 192.168.5.x vlan2- 192.168.10.x vlan 3- 192.168.20.x Thank you in advance Paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] VLAN Help
Do you have vlan1, 2 and 3 tagged on your inside physical interface (BGE1) for me of pfsense. If not then you probably won't be able to get this to work. Try doing that, then configure the Dell switch as tagged on all three vlans on the port that connects to the firewall. Then select untagged when connecting to a workstation or server that is not vlan aware. This should fix your issue unless I did not understand your question correctly. -- Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com
Re: [pfSense Support] VLAN Help
Not sure if I know what you mean. In the pfsense firewall I have the basic lan as 192.168.5.x. Then I created virtual ip and vlan as #2 192.168.10.x. I figured if I created a vlan1 then it might conflict with the switch since it uses the default as vlan1. If I'm explaining that correctly. Maybe I should start here. I have 3 nics in the pfsense 2 of which will be used for WAN with failover. Default LAN has an ip 192.168.5.x that works correctly when untagged in the switch under default vlan1. I scoured the web to see how to setup vlan and am having a hard time for a new guy, Then in the pfsense I went to Interface >Assign>VLAN. add interface Parent Interface rl0 (LAN NIC) VLAN Tag 3, Description Bench. Under Interface Assignments added the new vlan. as VLAN3 on rl0. Enabled the interface and turned on the dhcp for it. In the switch added vlan with ID3 to match the router. untagged on port 1(test part) and port 25 (router port). DHCP times out. But if I take port 1 and remove from vlan3 and untag it under the default vlan it will get a 192.168.5.x address. From reading it does not sound like I need to trunk the ports since its only 1 switch. I even added a rule in the firewall under the new Bench Vlan to allow source Bench Lan any > any any to see if that might be an issue. Hopefully this will give an idea of what I have going on Curtis LaMasters wrote: Do you have vlan1, 2 and 3 tagged on your inside physical interface (BGE1) for me of pfsense. If not then you probably won't be able to get this to work. Try doing that, then configure the Dell switch as tagged on all three vlans on the port that connects to the firewall. Then select untagged when connecting to a workstation or server that is not vlan aware. This should fix your issue unless I did not understand your question correctly. -- Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] VLAN Help
If you leave an untagged vlan on the pfsense interface, the traffic will default to it. Not sure why that is The LAN interface should say "VLAN 1 on bge0 (VLAN1)" ...if this is so then your other VLAN's should follow suite. For the switchport connected to pfsense, it should be tagged (Trunked in Cisco Terms) on all VLANs. After those steps are completed, you should be able to plug in a host on the switch with an untagged VLAN interface and be able to pass traffic. There's probably other ways to do this but I do know this method works 100% of the time. What NIC's are you running? -- Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com
Re: [pfSense Support] VLAN Help
For some reason I locked my self out remotely out of the desktop with a tftp server install. Port25 is connected to the router so I tagged it on all vlan's and left the ports to the computer untagged under its designated vlan setup. In the pfsense I created a vlan1 to match the default on the switch and changed LAN from rl0 to vlan1 on rl0. Still not passing dhcp or if set static can;t ping. When I'm back in the office on Tues I'll do a firmware update on the switch and post back. Thank you for you help. I starting to figure it out and unfortunately I learn better by doing then reading.. Should I only trunk the connecting ports if I add another switch vlan on the pfsense interface, the traffic will default to it. Not sure why that is The LAN interface should say "VLAN 1 on bge0 (VLAN1)" ...if this is so then your other VLAN's should follow suite. For the switchport connected to pfsense, it should be tagged (Trunked in Cisco Terms) on all VLANs. After those steps are completed, you should be able to plug in a host on the switch with an untagged VLAN interface and be able to pass traffic. There's probably other ways to do this but I do know this method works 100% of the time. What NIC's are you running? -- Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] VLAN Help
on the NIC's 2 are surplus realtek and not sure on the 3rd one. The lan nic is on the realtek though. Might there be an issue with the nic passing the vlan tagging even though the pfsense states only nics capable of it are listed. Curtis LaMasters wrote: If you leave an untagged vlan on the pfsense interface, the traffic will default to it. Not sure why that is The LAN interface should say "VLAN 1 on bge0 (VLAN1)" ...if this is so then your other VLAN's should follow suite. For the switchport connected to pfsense, it should be tagged (Trunked in Cisco Terms) on all VLANs. After those steps are completed, you should be able to plug in a host on the switch with an untagged VLAN interface and be able to pass traffic. There's probably other ways to do this but I do know this method works 100% of the time. What NIC's are you running? -- Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] load balancing outbound connections?
I'm trying to figure out if it's possible to bond two DSL lines in software - assume for a moment that I have a machine in a co-lo with 100Mbit connectivity running FreeBSD 7 (10ms away from my DSL) - if I were to add a second DSL and make two ipsec tunnels to the co-lo box - one over each dsl - would pfsense do the "right thing" and queue packets on the tunnel with the lowest queue size? (or at least alternate?) Or is this a bad idea for other reasons (like the greatly increased probability of out of order packets?) John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
