Upgrade from 12/13 to 12/18 -> PPPoE dead…
-
Ok. I can test this, but I rely heavily on avahi for the apple bonjour stuff…
-
Bonjour works without the avahi package on your router. I have lots of macs and mac products on my networks and no avahi package on my routers.
I'm not really even sure of the purpose of a router running avahi. What are you trying to do?
GB
-
Well if you have LAN and WLAN on separate interfaces you need avahi in order for Bonjour to work…
(eg iTunes Remote / Connection from AppleTV(WLAN) to iTunes(LAN)) -
Hello…. same problem on Dec 28 pppoe dead after afew minute connected. AMD64
-
Please update to a snapshot after 28 December.
-
A fix was introduced on the 28th which means you should be running a snap from the 29th or 30th. Can someone please test this… This is one of our last issues remaining before rc1.
-
mine is still acting up have to hit connect to make it connect
-
Just updated my home router from a late November snap to:
2.0-BETA5 (i386) built on Thu Dec 30 11:06:13 EST 2010
PPPoE connected fine at boot without intervention. No problems here.
EDIT: Note that this is an always-on connection so I do not have dial-on-demand checked. I have a blank idle timeout, and periodic reset is disabled.
-
mine is still acting up have to hit connect to make it connect
dedicated or dial up? can you compare your settings with jim-p?
-
Updated to Thu Dec 30 21:38:56 EST 2010 right now. Still seeing the same behavior as before. Doesn't come up after reboot, mpd5 dies after some time, WebUI not accessable (500 - Internal Server Error) after the first connect so I need another reboot! After that I also need to click save on WAN interface again…
-
not had the web gui problem but do have to make it connect after boot my settings are the same as jims
-
Updated to Thu Dec 30 21:38:56 EST 2010 right now. Still seeing the same behavior as before. Doesn't come up after reboot, mpd5 dies after some time, WebUI not accessable (500 - Internal Server Error) after the first connect so I need another reboot! After that I also need to click save on WAN interface again…
The 500 error is due to package issues, but it could be related to this in some way I suppose.
-
What we really need to know from everyone having issues is at least:
- Architecture (i386 or amd64)
- Full install or NanoBSD
- Packages installed
- If it's WAN or an OPT on PPPoE (or both)
- PPPoE settings on the interface page (dial on demand, idle timeout, periodic reset)
- PPPoE connection logs from the system logs
- Your mpd_*.conf files from /var/etc/ - make sure to remove or mask your login credentials
-
Hi all .. this could be off topic … but I wonder has anyone ever dialed two or more PPPOE simultaneously? like practically using the interface type as PPPOE on more than 1 interface to dial to ISPs?
-
Hi there,
I don't have time to post all of the requested info now, but I think I may be experiencing this issue now too, though I don't believe it impacted me before. I updated from a Dec.26 snap to 2.0-BETA5 (i386)
built on Fri Dec 31 06:22:39 EST 2010.I have 2 PPPoE interfaces. My WAN and OPT1 (renamed VDSL and DSL respectively) are the PPPoE interfaces. WAN/VDSL works, OPT1/DSL does not.
Anyway - I've tried Dial on demand and not. I set the idle timeout to 0, with no periodic reset enabled. Doesn't seem to allow my OPT1 to connect.
Snip from GUI PPP Log page :
Dec 31 17:25:32 ppp: [opt1_link0] Link: Shutdown
Dec 31 17:25:32 ppp: [opt1] Bundle: Shutdown
Dec 31 17:25:32 ppp: [opt1_link0] LCP: LayerFinish
Dec 31 17:25:32 ppp: [opt1_link0] LCP: state change Starting –> Initial
Dec 31 17:25:32 ppp: [opt1_link0] LCP: Close event
Dec 31 17:25:30 ppp: [opt1] IPCP: Close event
Dec 31 17:25:30 ppp: [opt1] IFACE: Close event
Dec 31 17:25:30 ppp: caught fatal signal term
Dec 31 17:25:30 ppp: [opt1_link0] Link: reconnection attempt 81 in 2 seconds
Dec 31 17:25:30 ppp: [opt1_link0] LCP: Down event
Dec 31 17:25:30 ppp: [opt1_link0] Link: DOWN event
Dec 31 17:25:30 ppp: [opt1_link0] can't remove hook mpd32090-0 from node "[bc]:": No such file or directory
Dec 31 17:25:30 ppp: [opt1_link0] PPPoE: can't connect "[bc]:"->"mpd32090-0" and "[ba]:"->"left": No such file or directory
Dec 31 17:25:30 ppp: [opt1_link0] Link: reconnection attempt 80
Dec 31 17:25:26 ppp: [opt1_link0] Link: reconnection attempt 80 in 4 seconds
Dec 31 17:25:26 ppp: [opt1_link0] LCP: Down event
Dec 31 17:25:26 ppp: [opt1_link0] Link: DOWN event
Dec 31 17:25:26 ppp: [opt1_link0] can't remove hook mpd32090-0 from node "[bc]:": No such file or directory
Dec 31 17:25:26 ppp: [opt1_link0] PPPoE: can't connect "[bc]:"->"mpd32090-0" and "[ba]:"->"left": No such file or directory
Dec 31 17:25:26 ppp: [opt1_link0] Link: reconnection attempt 79
Dec 31 17:25:23 ppp: [opt1_link0] Link: reconnection attempt 79 in 3 seconds
Dec 31 17:25:23 ppp: [opt1_link0] LCP: Down event
Dec 31 17:25:23 ppp: [opt1_link0] Link: DOWN event
Dec 31 17:25:23 ppp: [opt1_link0] can't remove hook mpd32090-0 from node "[bc]:": No such file or directory
Dec 31 17:25:23 ppp: [opt1_link0] PPPoE: can't connect "[bc]:"->"mpd32090-0" and "[ba]:"->"left": No such file or directoryHope this is helpful,
– Phob
-
Sorry, it's going to be a few days before I'm back in town to try an update.
-
Hi again,
Just checked my packages screen - I only have the Open-VM-Tools installed at present.
– Phob
-
Hrm - I disabled my OPT1 interface for a while to stop the constant PPPoE requests, and just re-enabled it to discover that it has negotiated another session.
Might be a carrier issue as I see some packet loss today in my graphs.
Anyway - if the issue resurfaces, I'll post again.
– Phob
-
Hi again,
OK - further to my last, with dial on demand un-ticked, I have to manually start my PPPoE sessions from Status –> Interfaces on reboot.
Also, entering the down interface from Interfaces --> DSL or VDSL then clicking save also seems to get my PPPoE back online, but when I do that, I have to manually go into System --> Routing and delete the automatically created gateways which overwrite my working gateway setup. (the system creates GW_WAN and GW_OPT1 when I've already got gateways defined with different names (VDSL and DSL) that are in turn members of gateway groups for load balancing and failover)
Sorry to muddy the waters - I re-read this entire thread which I admit not to have done the first time I posted. I appear to have the same issue as others.
-- Phob
-
What we really need to know from everyone having issues is at least:
- Architecture (i386 or amd64)
- Full install or NanoBSD
- Packages installed
- If it's WAN or an OPT on PPPoE (or both)
- PPPoE settings on the interface page (dial on demand, idle timeout, periodic reset)
- PPPoE connection logs from the system logs
- Your mpd_*.conf files from /var/etc/ - make sure to remove or mask your login credentials
- i386
- NanoBSD
- Avahi, Backup, RRD Summary, Nmap, Unbound, Shellcmd
- WAN (PPPoE)
- Standard Settings, except periodic reset at midnight each day
- For configs/logfiles see my previous posts