summaryrefslogtreecommitdiff
path: root/doc/ipconfig-api.txt
blob: 080fdac568eaf930d92d6351bb35187e5143e57a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
IP configuration handling
*************************


IP basics
=========

The core IP handling is designed around network interfaces or more precisely
what the Linux kernel handles as struct net_device. Via RTNL every interface
is tracked and an IP device created for it.

	+--------+           +---- eth0 -----+
	|        |           |               |
	|  RTNL  +-----+---->|   IP device   |
	|        |     |     |               |
	+--------+     |     +---------------+
                       |
                       |     +---- wlan0 ----+
	               |     |               |
	               +---->|   IP device   |
	                     |               |
	                     +---------------+

The IP device tracks link configuration, IP address setting and routing
information for that interface. Every IP device also contains a configuration
element. That element contains an operation table for callbacks based on
different events.

	struct connman_ipconfig_ops {
		void (*up)         (struct connman_ipconfig *);
		void (*down)       (struct connman_ipconfig *);
		void (*lower_up)   (struct connman_ipconfig *);
		void (*lower_down) (struct connman_ipconfig *);
		void (*ip_bound)   (struct connman_ipconfig *);
		void (*ip_release) (struct connman_ipconfig *);
	};

All configuration objects created directly by RTNL are tightly bound to the
IP device. They will trigger DHCP or other configuration helpers.