Upgrade from 12/13 to 12/18 -> PPPoE dead…

jlepthien

/var/etc/mpd_wan.conf:

startup:
	# configure the console
	set console close
	# configure the web server
	set web close

default:
pppoeclient:
	create bundle static wan
	set iface name pppoe0
	set iface route default
	set iface disable on-demand
	set iface idle 0
	set iface enable tcpmssfix
	set iface up-script /usr/local/sbin/ppp-linkup
	set iface down-script /usr/local/sbin/ppp-linkdown
	set ipcp ranges 0.0.0.0/0 0.0.0.0/0
	#log -bund -ccp -chat -iface -ipcp -lcp -link

	create link static wan_link0 pppoe
	set link action bundle wan
	set link disable multilink
	set link keep-alive 10 60
	set link max-redial 0
	set link disable chap pap
	set link accept chap pap eap
	set link disable incoming
	set link mtu 1492
	set auth authname "xxxx@t-online.de"
	set auth password xxxx
	set pppoe iface vr1
	open

ps uxawww | grep mpd5:

root   31262  0.0  1.6  7440  3940  ??  SNs   2:22PM   0:00.02 /usr/local/sbin/mpd5 -b -k -d /var/etc -f mpd_wan.conf -p /var/run/pppoe_wan.pid -s ppp pppoeclient

Also check out the screenshot attached. If I open up mpd_wan.conf with vi there is some sort of control character at the end of the file…

![Bildschirmfoto 2010-12-28 um 14.24.10.png](/public/imported_attachments/1/Bildschirmfoto 2010-12-28 um 14.24.10.png)

jimp

So those are the files from the same time you are getting the errors in the logs?

Dec 27 21:37:35    ppp: [wan_link0] can't remove hook mpd8816-0 from node "[11]:": No such file or directory
Dec 27 21:37:35    ppp: [wan_link0] PPPoE: can't connect "[11]:"->"mpd8816-0" and "[f]:"->"left": No such file or directory

That ^M is just a windows carriage return, usually programs are smart enough to ignore those. I've got one on my home router running a working snap from late November, so it's probably not the cause here.

jlepthien

I think so. I took this as soon as I could ssh into the box. But these errors go away and for some time you have the other stuff I posted above going on until it finally connects…

eri--

I just committed a patch which hopefully will resolve this.
Please test with a new snapshot because you need a new mpd binary.

jimp

FYI- I just rebuilt it on the builder after Ermal's patch, and restarted the build, so the next new snapshot that uploads should include the fix.

jlepthien

It got even worse over here…
After a reboot the ppp.log showed this:

