Buggy behavior of xl2tpd-control and the daemon

[tespent]

I'm writing a library that controls the daemon, so I refer to x2ltpd-control.c and xl2tpd.c for the protocol. And I have noticed several bugs in both the daemon and the client. Here are some of them:

1. xl2tpd-control available does not output anything as expected unless specify -d to dump information, which is caused by a buggy implementation of xl2tpd-control.
2. The daemon does not respond to CONTROL_PIPE_REQ_LAC_STATUS request. since the handler is almost empty and does not return any unimplemented notification.

I may update the list later if I discover more bugs related to the control protocol or its implementation.

BTW, I've recently found that the mailing list returns 404. I'm wondering what happens to the mailing list.