Reboot Router forcing Pogoplug(Alarm) to require reboot

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

Reboot Router forcing Pogoplug(Alarm) to require reboot

Postby snakepit28 » Tue Jun 16, 2015 9:40 pm

Whenver I have to reboot my router, i find that i have to reboot the pogo as well or else i lose connectivity to the pogo.

Furthermore, the router has to be fully booted in order to successfully boot the pogo with connectivity to network.

Why is that?

Anyway to fix that?
snakepit28
 
Posts: 6
Joined: Sun Jan 05, 2014 12:54 am

Re: Reboot Router forcing Pogoplug(Alarm) to require reboot

Postby WarheadsSE » Tue Jun 16, 2015 9:57 pm

Your router directs traffic on the network, as well as handing out addresses (DHCP).

In some consumer home routers will not send traffic to devices that have an address in their DHCP range that they don't have a record of handing out. In this case, a reboot is removing the record of the address it handed to the Pogoplug. The reboot of the pogoplug the causes a fresh DHCP request, getting the address added to the router's memory, resulting in it being willing to send traffic to it.

Does that all make sense?
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Reboot Router forcing Pogoplug(Alarm) to require reboot

Postby snakepit28 » Tue Jun 16, 2015 10:33 pm

Thanks for that explanation.


One is dd wrt and the other is consumer dsl router. Both with the same result.

I see the challenge now.

How is the pogoplug supposed to know the router restarted? That would probably require very constant cron job to ping the router.

Is there a command that can delay the lan0 from connecting upon booting? say delay it by about 90 seconds, so the router can fully boot?
snakepit28
 
Posts: 6
Joined: Sun Jan 05, 2014 12:54 am

Re: Reboot Router forcing Pogoplug(Alarm) to require reboot

Postby nhamnhi » Thu Jul 30, 2015 1:49 pm

I have a same problem too. And I am using static IP. I also have a WDTV Live Duo nas (and other WS) and it reconnected to the network just fine once the router finished rebooting.

Is there a command or script or something that can be used to get the pogoplug to reconnect automatically without rebooting?

TIA
nhamnhi
 
Posts: 10
Joined: Thu Jul 30, 2015 1:45 pm

Re: Reboot Router forcing Pogoplug(Alarm) to require reboot

Postby pepedog » Thu Jul 30, 2015 8:33 pm

pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Reboot Router forcing Pogoplug(Alarm) to require reboot

Postby nhamnhi » Tue Aug 04, 2015 3:03 am

Thanks for the direction.

SO I copied the ethernet-static file and placed it in /etc/netctl, changed the network info to match with eth0's info.


[root@pogoplug netctl]# more ethernet-static
Description='A basic static ethernet connection'
Interface=eth0
Connection=ethernet
IP=static
Address=('192.168.1.10/24')
#Routes=('192.168.0.0/24 via 192.168.1.2')
Gateway='192.168.1.1'
DNS=('192.168.1.1')

## For IPv6 autoconfiguration
#IP6=stateless

## For IPv6 static address configuration
#IP6=static
#Address6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
#Routes6=('abcd::1234')
#Gateway6='1234:0:123::abcd'
[root@pogoplug netctl]#


When I tried to start the profile, it errored out...


[root@pogoplug netctl]# netctl start ethernet-static
Job for netctl@ethernet\x2dstatic.service failed. See 'systemctl status netctl@ethernet\x2dstatic.service' and 'journalctl -xn' for details.
[root@pogoplug netctl]#journalctl -xn
.
.
.
Aug 03 22:52:57 pogoplug network[1226]: Starting network profile 'ethernet-static'...
Aug 03 22:52:57 pogoplug network[1226]: The interface of network profile 'ethernet-static' is already up
Aug 03 22:52:57 pogoplug systemd[1]: netctl@ethernet\x2dstatic.service: main process exited, code=exited, status=1/FAIL
Aug 03 22:52:57 pogoplug systemd[1]: Failed to start Networking for netctl profile ethernet-static.
-- Subject: Unit netctl@ethernet\x2dstatic.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
-- Documentation: http://www.freedesktop.org/wiki/Softwar ... e9d022f03d
--
-- Unit netctl@ethernet\x2dstatic.service has failed.
--
-- The result is failed.

[root@pogoplug netctl]# netctl status ethernet-static
netctl@ethernet\x2dstatic.service - Networking for netctl profile ethernet-static
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
Active: failed (Result: exit-code) since Mon 2015-08-03 22:53:41 EDT; 48s ago
Docs: man:netctl.profile(5)
Process: 1244 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
Main PID: 1244 (code=exited, status=1/FAILURE)

Aug 03 22:53:41 pogoplug network[1244]: Starting network profile 'ethernet-static'...
Aug 03 22:53:41 pogoplug network[1244]: The interface of network profile 'ethernet-static' is already up
Aug 03 22:53:41 pogoplug systemd[1]: netctl@ethernet\x2dstatic.service: main process exited, code=exited, stat...AILURE
Aug 03 22:53:41 pogoplug systemd[1]: Failed to start Networking for netctl profile ethernet-static.
Aug 03 22:53:41 pogoplug systemd[1]: Unit netctl@ethernet\x2dstatic.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
[root@pogoplug netctl]#


I also created the ifplugd@eth0.service file /usr/lib/systemd/system, started and enabled ifplugd. That seems to work no problem.

[root@pogoplug system]# ps -ef |grep ifplug
root 151 1 0 Jul30 ? 00:00:23 /usr/bin/ifplugd -i eth0 -r /etc/ifplugd/netctl.action -bfIns
root 1341 1201 0 22:59 pts/0 00:00:00 grep ifplug
[root@pogoplug system]#


But it seems like the netctl is not working somehow. Sorry I've been trying, but not getting anywhere. Do I have to get both netctl profile to start and ifplugd to start before it can work?

Any other ideas?

Thanks
nhamnhi
 
Posts: 10
Joined: Thu Jul 30, 2015 1:45 pm

Re: Reboot Router forcing Pogoplug(Alarm) to require reboot

Postby WarheadsSE » Tue Aug 04, 2015 2:51 pm

There should be an netctl-ifplugd@.service
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Reboot Router forcing Pogoplug(Alarm) to require reboot

Postby nhamnhi » Tue Aug 04, 2015 3:13 pm

I will check when I get home later today. But it actually says

Aug 03 22:53:41 pogoplug network[1244]: The interface of network profile 'ethernet-static' is already up

Does it mean it's already started? But it has to be started in order for me to log in though right?

I know its dumb, but I actually tried to stop it and indeed lost connection. Had to hard reboot :~).

Back to your statement. Does that file need to be renamed to netctl-ifplugd@eth0.service or just leave it like it is?
nhamnhi
 
Posts: 10
Joined: Thu Jul 30, 2015 1:45 pm

Re: Reboot Router forcing Pogoplug(Alarm) to require reboot

Postby WarheadsSE » Tue Aug 04, 2015 3:40 pm

$this->bbcode_second_pass_code('', '
systemctl enable netctl-ifplug@eth0.service
netctl stop-all && systemctl start netctl-ifplugd@eth0.service ;
')
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Reboot Router forcing Pogoplug(Alarm) to require reboot

Postby nhamnhi » Tue Aug 04, 2015 3:45 pm

Thanks. Will try this and update later.
nhamnhi
 
Posts: 10
Joined: Thu Jul 30, 2015 1:45 pm

Next

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 42 guests