Dec 29 16:34:25 voldemort ppp: [wan_link0] can't remove hook mpd10506-0 from node "[12]:": No such file or directory
Dec 29 16:34:25 voldemort ppp: [wan_link0] Link: DOWN event
Dec 29 16:34:25 voldemort ppp: [wan_link0] LCP: Down event
Dec 29 16:34:25 voldemort ppp: [wan_link0] Link: reconnection attempt 2 in 1 seconds
Dec 29 16:34:26 voldemort ppp: [wan_link0] Link: reconnection attempt 2
Dec 29 16:34:26 voldemort ppp: [wan_link0] PPPoE: can't connect "[12]:"->"mpd10506-0" and "[f]:"->"left": No such file or directory
Dec 29 16:34:26 voldemort ppp: [wan_link0] can't remove hook mpd10506-0 from node "[12]:": No such file or directory
Dec 29 16:34:26 voldemort ppp: [wan_link0] Link: DOWN event
Dec 29 16:34:26 voldemort ppp: [wan_link0] LCP: Down event
Dec 29 16:34:26 voldemort ppp: [wan_link0] Link: reconnection attempt 3 in 2 seconds
Dec 29 16:34:28 voldemort ppp: [wan_link0] Link: reconnection attempt 3
Dec 29 16:34:28 voldemort ppp: [wan_link0] PPPoE: can't connect "[12]:"->"mpd10506-0" and "[f]:"->"left": No such file or directory
Dec 29 16:34:28 voldemort ppp: [wan_link0] can't remove hook mpd10506-0 from node "[12]:": No such file or directory
Dec 29 16:34:28 voldemort ppp: [wan_link0] Link: DOWN event
Dec 29 16:34:28 voldemort ppp: [wan_link0] LCP: Down event
Dec 29 16:34:28 voldemort ppp: [wan_link0] Link: reconnection attempt 4 in 2 seconds
Dec 29 16:34:30 voldemort ppp: [wan_link0] Link: reconnection attempt 4
Dec 29 16:34:30 voldemort ppp: [wan_link0] PPPoE: can't connect "[12]:"->"mpd10506-0" and "[f]:"->"left": No such file or directory
Dec 29 16:34:30 voldemort ppp: [wan_link0] can't remove hook mpd10506-0 from node "[12]:": No such file or directory
Dec 29 16:34:30 voldemort ppp: [wan_link0] Link: DOWN event
Dec 29 16:34:30 voldemort ppp: [wan_link0] LCP: Down event
Dec 29 16:34:30 voldemort ppp: [wan_link0] Link: reconnection attempt 5 in 4 seconds
Dec 29 16:34:34 voldemort ppp: [wan_link0] Link: reconnection attempt 5
Dec 29 16:34:34 voldemort ppp: [wan_link0] PPPoE: can't connect "[12]:"->"mpd10506-0" and "[f]:"->"left": No such file or directory
Dec 29 16:34:34 voldemort ppp: [wan_link0] can't remove hook mpd10506-0 from node "[12]:": No such file or directory
Dec 29 16:34:34 voldemort ppp: [wan_link0] Link: DOWN event
Dec 29 16:34:34 voldemort ppp: [wan_link0] LCP: Down event
Dec 29 16:34:34 voldemort ppp: [wan_link0] Link: reconnection attempt 6 in 4 seconds
Dec 29 16:34:38 voldemort ppp: [wan_link0] Link: reconnection attempt 6
Dec 29 16:34:38 voldemort ppp: [wan_link0] PPPoE: can't connect "[12]:"->"mpd10506-0" and "[f]:"->"left": No such file or directory
Dec 29 16:34:38 voldemort ppp: [wan_link0] can't remove hook mpd10506-0 from node "[12]:": No such file or directory
Dec 29 16:34:38 voldemort ppp: [wan_link0] Link: DOWN event
Dec 29 16:34:38 voldemort ppp: [wan_link0] LCP: Down event
Dec 29 16:34:38 voldemort ppp: [wan_link0] Link: reconnection attempt 7 in 1 seconds
Dec 29 16:34:39 voldemort ppp: [wan_link0] Link: reconnection attempt 7
Dec 29 16:34:39 voldemort ppp: [wan_link0] PPPoE: can't connect "[12]:"->"mpd10506-0" and "[f]:"->"left": No such file or directory
Dec 29 16:34:39 voldemort ppp: [wan_link0] can't remove hook mpd10506-0 from node "[12]:": No such file or directory
Dec 29 16:34:39 voldemort ppp: [wan_link0] Link: DOWN event
Dec 29 16:34:39 voldemort ppp: [wan_link0] LCP: Down event
Dec 29 16:34:39 voldemort ppp: [wan_link0] Link: reconnection attempt 8 in 3 seconds
Dec 29 16:34:41 voldemort ppp: caught fatal signal term
Dec 29 16:34:41 voldemort ppp: [wan] IFACE: Close event
Dec 29 16:34:41 voldemort ppp: [wan] IPCP: Close event
Dec 29 16:34:42 voldemort ppp: [wan_link0] LCP: Close event
Dec 29 16:34:42 voldemort ppp: [wan_link0] LCP: state change Starting --> Initial
Dec 29 16:34:42 voldemort ppp: [wan_link0] LCP: LayerFinish
Dec 29 16:34:43 voldemort ppp: [wan] Bundle: Shutdown
Dec 29 16:34:43 voldemort ppp: [wan_link0] Link: Shutdown
Dec 29 16:34:43 voldemort ppp: process 10506 terminated
Dec 29 16:34:46 voldemort ppp: Multi-link PPP daemon for FreeBSD
Dec 29 16:34:46 voldemort ppp:  
Dec 29 16:34:46 voldemort ppp: process 25103 started, version 5.5 (root@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org 16:48 28-Dec-2010)
Dec 29 16:34:46 voldemort ppp: web: web is not running
Dec 29 16:34:46 voldemort ppp: [wan] Bundle: Interface ng0 created
Dec 29 16:34:46 voldemort ppp: [wan_link0] Link: OPEN event
Dec 29 16:34:46 voldemort ppp: [wan_link0] LCP: Open event
Dec 29 16:34:46 voldemort ppp: [wan_link0] LCP: state change Initial --> Starting
Dec 29 16:34:46 voldemort ppp: [wan_link0] LCP: LayerStart
Dec 29 16:34:46 voldemort ppp: [wan_link0] PPPoE: Connecting to '*'
Dec 29 16:34:46 voldemort ppp: PPPoE: rec'd ACNAME "KIER71-se800-B2234310702478"
Dec 29 16:34:55 voldemort ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Dec 29 16:34:55 voldemort ppp: [wan_link0] Link: DOWN event
Dec 29 16:34:55 voldemort ppp: [wan_link0] LCP: Down event
Dec 29 16:34:55 voldemort ppp: [wan_link0] Link: reconnection attempt 1 in 1 seconds
Dec 29 16:34:56 voldemort ppp: [wan_link0] Link: reconnection attempt 1
Dec 29 16:34:56 voldemort ppp: [wan_link0] PPPoE: Connecting to '*'
Dec 29 16:34:57 voldemort ppp: PPPoE: rec'd ACNAME "KIER71-se800-B2234310702478"
Dec 29 16:35:06 voldemort ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Dec 29 16:35:06 voldemort ppp: [wan_link0] Link: DOWN event
Dec 29 16:35:06 voldemort ppp: [wan_link0] LCP: Down event
Dec 29 16:35:06 voldemort ppp: [wan_link0] Link: reconnection attempt 2 in 1 seconds
Dec 29 16:35:07 voldemort ppp: [wan_link0] Link: reconnection attempt 2
Dec 29 16:35:07 voldemort ppp: [wan_link0] PPPoE: Connecting to '*'
Dec 29 16:35:07 voldemort ppp: PPPoE: rec'd ACNAME "KIER71-se800-B2234310702478"
Dec 29 16:35:16 voldemort ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Dec 29 16:35:16 voldemort ppp: [wan_link0] Link: DOWN event
Dec 29 16:35:16 voldemort ppp: [wan_link0] LCP: Down event
Dec 29 16:35:16 voldemort ppp: [wan_link0] Link: reconnection attempt 3 in 3 seconds
Dec 29 16:35:19 voldemort ppp: [wan_link0] Link: reconnection attempt 3
Dec 29 16:35:19 voldemort ppp: [wan_link0] PPPoE: Connecting to '*'
Dec 29 16:35:19 voldemort ppp: PPPoE: rec'd ACNAME "KIER71-se800-B2234310702478"

