From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [Development] Recent networking changes
Date: Sun, 24 Jun 2012 01:20:06 +0200 [thread overview]
Message-ID: <1340493606.20688.15.camel@hughes.tremer.info> (raw)
In-Reply-To: <1340199364.20568.26.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 2237 bytes --]
Good evening,
it is time for another smaller status update about the patches that have
been added to the networking code in the last two weeks.
There has been a bunch of fixes for bugs that have mainly been
discovered by Stefan. Thanks for that.
One bigger step has been a proper output of the status of the zones. The
console has often been cluttered with too much information and we needed
to fix that. You will now see the same output a bit shortened and with
some colours marking the most important this (zone is down or something
like that).
There has also been done some work for creating this output a bit faster
which translates to: Not so many forks in the shell code and sourcing
the hooks in a subshell without including the whole function library
again.
The pppoe hook has been reworked. That means duplicate code has been
consolidated and documentation has been added. The service name and
access concentrator options which are present in IPFire 2 have been
added. PLEASE test this. I have done everything I could, but have no
access to an IPv6 enabled DSL line. I don't expect this to work right
now.
Information on how to use the pppoe hook is available:
man 8 network-zone-pppoe
As mentioned earlier, I had no possibility to test the pppoe hook and
therefore I built the pppoe-server config hook. This just listens on a
zone for PPPoE packets and creates an instance of pppd for each
connection. I have no idea if this is a feature that will be requested
by many users, but it is quite handy for development purposes.
Please give it some testing as well:
man 8 network-zone-config-pppoe-server
Finally, there has been a command added to configure the local pool of
DNS servers. You may add a DNS server by running "network dns add
8.8.8.8 20" where 8.8.8.8 is the IP address of the DNS server and 20 is
the priority. A list of all configured DNS servers can be viewed by
issuing "network dns list". Detailed information is available at the
usual location:
man 8 network-dns
That's all for now. Thank you for reading and testing in advance.
Michael
On Wed, 2012-06-20 at 15:36 +0200, Michael Tremer wrote:
> Thank you very much. The changes you sent me have been merged to the
> master tree.
>
> Michael
next prev parent reply other threads:[~2012-06-23 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 12:15 Michael Tremer
2012-06-17 20:09 ` Stefan Schantl
2012-06-20 13:36 ` Michael Tremer
2012-06-23 23:20 ` Michael Tremer [this message]
2012-06-26 17:40 ` Stefan Schantl
2012-07-01 20:41 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1340493606.20688.15.camel@hughes.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox