X-FeedAbuse: http://nntpfeed.proxad.net/abuse.pl feeded by 78.192.65.63 Path: csiph.com!usenet.pasdenom.info!nntpfeed.proxad.net!news.muarf.org!news.roellig-ltd.de!open-news-network.org!border2.nntp.ams1.giganews.com!nntp.giganews.com!buffer2.nntp.ams1.giganews.com!local2.nntp.ams1.giganews.com!nntp.brightview.co.uk!news.brightview.co.uk.POSTED!not-for-mail NNTP-Posting-Date: Thu, 06 Aug 2015 15:52:13 -0500 Subject: Re: Logs Newsgroups: comp.sys.raspberry-pi From: T M Smith X-Editor: EmailEdit 6.00 Date: Thu, 06 Aug 2015 21:51:54 +0100 Message-ID: References: <5df3fded54.Broadband@tmsmith36.plus.com> <98j89c-md6.ln1@myleafnode.oneyv.org> <74a49bee54.Broadband@tmsmith36.plus.com> User-Agent: Messenger-Pro/6.06 (MsgServe/6.04S) (RISC-OS/5.21) NewsHound/v1.52-32 Lines: 79 X-Usenet-Provider: http://www.giganews.com X-Trace: sv3-UI3lcc4LlAuZ9CvQIUjUuA4ws5AXrgFe3eIII7wvcsyzVE5kLpZR4p2rrG4q3N+LZ3uO8WYgzbwZFz7!plTD/d0B4UWC55yu+8XjqVkiuKXBAJ6qrHXQQUisHdTTHbqdrQae9EPdeIomsPtHoRlnuougZkwa!NYWdBq8vdK0= X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 4006 Xref: csiph.com comp.sys.raspberry-pi:9361 In message alister wrote: > On Wed, 05 Aug 2015 23:58:24 +0100, T M Smith wrote: >> In message <98j89c-md6.ln1@myleafnode.oneyv.org> >> JimR wrote: >> >>> On 08/04/2015 06:33 PM, T M Smith wrote: >>>> In message >>>> The Natural Philosopher wrote: >> >>>> One puzzle is that the date shown in the log was 15th May. >>>> This is a backup SD card I have just put in the Pi and I am now >>>> wondering the date must be wrong. I had expected it would have >>>> corrected date and time. >> >>> The RPi has no real-time clock on board. When you power it down, it >>> loses the correct time settings. Early in the boot-up sequence, it >>> connects to an NTP server and adjusts the time. If you inspect the >>> syslog right after a power-up, you will see the timestamp suddenly >>> jump. >> >> >>>> However the WiFi works OK with WiFi config displaying normally. >>>> Another puzzle is that it gave the Pi as 192.168.1.95 Changing this to >>>> a static address of 192.168.1.90 has not worked, it still comes up as >>>> 192.168.1.95 >>>> >>>> Here is interfaces file >>>> >>>> auto lo >>>> >>>> iface lo inet loopback iface eth0 inet static >>>> >>>> address 192.168.1.90 netmask 255.255.255.0 gateway 192.168.1.254 >>>> >>>> allow-hotplug wlan0 iface wlan0 inet manual wpa-roam >>>> /etc/wpa_supplicant/wpa_supplicant.conf iface default inet dhcp >>>> >>>> >>> My RPi runs as a headless server, and has a static IP address assigned. >>> I never had much luck with adjusting /etc/network/interfaces, in >>> fact, >>> the only thing in mine right now is >> >>> auto lo iface lo inet loopback >> >> >>> However, I *did* use wicd-curses when I first set up my rpi. In there, >>> under Config, you will find an option to set a static IP address. That >>> worked for me. You might find that wicd-curses is not installed by >>> default. If not, simply sudo apt-get install wicd-curses >> >>> Best of luck JimR >> What puzzles me is that while 192.168.1.90 is stored in the file above I >> can find no race of 192.168.1.95 which is actually used >> >> Malcolm > I think this line may be your problem > " > /etc/wpa_supplicant/wpa_supplicant.conf iface default inet dhcp > " > the dhcp option is causing the interface to reset its ip address to one > supplied by your DHCP server I have just tried your sugestion in as much as I commented out the line you suspected (actually 2 lines in the program).The result was that no ip address was allocated, not even 192.168.1.95. WiFi Config showed 'Could not get status from wpa_supplicant'. -- T M Smith Using an ARMX6 and RISC OS 5.21 in the North Riding of Yorkshire