Then suddenly it stopped and I checked if mpd5 was running which was not. Also the WebGUI wasn't accessable…

system.log showed the following:

Dec 29 16:37:35 voldemort kernel: pid 14143 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 14463 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 14739 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 14314 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 14793 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 15107 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 15387 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 15807 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 16146 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 16160 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 15704 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 16285 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 16331 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 16761 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 16748 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 17055 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 17089 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 17394 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 16638 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 16853 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 17664 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 18136 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 17773 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 18389 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 18687 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 18083 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 18495 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 18919 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 18798 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 19008 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 19298 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 19625 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 19589 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 19925 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 20132 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 20418 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 20714 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 20804 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 20829 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 21317 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 21104 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 21314 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 21511 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 21839 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 22209 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 22150 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 22368 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 22644 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 22831 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 22645 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 23037 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 23171 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 23461 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 24007 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 23702 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 24061 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 24346 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 24312 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 24044 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 24669 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 24820 (php), uid 0: exited on signal 11
Dec 29 16:37:35 voldemort kernel: pid 24933 (php), uid 0: exited on signal 11

So I had to do a 'killall php' and restart the Web Configurator. After that I could click save on the WAN interface so that mpd5 would start again. This time the ppp logs started again and it took some more minutes before the connection came up. Still not everything was right (see screenshot attached) - the IP on WAN was missing and I could not access website although the connection seemed to be up…

After another reboot and waiting some minutes for the connection to come up everything looked fine. But the packages (at the moment only avahi installed) did not get reinstalled automatically, again... After manually reinstalling avahi that was the log:

