mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2025-12-24 23:00:07 +01:00
1361ede099
a40949267 build: add CI run without ebpf
044db2056 n-acd: drop redundant headers
6a391cd83 n-acd: fix build without eBPF
bb194cf09 n-acd/config: make transport mandatory
ec2865743 build: drop unused c-sundry
721d9d84f n-acd: inline c_container_of()
1a7ee317c util/timer: fix coding-style
6c96f926b util/timer: fall back to CLOCK_MONOTONIC if necessary
4ea3165fc n-acd: only use CLOCK_BOOTTIME if really necessary
c1b853c6c util/timer: cleanup headers
b1d6ad272 n-acd: add destructors that return void
185be55b6 test-bpf: skip test in case of unsufficient privs
84a40e8fa build: add NEWS file
bf11443ff build: mention mailinglist in readme
e2797984a test-bpf: drop bpf-filter.h
668ed3c82 subprojects: pull in updates
dd8cab3f0 test-veth: reduce parallel execution to 9
68b09ba2b build: update AUTHORS
3f77e3e88 test: make function headers valid C
5275a5120 test: get rid of spurious tab
037df412c n-acd: make struct initializers valid C
346ec0c67 build: upgrade CI
38682a36d n-acd: fix signed vs unsigned comparison
5e7578b33 bpf: properly zero out trailing bpf_attr space
ee1e432ae probe: fix coding-style
a143540f9 build: use lower-case build options
835533e7d build: minor style fixes
2bd6d1d29 build: get rid of tabs
b14979934 eBPF: make compile-time optional
6f13c27ee n-acd: filter out invalid packets
4e6a169a0 build: sync with c-util repositories
6c4a9117b build: document eBPF kernel requirement
3ef08394d n-acd: don't remember dropped defense attempts
4dff8771f n-acd: fix coding-style
b11fb9706 n-acd/config: default to the RFC-specified timeout
d885bb3b7 n-acd/event: don't expose the type of operation that caused a conflict
e2f87e047 TODO: drop remaining items
f06993856 test/veth: reduce the number of probed addresses
8b4f7ed64 test/veth: bump the timeout a bit
14e4606f6 n-acd/probe: don't cap the jitter at 4s
a0247b86f test/veth: fix stackvariable corruption
a64ac8389 n-acd/probe: update comments
aa9c25bc1 n-acd/handle_timeout: update comments
b6c2df3a9 timer: rename timer_pop() to timer_pop_timeout()
47c657a8d test: fix handling of child addresses
27168ba9e timer: move timer_read() from n-acd.c to util/timer.c
21a1e37aa timer: require timer to be explicitly rearmed
ee1080820 bpf/map: make key/value sizes self-documenting
fd444353e test/veth: rework test
ba2bc433c test: rework child_ip() helper
07881b8da test: silence a warning
38da00b0a test/bpf: make tests for map modifications more comprehensive
6a2ffd23a test/timerfd: for documentation purposes verify the kernel API
01a9cf54b probe: move from ms to ns internally
4fe438dd9 n-acd: move to use the Timer utility library
e098cfc79 util: add a timer utility helper
8ea196e5b subprojects: pull in c-sundry
0c0b3c29f acd/probe: do not subscribe to packets in FAILED state
9c922ea3d acd/probe: introduce probe_{un,}link() helpers
024a830e6 acd/probe: use unschedule() helper in free()
b098a3bcc tests/veth: minor fixes to the test
fe3d9578a acd/packet: consider unexpected packets a fatal error
34d7656d7 acd: stop state-machine after USED or CONFLICT events
7d9e5ec6b acd: don't declare iovec entries inline
7afd8d8a3 tests: add veth test
26a737b42 tests/veth: add helper for adding IP addresses to child device
e73a37a11 probe: store a userdata pointer in the probe object
327e82625 test: introduce loopback helper
0682b15f8 acd: reduce default map size
afead881f tests: reinstate loopback test
4527d2f71 BPF: move and document the eBPF helpers
88bacc022 socket filter: move to the new eBPF helpers
245104d5c tests: skip tests if lacking permissions
195d9ff5a n-acd: rework API to support many probes on a context
ab440eb99 eBPF: never return packets that userspace should unconditionally drop
ac933f412 eBPF: add eBPF helper functions
git-subtree-dir: shared/n-acd
git-subtree-split: a40949267923c45cb232fa4c1d60eafacee4b36e
85 lines
4.3 KiB
Text
85 lines
4.3 KiB
Text
|
|
******************
|
|
2008-12-11: NetworkManager core daemon has moved to git.freedesktop.org!
|
|
|
|
git clone git://git.freedesktop.org/git/NetworkManager/NetworkManager.git
|
|
******************
|
|
|
|
|
|
Networking that Just Works
|
|
--------------------------
|
|
|
|
NetworkManager attempts to keep an active network connection available at all
|
|
times. The point of NetworkManager is to make networking configuration and
|
|
setup as painless and automatic as possible. NetworkManager is intended to
|
|
replace default route, replace other routes, set IP addresses, and in general
|
|
configure networking as NM sees fit (with the possibility of manual override as
|
|
necessary). In effect, the goal of NetworkManager is to make networking Just
|
|
Work with a minimum of user hassle, but still allow customization and a high
|
|
level of manual network control. If you have special needs, we'd like to hear
|
|
about them, but understand that NetworkManager is not intended for every
|
|
use-case.
|
|
|
|
NetworkManager will attempt to keep every network device in the system up and
|
|
active, as long as the device is available for use (has a cable plugged in,
|
|
the killswitch isn't turned on, etc). Network connections can be set to
|
|
'autoconnect', meaning that NetworkManager will make that connection active
|
|
whenever it and the hardware is available.
|
|
|
|
"Settings services" store lists of user- or administrator-defined "connections",
|
|
which contain all the settings and parameters required to connect to a specific
|
|
network. NetworkManager will _never_ activate a connection that is not in this
|
|
list, or that the user has not directed NetworkManager to connect to.
|
|
|
|
|
|
How it works:
|
|
|
|
The NetworkManager daemon runs as a privileged service (since it must access
|
|
and control hardware), but provides a D-Bus interface on the system bus to
|
|
allow for fine-grained control of networking. NetworkManager does not store
|
|
connections or settings, it is only the mechanism by which those connections
|
|
are selected and activated.
|
|
|
|
To store pre-defined network connections, two separate services, the "system
|
|
settings service" and the "user settings service" store connection information
|
|
and provide these to NetworkManager, also via D-Bus. Each settings service
|
|
can determine how and where it persistently stores the connection information;
|
|
for example, the GNOME applet stores its configuration in GConf, and the system
|
|
settings service stores its config in distro-specific formats, or in a distro-
|
|
agnostic format, depending on user/administrator preference.
|
|
|
|
A variety of other system services are used by NetworkManager to provide
|
|
network functionality: wpa_supplicant for wireless connections and 802.1x
|
|
wired connections, pppd for PPP and mobile broadband connections, DHCP clients
|
|
for dynamic IP addressing, dnsmasq for proxy nameserver and DHCP server
|
|
functionality for internet connection sharing, and avahi-autoipd for IPv4
|
|
link-local addresses. Most communication with these daemons occurs, again,
|
|
via D-Bus.
|
|
|
|
|
|
Why doesn't my network Just Work?
|
|
|
|
Driver problems are the #1 cause of why NetworkManager sometimes fails to
|
|
connect to wireless networks. Often, the driver simply doesn't behave in a
|
|
consistent manner, or is just plain buggy. NetworkManager supports _only_
|
|
those drivers that are shipped with the upstream Linux kernel, because only
|
|
those drivers can be easily fixed and debugged. ndiswrapper, vendor binary
|
|
drivers, or other out-of-tree drivers may or may not work well with
|
|
NetworkManager, precisely because they have not been vetted and improved by the
|
|
open-source community, and because problems in these drivers usually cannot
|
|
be fixed.
|
|
|
|
Sometimes, command-line tools like 'iwconfig' will work, but NetworkManager will
|
|
fail. This is again often due to buggy drivers, because these drivers simply
|
|
aren't expecting the dynamic requests that NetworkManager and wpa_supplicant
|
|
make. Driver bugs should be filed in the bug tracker of the distribution being
|
|
run, since often distributions customize their kernel and drivers.
|
|
|
|
Sometimes, it really is NetworkManager's fault. If you think that's the case,
|
|
please file a bug at http://bugzilla.gnome.org and choose the NetworkManager
|
|
component. Attaching the output of /var/log/messages or /var/log/daemon.log
|
|
(wherever your distribution directs syslog's 'daemon' facility output) is often
|
|
very helpful, and (if you can get) a working wpa_supplicant config file helps
|
|
enormously.
|
|
|
|
|