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

      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
                    • C
                      cadtiagof
                      last edited by

                      @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

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

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

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

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

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

                            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.

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

                              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  :-\

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

                                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…

                                1 Reply Last reply Reply Quote 0
                                • R
                                  rafael.cardoso
                                  last edited by

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

                                  Respect is Everything!

                                  1 Reply Last reply Reply Quote 0
                                  • A
                                    aldo
                                    last edited by

                                    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

                                    1 Reply Last reply Reply Quote 0
                                    • T
                                      trendchiller
                                      last edited by

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

                                      1 Reply Last reply Reply Quote 0
                                      • O
                                        oasisgate
                                        last edited by

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

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

                                          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?

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            sullrich
                                            last edited by

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

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