Dec 29 16:41:22 voldemort avahi-daemon[38866]: Found user 'avahi' (UID 558) and group 'avahi' (GID 558).
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Successfully dropped root privileges.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: avahi-daemon 0.6.24 starting up.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Dec 29 16:41:22 voldemort avahi-daemon[38866]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Loading service file /usr/local/etc/avahi/services/sftp-ssh.service.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Loading service file /usr/local/etc/avahi/services/ssh.service.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Joining mDNS multicast group on interface ng1.IPv4 with address xxxx.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: New relevant interface ng1.IPv4 for mDNS.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Joining mDNS multicast group on interface ath0_wlan1.IPv4 with address 192.168.100.254.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: New relevant interface ath0_wlan1.IPv4 for mDNS.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Joining mDNS multicast group on interface ath0_wlan0.IPv4 with address 172.16.100.254.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: New relevant interface ath0_wlan0.IPv4 for mDNS.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Joining mDNS multicast group on interface vr0.IPv4 with address 10.0.100.254.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: New relevant interface vr0.IPv4 for mDNS.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Network interface enumeration completed.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Registering new address record for fe80::20d:b9ff:fe13:54a8 on ng1.*.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Registering new address record for xxxx on ng1.IPv4.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Registering new address record for fe80::480:48ff:fe62:fa57 on ath0_wlan1.*.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Registering new address record for 192.168.100.254 on ath0_wlan1.IPv4.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Registering new address record for fe80::280:48ff:fe62:fa57 on ath0_wlan0.*.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Registering new address record for 172.16.100.254 on ath0_wlan0.IPv4.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Registering new address record for fe80::20d:b9ff:fe13:54a8 on vr0.*.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Registering new address record for 10.0.100.254 on vr0.IPv4.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Registering HINFO record with values 'I386'/'FREEBSD'.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Short read() on signal pipe.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: Short read() on signal pipe.
Dec 29 16:41:22 voldemort avahi-daemon[38866]: daemon_signal_next() failed
Dec 29 16:41:22 voldemort avahi-daemon[38866]: daemon_signal_next() failed
Dec 29 16:41:22 voldemort check_reload_status: reloading filter
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: iface.c: avahi_server_add_service() failed: Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: Server startup complete. Host name is voldemort.hogwarts.lan. Local service cookie is 3244555418.
Dec 29 16:41:23 voldemort avahi-daemon[38866]: Failed to add service 'voldemort' of type '_ssh._tcp', ignoring service group (/usr/local/etc/avahi/services/ssh.service): Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: Failed to add service 'voldemort' of type '_ssh._tcp', ignoring service group (/usr/local/etc/avahi/services/ssh.service): Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: Failed to add service 'SFTP File Transfer on voldemort' of type '_sftp-ssh._tcp', ignoring service group (/usr/local/etc/avahi/services/sftp-ssh.service): Not supported
Dec 29 16:41:23 voldemort avahi-daemon[38866]: Failed to add service 'SFTP File Transfer on voldemort' of type '_sftp-ssh._tcp', ignoring service group (/usr/local/etc/avahi/services/sftp-ssh.service): Not supported

So still some error messages. What are these. Are they 'normal'?

![Bildschirmfoto 2010-12-29 um 16.42.48.png](/public/imported_attachments/1/Bildschirmfoto 2010-12-29 um 16.42.48.png)
![Bildschirmfoto 2010-12-29 um 16.42.48.png_thumb](/public/imported_attachments/1/Bildschirmfoto 2010-12-29 um 16.42.48.png_thumb)

eri--

I think your problems come from avahi package because it does some very bad things to base system.
Please uninstall avahi and if you can upgrade to a latest snap.

jlepthien

Ok. I can test this, but I rely heavily on avahi for the apple bonjour stuff…

gnhb

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

jlepthien

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

wachaq

Hello…. same problem on Dec 28 pppoe dead after afew minute connected. AMD64

eri--

Please update to a snapshot after 28 December.

sullrich

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.

grandrivers

mine is still acting up have to hit connect to make it connect

jimp

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.

sullrich

@grandrivers:

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?

jlepthien

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…

grandrivers

not had the web gui problem but do have to make it connect after boot my settings are the same as jims

jimp

@jlepthien:

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.

jimp

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