1-2 release - wan won't connect
-
Can you try a reinstall? Or running your config.xml from floppy with the 1.2beta1 livecd? I wonder if this is an upgradeglitch.
-
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?
-
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
-
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.
-
well, yes !
Works really nice, and now dyndns works well again, so perhaps try a fresh install… ??? -
I have posted links to the mpd logs I recovered for what seems to be the same problem:
http://forum.pfsense.org/index.php/topic,5151.0.html
The last snapshot I have that works with my PPPoE connection is 1.0.1-SNAPSHOT-03-15-2007.
-
Hi,
Is there any update on this issue? I am having the same problem with 1.2 RC2.
Tried update from 1.0.1, fresh 1.2 RC2 install, none worked.
Best Regards,
Tiago Baptista -
Hi,
Today I also tried Monowall 1.3b4 and had the same problem.
Tiago Baptista