last night as discussed I shutdown pcp via gui and then issued a ping to
pcp from pc where I got Request timout as expected.
I did *not* unplug the pcp from mains...and this morning out of
curiosity I isuued another ping
Code:
--------------------
C:\Users\nikos>ping 192.168.0.10
Pinging 192.168.0.10 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.110: Destination host unreachable.
Ping statistics for 192.168.0.10:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
C:\Users\nikos>ping 192.168.0.10
Pinging 192.168.0.10 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.10:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\nikos>ping 192.168.0.10
Pinging 192.168.0.10 with 32 bytes of data:
Reply from 192.168.0.110: Destination host unreachable.
Request timed out.
Reply from 192.168.0.110: Destination host unreachable.
Request timed out.
Ping statistics for 192.168.0.10:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
C:\Users\nikos>ping 192.168.0.10
Pinging 192.168.0.10 with 32 bytes of data:
Reply from 192.168.0.110: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.10:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
--------------------
x.110 is my pc and host unreachable would be perfectly normal as long as
this was 100% consistent...without the intermittent Request timouts.
after all this ping was issued 13 hours later than the first one.
A new Advanced Ip Scanner run shows two deads:
192.168.0.10 Raspberry Pi Foundation B8:27:EB:4E:51:A2
*and*
192.168.0.231 Raspberry Pi Foundation B8:27:EB:4E:51:A2
All these days with the pcp online, an Advanced Ip Scanner run would
never show the x.231 and would only show the x.10 as
alive-and-kicking...
??????
Background info:
My first attempt at setting up pcp was interrupted since after the image
being burnt to the sd I could not get an ip address through dhcp (was to
be expected since the router at the office has a dodgy semi-working dhpc
implementation and I had not hdmi cable at hand to use console.
So when I got home that night I connected the pcp to my monitor..run
setup..issued the x.10 static address verified that wifi was off..and
the rest is history.
Could there be a x.231 address left behind "somewhere" in the pcp config
files from when the pcp tried to get a first ip during it's very first
dhcp attempt? If so where would such address be stuck?
Also upon some digging in pcp files I paste below a message which may or
may not be of use:
Code:
--------------------
tc@piCorePlayer:/var/log$ cat pcp_boot.logStarting piCorePlayer setup...
Loading pcp-functions...and pCP configuration file.sh: 3: unknown operand
Done.
--------------------
Any advice is highly appreciated.
I could always wipe the sd and burn pcp from scratch but I think it's
much better to understand what is going on before I evaporize the body.
Nikos
ps:epoch1970 kudos ;)
------------------------------------------------------------------------
_NK_'s Profile: http://forums.slimdevices.com/member.php?userid=2645
View this thread: http://forums.slimdevices.com/showthread.php?t=108198
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
