1-2 release - wan won't connect



  • I upgraded one 1.01 firewall to the 1.2 snapshot and wan won't connect.

    Then I did a clean install and still no connection.

    I had to downgrade to 1.01.

    Is the any thing different with PPPoE client?

    I have a speedtouch 510i router in bridge mode.



  • Mine works ok on PPOE through a roter on bridge mode to PPPOA



  • I did the exact same configuration, and didn't work.

    I don't know what is wrong ???



  • I have noticed a prob with the config on IPSEC not being taken over ok.  Maybe this has same prob. Try rekeying all the PPPOE data from your ISP and resave and apply the info.



  • I did the "Setup Wizard" several times, I did it on the wan tab, and rebooted the firewall.

    The result is the same.



  • goto interfaces then wan. Make sure PPPOE is selected then scroll down and put your details in.



  • @Jonb:

    goto interfaces then wan. Make sure PPPOE is selected then scroll down and put your details in.

    already made that.

    I noticed  that the wan IP appears in the log, but it won't connect.



  • What do you mean the WAN IP appears in the logs? With PPPoE you do not set a WAN IP, it's assigned by the ISP to you. What does status>interfaces tell about the WAN connection? Also can you paste some logs from the login attempts?



  • @hoba:

    What do you mean the WAN IP appears in the logs?

    Usually my wan IP is something like 85.2xx.xxx.xxx , and there was one IP like that in the logs.

    @hoba:

    What does status>interfaces tell about the WAN connection?

    It has the connect button.

    @hoba:

    Also can you paste some logs from the login attempts?

    I will, but only tomorrow. I'm not near it now.

    Thanks



  • Last 50 system log entries
    Apr 26 09:28:04	php: : WARNING! /etc/rc.newwanip could not deterimine the previous ip address ( wan ).
    Apr 26 09:28:07	php: : Informational: DHClient spawned /etc/rc.newwanip and the new ip is wan - .
    Apr 26 09:28:07	php: : Creating rrd update script
    Apr 26 09:28:09	php: : Configuring slbd
    Apr 26 09:28:09	check_reload_status: reloading filter
    Apr 26 09:28:10	dnsmasq[538]: reading /etc/resolv.conf
    Apr 26 09:28:10	dnsmasq[538]: using nameserver 212.55.154.174#53
    Apr 26 09:28:14	check_reload_status: updating dyndns
    Apr 26 09:29:08	mpd: MRU 1492
    Apr 26 09:29:08	mpd: MAGICNUM eccf7855
    Apr 26 09:29:09	mpd: MRU 1492
    Apr 26 09:29:09	mpd: AUTHPROTO PAP
    Apr 26 09:29:09	mpd: MAGICNUM 193e693f
    Apr 26 09:29:09	mpd: MRU 1492
    Apr 26 09:29:09	mpd: AUTHPROTO PAP
    Apr 26 09:29:09	mpd: MAGICNUM 193e693f
    Apr 26 09:29:09	mpd: MRU 1492
    Apr 26 09:29:09	mpd: MAGICNUM eccf7855
    Apr 26 09:29:09	mpd: IPADDR 0.0.0.0
    Apr 26 09:29:09	mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Apr 26 09:29:09	mpd: PRIDNS 0.0.0.0
    Apr 26 09:29:09	mpd: SECDNS 0.0.0.0
    Apr 26 09:29:11	mpd: IPADDR 0.0.0.0
    Apr 26 09:29:11	mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Apr 26 09:29:11	mpd: PRIDNS 0.0.0.0
    Apr 26 09:29:11	mpd: SECDNS 0.0.0.0
    Apr 26 09:29:11	mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Apr 26 09:29:11	mpd: SECDNS 0.0.0.0
    Apr 26 09:29:11	mpd: IPADDR 0.0.0.0
    Apr 26 09:29:11	mpd: PRIDNS 0.0.0.0
    Apr 26 09:29:11	mpd: IPADDR 85.240.109.153
    Apr 26 09:29:11	mpd: 85.240.109.153 is OK
    Apr 26 09:29:11	mpd: PRIDNS 212.55.154.174
    Apr 26 09:29:11	mpd: PRIDNS 212.55.154.174
    Apr 26 09:29:11	mpd: PRIDNS 212.55.154.174
    Apr 26 09:29:12	mpd: IPADDR 194.65.169.212
    Apr 26 09:29:12	mpd: 194.65.169.212 is OK
    Apr 26 09:29:12	mpd: IPADDR 194.65.169.212
    Apr 26 09:29:12	mpd: 85.240.109.153 -> 194.65.169.212
    Apr 26 09:29:12	check_reload_status: rc.newwanip starting
    Apr 26 09:29:14	php: : Informational: rc.newwanip is starting .
    Apr 26 09:29:14	php: : rc.newwanip working with IP address wan ed1.
    Apr 26 09:29:14	php: : WARNING! /etc/rc.newwanip could not deterimine the previous ip address ( wan ).
    Apr 26 09:29:16	php: : Informational: DHClient spawned /etc/rc.newwanip and the new ip is wan - .
    Apr 26 09:29:17	php: : Creating rrd update script
    Apr 26 09:29:19	php: : Configuring slbd
    Apr 26 09:29:19	check_reload_status: reloading filter
    Apr 26 09:29:22	dnsmasq[538]: reading /etc/resolv.conf
    Apr 26 09:29:22	dnsmasq[538]: using nameserver 212.55.154.174#53
    Apr 26 09:29:24	check_reload_status: updating dyndns
    


  • what version did you upgrade from



  • This is from a clean install.



  • I am having a similiar issue with the latest version.

    pfSense seems to get stuck at "Configuring WAN Interface" while booting up.



  • I would suggest installing 1.01 see if it works then upgrade to 1.2. I know futher up you have said that u upgraded from 1.01 to 1.2. Is this an embeded solution ur using. I am running full and I haven't had any problems.



  • 1.0.1 does not support my nics…. :-\

    1-2 seems to work it just takes some time for the WAN interface to timeout?

    Is anyone using the 1-2 version in production?



  • @Jonb:

    I would suggest installing 1.01 see if it works then upgrade to 1.2. I know futher up you have said that u upgraded from 1.01 to 1.2. Is this an embeded solution ur using. I am running full and I haven't had any problems.

    First I upgraded from 1.01 snapshot ( 15-04-2007 ) if I'm not mistaken.

    Then I did a clean install of 1.2 ( 23-04-2007 ).

    Then I instaled 1.01 - this one is working.

    The pictures are from live cd.

    I'm using one PC.

    Edit: Sorry, I meant 15-03-2007 and 27-03-2007.



  • I am using it at home with a 3com nic dailing PPPOE to an ADSL modem in bridge mode that provide VPN and VOIP to work from home. I am 1.2 and it is fine.



  • Hmmm I don't know then because that is exseaclty what I did for an upgrade to and mine has gone fine. I know they did change somthing to the PPPOE about 1 month ago and it didn't work and it was reverted back. I have heard of it going to the new type again



  • I did tried the last snapshot of 1.01 and it didn't work.

    Then reversed to the prior one ( 15-04-2007 ) if I'm not mistaken.

    Edit: Sorry, I meant 15-03-2007



  • I also noticed that when I change the lan IP address on the console, it doesn't change until I reboot.



  • Sounds very strange I haven't had any problem with PPPOE apart from that once and deffinatly not with changing the LAN ip.  I am out of suggestions.  I don't know wether the nic make any difference.



  • Changing the LAN IP from the web interface it's no problem.
    I have only noticed that when I did it on the console.



  • try unsetting the block prived networks option
    some isp give you first a prived ip and later a real ip
    if pfsense is in blokking mode then you will not get that real ip



  • @jeroen234:

    try unsetting the block prived networks option
    some isp give you first a prived ip and later a real ip
    if pfsense is in blokking mode then you will not get that real ip

    Did it with 2007-Apr-30 snaapshot, and it didn't work.

    
    Apr 30 21:00:41	mpd: MRU 1492
    Apr 30 21:00:41	mpd: MAGICNUM 7d5c1c8e
    Apr 30 21:00:41	mpd: MRU 1492
    Apr 30 21:00:41	mpd: AUTHPROTO PAP
    Apr 30 21:00:41	mpd: MAGICNUM 625207b8
    Apr 30 21:00:41	mpd: MRU 1492
    Apr 30 21:00:41	mpd: AUTHPROTO PAP
    Apr 30 21:00:41	mpd: MAGICNUM 625207b8
    Apr 30 21:00:41	mpd: MRU 1492
    Apr 30 21:00:41	mpd: MAGICNUM 7d5c1c8e
    Apr 30 21:00:42	mpd: IPADDR 0.0.0.0
    Apr 30 21:00:42	mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Apr 30 21:00:42	mpd: PRIDNS 0.0.0.0
    Apr 30 21:00:42	mpd: SECDNS 0.0.0.0
    Apr 30 21:00:44	mpd: IPADDR 0.0.0.0
    Apr 30 21:00:44	mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Apr 30 21:00:44	mpd: PRIDNS 0.0.0.0
    Apr 30 21:00:44	mpd: SECDNS 0.0.0.0
    Apr 30 21:00:45	mpd: IPADDR 194.65.169.212
    Apr 30 21:00:45	mpd: 194.65.169.212 is OK
    Apr 30 21:00:45	mpd: IPADDR 194.65.169.212
    Apr 30 21:00:46	mpd: IPADDR 0.0.0.0
    Apr 30 21:00:46	mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Apr 30 21:00:46	mpd: PRIDNS 0.0.0.0
    Apr 30 21:00:46	mpd: SECDNS 0.0.0.0
    Apr 30 21:00:46	mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Apr 30 21:00:46	mpd: SECDNS 0.0.0.0
    Apr 30 21:00:46	mpd: IPADDR 0.0.0.0
    Apr 30 21:00:46	mpd: PRIDNS 0.0.0.0
    Apr 30 21:00:46	mpd: IPADDR 85.243.197.162
    Apr 30 21:00:46	mpd: 85.243.197.162 is OK
    Apr 30 21:00:46	mpd: PRIDNS 212.55.154.174
    Apr 30 21:00:46	mpd: PRIDNS 212.55.154.174
    Apr 30 21:00:46	mpd: PRIDNS 212.55.154.174
    Apr 30 21:00:46	mpd: 85.243.197.162 -> 194.65.169.212
    Apr 30 21:00:46	mpd: mpd: caught fatal signal term
    Apr 30 21:00:48	mpd: mpd: process 298 terminated
    Apr 30 21:00:49	mpd: mpd: pid 1307, version 3.18 (root@builder6.pfsense.com 13:56 13-Feb-2007)
    Apr 30 21:00:50	check_reload_status: rc.newwanip starting
    Apr 30 21:01:21	check_reload_status: reloading filter
    Apr 30 21:01:22	dnsmasq[537]: exiting on receipt of SIGTERM
    Apr 30 21:01:23	dnsmasq[1607]: started, version 2.36 cachesize 150
    Apr 30 21:01:23	dnsmasq[1607]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N
    Apr 30 21:01:23	dnsmasq[1607]: reading /etc/resolv.conf
    Apr 30 21:01:23	dnsmasq[1607]: using nameserver 212.55.154.174#53
    Apr 30 21:01:23	dnsmasq[1607]: read /etc/hosts - 2 addresses
    Apr 30 21:01:24	dhcpd: Internet Systems Consortium DHCP Server V3.0.5
    Apr 30 21:01:24	dhcpd: Copyright 2004-2006 Internet Systems Consortium.
    Apr 30 21:01:24	dhcpd: All rights reserved.
    Apr 30 21:01:24	dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
    Apr 30 21:01:30	check_reload_status: reloading filter
    Apr 30 21:03:04	mpd: MRU 1492
    Apr 30 21:03:04	mpd: MAGICNUM f614ee1c
    Apr 30 21:03:04	mpd: MRU 1492
    Apr 30 21:03:04	mpd: AUTHPROTO PAP
    Apr 30 21:03:04	mpd: MAGICNUM 45c5024b
    Apr 30 21:03:04	mpd: MRU 1492
    Apr 30 21:03:04	mpd: AUTHPROTO PAP
    Apr 30 21:03:04	mpd: MAGICNUM 45c5024b
    Apr 30 21:03:04	mpd: MRU 1492
    Apr 30 21:03:04	mpd: MAGICNUM f614ee1c
    Apr 30 21:03:04	mpd: IPADDR 0.0.0.0
    Apr 30 21:03:04	mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Apr 30 21:03:04	mpd: PRIDNS 0.0.0.0
    Apr 30 21:03:04	mpd: SECDNS 0.0.0.0
    Apr 30 21:03:04	mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Apr 30 21:03:04	mpd: SECDNS 0.0.0.0
    Apr 30 21:03:04	mpd: IPADDR 0.0.0.0
    Apr 30 21:03:04	mpd: PRIDNS 0.0.0.0
    Apr 30 21:03:04	mpd: IPADDR 85.243.36.49
    Apr 30 21:03:04	mpd: 85.243.36.49 is OK
    Apr 30 21:03:04	mpd: PRIDNS 212.55.154.174
    Apr 30 21:03:04	mpd: PRIDNS 212.55.154.174
    Apr 30 21:03:04	mpd: PRIDNS 212.55.154.174
    Apr 30 21:03:07	mpd: IPADDR 194.65.169.212
    Apr 30 21:03:07	mpd: 194.65.169.212 is OK
    Apr 30 21:03:07	mpd: IPADDR 194.65.169.212
    Apr 30 21:03:07	mpd: 85.243.36.49 -> 194.65.169.212
    Apr 30 21:03:08	check_reload_status: rc.newwanip starting
    Apr 30 21:03:32	mpd: mpd: caught fatal signal term
    Apr 30 21:03:34	mpd: mpd: process 1307 terminated
    Apr 30 21:03:35	mpd: mpd: pid 2071, version 3.18 (root@builder6.pfsense.com 13:56 13-Feb-2007)
    Apr 30 21:04:08	dnsmasq[1607]: exiting on receipt of SIGTERM
    Apr 30 21:04:08	check_reload_status: reloading filter
    Apr 30 21:04:09	dnsmasq[2114]: started, version 2.36 cachesize 150
    Apr 30 21:04:09	dnsmasq[2114]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N
    Apr 30 21:04:09	dnsmasq[2114]: reading /etc/resolv.conf
    Apr 30 21:04:09	dnsmasq[2114]: using nameserver 212.55.154.174#53
    Apr 30 21:04:09	dnsmasq[2114]: read /etc/hosts - 2 addresses
    Apr 30 21:04:10	dhcpd: Internet Systems Consortium DHCP Server V3.0.5
    Apr 30 21:04:10	dhcpd: Copyright 2004-2006 Internet Systems Consortium.
    Apr 30 21:04:10	dhcpd: All rights reserved.
    Apr 30 21:04:10	dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
    Apr 30 21:04:16	mpd: mpd: caught fatal signal term
    Apr 30 21:04:18	mpd: mpd: process 2071 terminated
    Apr 30 21:04:19	mpd: mpd: pid 2280, version 3.18 (root@builder6.pfsense.com 13:56 13-Feb-2007)
    Apr 30 21:04:50	last message repeated 2 times
    Apr 30 21:04:51	dnsmasq[2114]: exiting on receipt of SIGTERM
    Apr 30 21:04:52	dnsmasq[2579]: started, version 2.36 cachesize 150
    Apr 30 21:04:52	dnsmasq[2579]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N
    Apr 30 21:04:52	dnsmasq[2579]: reading /etc/resolv.conf
    Apr 30 21:04:52	dnsmasq[2579]: using nameserver 212.55.154.174#53
    Apr 30 21:04:52	dnsmasq[2579]: read /etc/hosts - 2 addresses
    Apr 30 21:04:53	dhcpd: Internet Systems Consortium DHCP Server V3.0.5
    Apr 30 21:04:53	dhcpd: Copyright 2004-2006 Internet Systems Consortium.
    Apr 30 21:04:53	dhcpd: All rights reserved.
    Apr 30 21:04:53	dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
    Apr 30 21:05:52	mpd: mpd: caught fatal signal term
    Apr 30 21:05:54	mpd: mpd: process 2280 terminated
    Apr 30 21:05:55	mpd: mpd: pid 2959, version 3.18 (root@builder6.pfsense.com 13:56 13-Feb-2007)
    Apr 30 21:06:27	dnsmasq[2579]: exiting on receipt of SIGTERM
    Apr 30 21:06:28	dnsmasq[3065]: started, version 2.36 cachesize 150
    Apr 30 21:06:28	dnsmasq[3065]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N
    Apr 30 21:06:28	dnsmasq[3065]: reading /etc/resolv.conf
    Apr 30 21:06:28	dnsmasq[3065]: using nameserver 212.55.154.174#53
    Apr 30 21:06:28	dnsmasq[3065]: read /etc/hosts - 2 addresses
    Apr 30 21:06:29	dhcpd: Internet Systems Consortium DHCP Server V3.0.5
    Apr 30 21:06:29	dhcpd: Copyright 2004-2006 Internet Systems Consortium.
    Apr 30 21:06:29	dhcpd: All rights reserved.
    Apr 30 21:06:29	dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
    Apr 30 21:06:35	last message repeated 3 times
    Apr 30 21:07:26	mpd: MRU 1492
    Apr 30 21:07:26	mpd: MAGICNUM 7970a872
    Apr 30 21:07:26	mpd: MRU 1492
    Apr 30 21:07:26	mpd: AUTHPROTO PAP
    Apr 30 21:07:26	mpd: MAGICNUM 04c1cc69
    Apr 30 21:07:26	mpd: MRU 1492
    Apr 30 21:07:26	mpd: AUTHPROTO PAP
    Apr 30 21:07:26	mpd: MAGICNUM 04c1cc69
    Apr 30 21:07:26	mpd: MRU 1492
    Apr 30 21:07:26	mpd: MAGICNUM 7970a872
    Apr 30 21:07:27	mpd: IPADDR 0.0.0.0
    Apr 30 21:07:27	mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Apr 30 21:07:27	mpd: PRIDNS 0.0.0.0
    Apr 30 21:07:27	mpd: SECDNS 0.0.0.0
    Apr 30 21:07:27	mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Apr 30 21:07:27	mpd: SECDNS 0.0.0.0
    Apr 30 21:07:27	mpd: IPADDR 0.0.0.0
    Apr 30 21:07:27	mpd: PRIDNS 0.0.0.0
    Apr 30 21:07:27	mpd: IPADDR 85.240.171.177
    Apr 30 21:07:27	mpd: 85.240.171.177 is OK
    Apr 30 21:07:27	mpd: PRIDNS 212.55.154.174
    Apr 30 21:07:27	mpd: PRIDNS 212.55.154.174
    Apr 30 21:07:27	mpd: PRIDNS 212.55.154.174
    Apr 30 21:07:30	mpd: IPADDR 194.65.169.212
    Apr 30 21:07:30	mpd: 194.65.169.212 is OK
    Apr 30 21:07:30	mpd: IPADDR 194.65.169.212
    Apr 30 21:07:30	mpd: 85.240.171.177 -> 194.65.169.212
    Apr 30 21:07:33	check_reload_status: rc.newwanip starting
    

    194.65.169.212 it's my ISP Gateway, and 85.240.171.177 should be my IP ( dynamic ).



  • Can you try a reinstall? Or running your config.xml from floppy with the 1.2beta1 livecd? I wonder if this is an upgradeglitch.



  • @hoba:

    Or running your config.xml from floppy with the 1.2beta1 livecd?

    That's what I'm doing, livecd with floppy for 1.2 testing, and 1.0.1 installed so I can have internet. This is on the same PC



  • Can you try with the livecd and a new config? Just configuring pppoe from scratch to see if it works?



  • @hoba:

    Can you try with the livecd and a new config? Just configuring pppoe from scratch to see if it works?

    That's what I'm doing.

    When I saw that I didn't work with the old config I did a clean one. I setup wan ( pppoe ), lan address, dhcp server and host name.



  • Isn't there any solution for me? ???  :'(

    Today I tried again with the latest snapshot ( 2007-May-11 ) in live CD and with two different PC's ( and different NIC's ), and the result is the same.  :'(

    Is it my router? ( speetouch 510i v4.3.2.6 ) but with 1.0.1 is working fine.

    Thanks.



  • I now have several recent 1.2 snapshots running at PPPoE lines without issues. I really don't know what's going on with your setup. Sorry  :-\



  • From your logs, there seems to be a legit issue, and a regression here between 1.0 and 1.2. I opened a ticket.

    http://cvstrac.pfsense.com/tktview?tn=1315

    That won't guarantee it'll get fixed, or even that anything will get changed, but it's something at least…



  • Works fine for me, just upgraded for last snapshots without any trouble…



  • looks a little like a mtu issue. when the pppoe link comes up it has to recieve the mru and mtu and match them if it is not possible to set them correctly it can just loop.

    just two cents worth. funny thing nothing has changed in pppoe config in 1.2 branch could someone with this issue test this on the 1.3 branch if we could make a build of this.

    4.1 mpd is much more complient in this respect over 1.3 mpd



  • i also use some more boxes with 1.2b1 setups with pppoe without any problems…  ???



  • i have same problem, but version 1.0.1 work fine… , the problem only for ppoe connection



  • Yeah it works properly for the vast majority of people.

    @aldo: RELENG_1 snapshots (to-be 1.3) are available.

    FOR TESTING PURPOSES ONLY. Unlike the RELENG_1_2 snapshots, these are absolutely not suitable for any production use unless you're a developer. They are suitable to at least test if they have the same PPPoE issues as 1.2b1.
    http://snapshots.pfsense.org/FreeBSD6/RELENG_1/

    Could somebody that can replicate this issue try one of the above snapshots and report back?



  • We do not build RELENG_1.  People would shoot themselves in the foot and ask us to fix it.



  • Ack… yeah I didn't realize those dirs were empty.



  • hi all…

    im not a programmer, but till now i can't use any snapshot version 1.2 for ppoe



  • @pinggan:

    hi all…

    im not a programmer, but till now i can't use any snapshot version 1.2 for ppoe

    It works for many others just fine.  We have no idea what is causing the issues unfortunately.


Log in to reply