[RESOLVED] New batch of pogoplug P22 E02 not working

[fgina]

looks like static ip using netctl profile method is not reliablly working. sometimes (20%) the device get the configured static ip, on some boots (80%) the device gets ip from dhcp server.

[pepedog]

You probably got 2 services running, look in /etc/systemd/system/ and its sub directories

[caldersm]

both eth0 and my Profile are running....at least it looks that way. I had an old compusa router, and so I got a new one this weekend from a sale on newegg.....and it doesnt do it on the new router. The old one was from 2006 and you couldnt even see the hostnames. The new one allowed me to set a reservation by MAC for a specific IP address....and that along with learning how to set the MAC in Arch has eliminated the issue completely.

btw....the USB drive throughput is AMAZING.....I am hitting 29MB/s on large file moves....this is SWEET...!! I also added another Tb drive that was configured as NTFS....and I did the "Obi" performance tips, and it is getting the same speeds...!! Just finished backing up all the computers in the house...and couldnt be happier...!!

Thanks so much....to all of you Devs.....even that one slightly impatient one....!! LoL..!! I am learning so much about Linux...and SOOO much more to go...

Steve

[fgina]

this is really a hair losing task. why is it that the pogoplug's default OS is able to reliability getting IPs but Arch running on the same hardware and same network switch/router/dhcp server is getting choked left and right? I fully understand the differences of commercial software vs. open source, and part of the fun is researching and learning. but, it seems so basic for dhcp server and client to work, and I see just so many people getting stumbled on this problem.

[fgina]

here's my further testings. hope arch devs can pick out why.

- booting pogo's stock OS, the device always reliably requests and grabs an ip from any dhcp servers I've tried. look at screenshot. the 100.100.100.101 ip was assigned to pogo while booting stock os. the mac address is correct.
- using arch from usb, the device got another ip 100.100.100.102. the mac address has a long string in front of its MAC. I dont' know what is it. maybe some router's built-in dhcp server are not able to parse this and gets confused therefore not able to complete the hand shakes? but why is arch's dhcp request sending out clearly incorrect mac string?

[grayman4hire]

Did you see BrianD's recent post?

viewtopic.php?f=53&t=5977&start=30#p33984

[fgina]

well, nice to find some progress to sort things out. maybe this is some info that should be documented or put in sub note.

next question. can we disable ipv6 and have old routers from 2000s to work? who needs ipv6 at home?

[moonman]

The fix is in the post linked to by greymen4hire

[fgina]

that seemed to solve ipv6 problems.

also got usb wifi stick configured. a linksys wusb54gc v3. good news, it works out of the box. no drivers or firmwares needed

[pepedog]

I am concerned.
Rpi image never had duid and did have ipv6.disable=1 in kernel command line, but there are still rare failures with ifplugd