Michael Tremer [Sun, 17 Jan 2016 18:37:10 +0000 (19:37 +0100)]
lock: Decrease the number of iterations per second
There have been reports about that this locking mechanism
wasn't too stable on their machines which can totally be
the case judging by the design of it.
However there is no other easy way to implement this any
better without any native C helper which I would like to
avoid at this moment.
So I decreased the amount of ticks which should make
any processes running at the same time less likely to
collide.
Fixes #10979
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Michael Tremer [Sat, 16 Jan 2016 16:09:47 +0000 (17:09 +0100)]
Implement identify feature
When executing "network [zone|port|device] XXX identify" the
port, device or all ports of the zone (that support this feature)
will flash for ten seconds.
Ports will also flash when they are attached to or detached from
a zone.
This is supposed to make plugging in a cable into the right
device is easier.
Fixes #10969
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Michael Tremer [Wed, 21 Oct 2015 16:42:06 +0000 (18:42 +0200)]
inetcalc: Allow build on 64 bit architectures
inetcalc previously used a GCC extension that was only
available on 64 bit platforms. This patch changes the
code to use struct in6_addr instead of __uint128_t for
storing IP addresses.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Stefan Schantl [Sun, 18 Oct 2015 17:36:57 +0000 (19:36 +0200)]
functions.ipv6: Fix doubble square bracket when calling assert
The assert check does not proper work when using doubble square backets,
so the check fails for some unknown reasons. Removing one bracket will allow
to successfully perform the assert check again.
Signed-off-by: Stefan Schantl <stefan.schantl@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Stefan Schantl [Sat, 5 Sep 2015 19:44:07 +0000 (21:44 +0200)]
dns: Better propagate known DNS servers
dns_servers_update() is a new function that must be called
when ever there are changes to the DNS server configuration.
This may be by the user or by learning new DNS servers from
a dial-up connection, etc.
Signed-off-by: Stefan Schantl <stefan.schantl@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Michael Tremer [Thu, 13 Aug 2015 09:02:58 +0000 (11:02 +0200)]
Introduce triggers
When the state of the network changes (i.e. a zone comes up, etc.)
a set of triggers will be called so that external applications can
adopt to these changes.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Michael Tremer [Sat, 2 May 2015 21:26:00 +0000 (21:26 +0000)]
dhclient: Properly handle IPv6
Router advertisements are now properly processed if there
is dhclient running on an interface and all information
from the DHCP client is removed when dhclient is stopped.
Michael Tremer [Wed, 31 Dec 2014 14:49:57 +0000 (14:49 +0000)]
Remove pptp
After a rather longer discussion we decided that there are
not many providers any more that use PPTP. The only ones that
we know of are legacy DSL lines in Austria. Most of the newer
DSL providers in Austria use PPPoE now.
Some "privacy" VPN providers allow using PPTP which is just
ridiculous. We do not want to support that.
PPTP is also very rarely used for IPv6 transition, but only
a few providers use that. They always support a different
technology.
Michael Tremer [Sat, 27 Dec 2014 13:32:07 +0000 (13:32 +0000)]
Fix hook settings writing and checking
Formerly the check functions were not correctly called in
some cases. Hence passing the check function is now explicitely
required. The {port,zone}_settings_{read,write} functions do
this transparent to the zone/port hooks.
Michael Tremer [Tue, 23 Dec 2014 00:29:15 +0000 (00:29 +0000)]
Split port hooks in to (create|remove|up|down) actions
The port hooks formerly had two functions that brought the device
up or down. That caused some problems with hotplugging of the zones.
Now the entire process has been split into four functions that
every port hooks has to implement.
create:
Creates the device but does not bring it up yet. This will
usually trigger a hotplug event so that various other port
or zone hooks can attach the device or do similar actions.
up:
Essentially brings up the device, just like:
ip link set devX up
The action should propagate to any slave devices.
down:
Does essentially the opposite of "up" and should propagate
to the slaves as well.
remove:
Removes any virtual devices and cleans up. This will also
trigger a hotplug event so that all connected hooks will
be notified about the removal.
Michael Tremer [Sat, 6 Dec 2014 19:18:37 +0000 (20:18 +0100)]
Remove support for ISDN
ISDN has never been deployed very much
in the world except Germany and some
other countries. Most of them went away
from ISDN to VoIP for telephony and
DSL or fibre for data connections.
The bandwidth is very small with only
64k per channel and this has only been
implemented for backup purposes if the
primary connection cut off. Nowadays
there is mobile connections with much
more bandwidth available for this.
Nobody is able (due to lack of ISDN)
and willing to support this any more.
Hence the entire support for ISDN
is removed.