Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    1-2 release - wan won't connect

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    49 Posts 15 Posters 23.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      Jonb
      last edited by

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

      Hosted desktops and servers with support without complication.
      www.blueskysystems.co.uk

      1 Reply Last reply Reply Quote 0
      • C
        cadtiagof
        last edited by

        @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.

        1 Reply Last reply Reply Quote 0
        • H
          hoba
          last edited by

          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?

          1 Reply Last reply Reply Quote 0
          • C
            cadtiagof
            last edited by

            @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

            1 Reply Last reply Reply Quote 0
            • C
              cadtiagof
              last edited by 

              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
              1 Reply Last reply Reply Quote 0
              • J
                Jonb
                last edited by

                what version did you upgrade from

                Hosted desktops and servers with support without complication.
                www.blueskysystems.co.uk

                1 Reply Last reply Reply Quote 0
                • C
                  cadtiagof
                  last edited by

                  This is from a clean install.

                  1 Reply Last reply Reply Quote 0
                  • M
                    maynarja
                    last edited by

                    I am having a similiar issue with the latest version.

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

                    1 Reply Last reply Reply Quote 0
                    • J
                      Jonb
                      last edited by

                      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.

                      Hosted desktops and servers with support without complication.
                      www.blueskysystems.co.uk

                      1 Reply Last reply Reply Quote 0
                      • M
                        maynarja
                        last edited by

                        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?

                        1 Reply Last reply Reply Quote 0
                        • C
                          cadtiagof
                          last edited by

                          @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.

                          1 Reply Last reply Reply Quote 0
                          • J
                            Jonb
                            last edited by

                            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.

                            Hosted desktops and servers with support without complication.
                            www.blueskysystems.co.uk

                            1 Reply Last reply Reply Quote 0
                            • J
                              Jonb
                              last edited by

                              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

                              Hosted desktops and servers with support without complication.
                              www.blueskysystems.co.uk

                              1 Reply Last reply Reply Quote 0
                              • C
                                cadtiagof
                                last edited by

                                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

                                1 Reply Last reply Reply Quote 0
                                • C
                                  cadtiagof
                                  last edited by

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

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    Jonb
                                    last edited by

                                    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.

                                    Hosted desktops and servers with support without complication.
                                    www.blueskysystems.co.uk

                                    1 Reply Last reply Reply Quote 0
                                    • C
                                      cadtiagof
                                      last edited by

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

                                      1 Reply Last reply Reply Quote 0
                                      • J
                                        jeroen234
                                        last edited by

                                        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

                                        1 Reply Last reply Reply Quote 0
                                        • C
                                          cadtiagof
                                          last edited by

                                          @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 ).

                                          1 Reply Last reply Reply Quote 0
                                          • H
                                            hoba
                                            last edited by

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

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.