1 |
Hi, |
2 |
|
3 |
finally I got set up pppoe, which turned out to be surprisingly easy. |
4 |
It's working fine, though I'm getting a warning when the pppoe interface |
5 |
is brought up: |
6 |
|
7 |
|
8 |
heimdali init.d # service net.ppp0 start |
9 |
* Bringing up interface ppp0 |
10 |
* Starting pppd in ppp0 ... [ ok ] |
11 |
* Backgrounding ... |
12 |
* WARNING: net.ppp0 has started, but is inactive |
13 |
heimdali init.d # |
14 |
|
15 |
|
16 |
Why is this warning showing, and what can I do about it? |
17 |
|
18 |
|
19 |
How does pppoe work together with shorewall and bind? |
20 |
|
21 |
When I stop the net.ppp0 service, shorewall is automatically stopped as |
22 |
well. When I start net.ppp0, shorewall is not started automatically. |
23 |
|
24 |
I would like to automatically have net.ppp0 first started and then |
25 |
shorewall. |
26 |
|
27 |
|
28 |
When net.ppp0 is stopped and restarted, I also must restart the name |
29 |
server (bind) :( Otherwise it is unable to resolve anything. |
30 |
|
31 |
Can this somehow be avoided? If not, can this be done automatically? |
32 |
|
33 |
|
34 |
The log files show martian sources from a bridge device which is used |
35 |
for the networking of a container: |
36 |
|
37 |
|
38 |
[1734776.722127] IPv4: martian source 255.255.255.255 from 192.168.1.1, on dev enp2s0 |
39 |
[1734776.722132] ll header: 00000000: ff ff ff ff ff ff 00 0b 6b 81 c9 44 08 00 ........k..D.. |
40 |
|
41 |
|
42 |
The enp2s0 interface is used for pppoe, 192.168.1.1 is the IP of the |
43 |
bridge. The bridge does not have a physical network interface assigned |
44 |
to it. |
45 |
|
46 |
The routefilter option is enabled on all interfaces. Why would there be |
47 |
such a broadcast originating from the bridge, and how can I prevent it? |
48 |
|
49 |
|
50 |
-- |
51 |
Again we must be afraid of speaking of daemons for fear that daemons |
52 |
might swallow us. Finally, this fear has become reasonable. |