1 |
On Tue, 2012-02-07 at 11:33 -0600, William Hubbs wrote: |
2 |
> On Tue, Feb 07, 2012 at 04:46:58PM +0000, Duncan wrote: |
3 |
> > 1) Separate net.lo service for stuff that doesn't have to have an |
4 |
> > external connection at all. |
5 |
> |
6 |
> This can be easily done. I'll just make net.lo* not provide net. |
7 |
> |
8 |
> > 2) A default net (or net*) service that is is composed of all non-net.lo |
9 |
> > services, with a default any-one-of-them policy. |
10 |
> > Two reasons for this: |
11 |
> > |
12 |
> > 2a) It'll "just work" in the simple case. |
13 |
> > |
14 |
> > 2b) It's the easiest to automatically preconfigure without getting into |
15 |
> > lots of "detect all the networks and magically figure out whether they're |
16 |
> > lan-only or inet" hairballs. |
17 |
> |
18 |
> As soon as you add a second interface, this default "net" service |
19 |
> breaks. That is why I think we should add an "internet" service that |
20 |
> consists of interfaces the user says provide a connection to the |
21 |
> internet. Then we could make our services that need real |
22 |
> internet connections need that service instead of net. |
23 |
|
24 |
As I discussed in #gentoo-dev, it breaks if some of your interfaces are |
25 |
lan-only. That might be not uncommon in the server room, but for the |
26 |
typical gentoo user with a desktop or laptop, all interfaces are |
27 |
generally expected to allow internet connections, and if more than one |
28 |
is up (e.g. both eth0 and wlan0), the kernel will do the intelligent |
29 |
thing and choose the best one to route through. |
30 |
|
31 |
-Alexandre. |