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.
-
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?
-
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.
What does status>interfaces tell about the WAN connection?
It has the connect button.
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?
-
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.