Hello Guys,
Long time no hear , I was stuck last time compiling the kernel with
additional b53 drivers . But that turned out to be a small issue with
the way the spec was consistency checking the .config files . After
getting friendly with the spec , the kernel was done . Now I have the
kernel working , and switch switching with Vlans . However I ran into
another funny one , and was hoping that some of the Fedora gurus might
point me in the right direction . I am using this box as a pppoe
terminator with a bridged adsl modem . And have installed rp-pppoe for
the pppoe part , this is because my config is too complex for the
regular approach , and I need to activate different layers of
connectivity as they become available . So I have a little script to
fire up pppoe , when the underlying connection is up . All it does is
run " pppoe-start" , which in theory should initiate the connection .
And that seems to happen but then after connecting the pppoe shuts down
shortly after . This is the syslog :
Jan 1 10:00:35 bananapi_r1 kernel: PPP generic driver version 2.4.2
Jan 1 10:00:35 bananapi_r1 kernel: NET: Registered protocol family 24
Jan 1 10:00:34 bananapi_r1 pppd[747]: Plugin
/usr/lib/pppd/2.4.7/rp-pppoe.so loaded.
Jan 1 10:00:34 bananapi_r1 pppd[747]: RP-PPPoE plugin version 3.8p
compiled against pppd 2.4.7
Jan 1 10:00:35 bananapi_r1 pppd[747]: pppd 2.4.7 started by root, uid 0
Jan 1 10:00:35 bananapi_r1 pppd[747]: PPP session is 86
Jan 1 10:00:35 bananapi_r1 pppd[747]: Connected to 00:30:48:92:23:89
via interface br0
Jan 1 10:00:35 bananapi_r1 pppd[747]: Using interface ppp0
Jan 1 10:00:35 bananapi_r1 pppd[747]: Connect: ppp0 <--> br0
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> (ppp0): new
Generic device (driver: 'unknown' ifindex: 7)
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> (ppp0): exported
as /org/freedesktop/NetworkManager/Devices/6
Jan 1 10:00:35 bananapi_r1 pppd[747]: PAP authentication succeeded
Jan 1 10:00:35 bananapi_r1 pppd[747]: peer from calling number
00:30:48:92:23:89 authorized
Jan 1 10:00:35 bananapi_r1 pppd[747]: local IP address 103.119.111.124
Jan 1 10:00:35 bananapi_r1 pppd[747]: remote IP address 10.20.21.170
Jan 1 10:00:35 bananapi_r1 pppd[747]: primary DNS address 103.12.160.35
Jan 1 10:00:35 bananapi_r1 pppd[747]: secondary DNS address 103.12.160.36
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> (ppp0): device
state change: unmanaged -> unavailable (reason 'connection-assumed') [10
20 41]
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> (ppp0): device
state change: unavailable -> disconnected (reason 'connection-assumed')
[20 30 41]
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) starting connection 'ppp0'
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) Stage 1 of 5 (Device Prepare) started...
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> (ppp0): device
state change: disconnected -> prepare (reason 'none') [30 40 0]
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) Stage 2 of 5 (Device Configure) scheduled...
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) Stage 1 of 5 (Device Prepare) complete.
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) Stage 2 of 5 (Device Configure) starting...
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> (ppp0): device
state change: prepare -> config (reason 'none') [40 50 0]
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) Stage 2 of 5 (Device Configure) successful.
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) Stage 3 of 5 (IP Configure Start) scheduled.
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) Stage 2 of 5 (Device Configure) complete.
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) Stage 3 of 5 (IP Configure Start) started...
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> (ppp0): device
state change: config -> ip-config (reason 'none') [50 70 0]
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) Stage 3 of 5 (IP Configure Start) complete.
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) Stage 5 of 5 (IPv4 Commit) started...
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> (ppp0): device
state change: ip-config -> ip-check (reason 'none') [70 80 0]
Jan 1 10:00:35 bananapi_r1 nm-dispatcher: Dispatching action 'pre-up'
for ppp0
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) Stage 5 of 5 (IPv4 Commit) complete.
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> (ppp0): device
state change: ip-check -> secondaries (reason 'none') [80 90 0]
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> (ppp0): device
state change: secondaries -> activated (reason 'none') [90 100 0]
Jan 1 10:00:35 bananapi_r1 NetworkManager[388]: <info> Activation
(ppp0) successful, device activated.
Jan 1 10:00:35 bananapi_r1 nm-dispatcher: Dispatching action 'up' for ppp0
Jan 1 10:00:39 bananapi_r1 dbus[395]: [system] Activating via systemd:
service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
Jan 1 10:00:39 bananapi_r1 dbus[395]: [system] Successfully activated
service 'org.freedesktop.ConsoleKit'
Jan 1 10:00:45 bananapi_r1 kernel: br0: port 1(eth0.101) entered
forwarding state
Jan 1 10:00:51 bananapi_r1 pppd[747]: Terminating on signal 15
Jan 1 10:00:51 bananapi_r1 pppd[747]: Connect time 0.3 minutes.
Jan 1 10:00:51 bananapi_r1 pppd[747]: Sent 3104 bytes, received 2210 bytes.
Jan 1 10:00:51 bananapi_r1 NetworkManager[388]: <info> (ppp0): device
state change: activated -> unmanaged (reason 'removed') [100 10 36]
Jan 1 10:00:51 bananapi_r1 NetworkManager[388]: <info> (ppp0):
deactivating device (reason 'removed') [36]
Jan 1 10:00:51 bananapi_r1 dbus[395]: [system] Activating via systemd:
service name='org.freedesktop.nm_dispatcher'
unit='dbus-org.freedesktop.nm-dispatcher.service'
Jan 1 10:00:51 bananapi_r1 dbus[395]: [system] Successfully activated
service 'org.freedesktop.nm_dispatcher'
Jan 1 10:00:51 bananapi_r1 nm-dispatcher: Dispatching action 'down' for
ppp0
My uneducated guess by looking at the log is that the NetworkManager is
deliberately shutting the connection down . SO question is , is it , and
what can I do to stop it from doing it .
Best Regards
Milorad
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
