Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.raspberry-pi > #9310 > unrolled thread

Logs

Back to article view | Back to comp.sys.raspberry-pi

Contents

  Logs T M Smith <tmsmith36@tmsmith36.plus.com> - 2015-08-04 19:15 +0100
    Re: Logs The Natural Philosopher <tnp@invalid.invalid> - 2015-08-04 19:49 +0100
      Re: Logs T M Smith <tmsmith36@tmsmith36.plus.com> - 2015-08-04 23:33 +0100
        Re: Logs JimR <NotReally@yahoo.com> - 2015-08-05 01:23 -0400
          Re: Logs T M Smith <tmsmith36@tmsmith36.plus.com> - 2015-08-05 23:58 +0100
            Re: Logs alister <alister.nospam.ware@ntlworld.com> - 2015-08-06 19:36 +0000
              Re: Logs T M Smith <tmsmith36@tmsmith36.plus.com> - 2015-08-06 21:51 +0100
                Re: Logs The Natural Philosopher <tnp@invalid.invalid> - 2015-08-06 22:07 +0100
                  Re: Logs T M Smith <tmsmith36@tmsmith36.plus.com> - 2015-08-06 23:24 +0100
                    Re: Logs The Natural Philosopher <tnp@invalid.invalid> - 2015-08-06 23:40 +0100
                      Re: Logs Stefan Enzinger <mindoms@aon.at> - 2015-08-07 10:23 +0200
                        Re: Logs Gordon Henderson <gordon+usenet@drogon.net> - 2015-08-07 13:51 +0000
                          Re: Logs Rob <nomail@example.com> - 2015-08-07 14:45 +0000
            Re: Logs Dom <domafp@blueyonder.co.uk> - 2015-08-07 06:51 +0100
              Re: Logs T M Smith <tmsmith36@tmsmith36.plus.com> - 2015-08-07 21:10 +0100
                Re: Logs T M Smith <tmsmith36@tmsmith36.plus.com> - 2015-08-07 22:14 +0100
                  Re: Logs Rob Morley <nospam@ntlworld.com> - 2015-08-08 17:26 +0100
                    Re: Logs T M Smith <tmsmith36@tmsmith36.plus.com> - 2015-08-08 21:23 +0100
                      Re: Logs The Natural Philosopher <tnp@invalid.invalid> - 2015-08-09 07:16 +0100
                Re: Logs Dom <domafp@blueyonder.co.uk> - 2015-08-08 06:21 +0100
                  Re: Logs Rob <nomail@example.com> - 2015-08-08 08:06 +0000
                    Re: Logs Dom <domafp@blueyonder.co.uk> - 2015-08-08 09:25 +0100
                      Re: Logs Rob <nomail@example.com> - 2015-08-08 08:37 +0000
                  Re: Logs T M Smith <tmsmith36@tmsmith36.plus.com> - 2015-08-08 21:08 +0100
        Re: Logs "A. Dumas" <alexandre@dumas.fr.invalid> - 2015-08-09 08:36 +0200
          Re: Logs The Natural Philosopher <tnp@invalid.invalid> - 2015-08-09 16:02 +0100
            Re: Logs Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-08-09 13:19 -0400
          Re: Logs T M Smith <tmsmith36@tmsmith36.plus.com> - 2015-08-09 20:45 +0100
            Re: Logs "A. Dumas" <alexandre@dumas.fr.invalid> - 2015-08-17 17:44 +0200
    Re: Logs Rob Morley <nospam@ntlworld.com> - 2015-08-04 20:34 +0100
    Re: Logs druck <news@druck.org.uk> - 2015-08-04 20:38 +0100
    Re: Logs mjb@signal11.invalid (Mike) - 2015-08-04 20:41 +0100
      Re: Logs Martin Gregorie <martin@address-in-sig.invalid> - 2015-08-05 08:16 +0000
      Re: Logs Gordon Henderson <gordon+usenet@drogon.net> - 2015-08-05 09:15 +0000

Page 1 of 2  [1] 2  Next page →

#9310 — Logs

Using Rasbian on a Pi is there a log kept of the data that scolls past 
as the system boots?

Malcolm Smith

-- 
T M Smith
Using an ARMX6 and RISC OS 5.21 in the North Riding of Yorkshire

[toc] | [next] | [standalone]

#9312

On 04/08/15 19:15, T M Smith wrote:
> Using Rasbian on a Pi is there a log kept of the data that scolls past
> as the system boots?
>
> Malcolm Smith
>

I think so.

Try the command dmesg and have a look in /var/log/syslog IIRC




-- 
New Socialism consists essentially in being seen to have your heart in 
the right place whilst your head is in the clouds and your hand is in 
someone else's pocket.

[toc] | [prev] | [next] | [standalone]

#9326

In message <mpr1g1$bqm$1@news.albasani.net>
          The Natural Philosopher <tnp@invalid.invalid> wrote:

> On 04/08/15 19:15, T M Smith wrote:
>> Using Rasbian on a Pi is there a log kept of the data that scolls past
>> as the system boots?
>>
>> Malcolm Smith
>>

> I think so.

> Try the command dmesg and have a look in /var/log/syslog IIRC
Thank you gentlemen.
Did not help me though, lost in a sea of words now.
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.
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

I did not think the last 4 lines should be there but cut them stops 
things working.

Malcolm




-- 
T M Smith
Using an ARMX6 and RISC OS 5.21 in the North Riding of Yorkshire

[toc] | [prev] | [next] | [standalone]

#9330

On 08/04/2015 06:33 PM, T M Smith wrote:
> In message <mpr1g1$bqm$1@news.albasani.net>
>            The Natural Philosopher <tnp@invalid.invalid> 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

[toc] | [prev] | [next] | [standalone]

#9358

In message <98j89c-md6.ln1@myleafnode.oneyv.org>
          JimR <NotReally@yahoo.com> wrote:

> On 08/04/2015 06:33 PM, T M Smith wrote:
>> In message <mpr1g1$bqm$1@news.albasani.net>
>>            The Natural Philosopher <tnp@invalid.invalid> 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



-- 
T M Smith
Using an ARMX6 and RISC OS 5.21 in the North Riding of Yorkshire

[toc] | [prev] | [next] | [standalone]

#9359

On Wed, 05 Aug 2015 23:58:24 +0100, T M Smith wrote:

> In message <98j89c-md6.ln1@myleafnode.oneyv.org>
>           JimR <NotReally@yahoo.com> wrote:
> 
>> On 08/04/2015 06:33 PM, T M Smith wrote:
>>> In message <mpr1g1$bqm$1@news.albasani.net>
>>>            The Natural Philosopher <tnp@invalid.invalid> 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




-- 
"...and the fully armed nuclear warheads, are, of course, merely a
courtesy detail."

[toc] | [prev] | [next] | [standalone]

#9361

In message <mq0cvl$8tm$1@speranza.aioe.org>
          alister <alister.nospam.ware@ntlworld.com> wrote:

> On Wed, 05 Aug 2015 23:58:24 +0100, T M Smith wrote:

>> In message <98j89c-md6.ln1@myleafnode.oneyv.org>
>>           JimR <NotReally@yahoo.com> wrote:
>> 
>>> On 08/04/2015 06:33 PM, T M Smith wrote:
>>>> In message <mpr1g1$bqm$1@news.albasani.net>
>>>>            The Natural Philosopher <tnp@invalid.invalid> 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

[toc] | [prev] | [next] | [standalone]

#9362

On 06/08/15 21:51, T M Smith wrote:
> In message <mq0cvl$8tm$1@speranza.aioe.org>
>            alister <alister.nospam.ware@ntlworld.com> wrote:
>
>> On Wed, 05 Aug 2015 23:58:24 +0100, T M Smith wrote:
>
>>> In message <98j89c-md6.ln1@myleafnode.oneyv.org>
>>>            JimR <NotReally@yahoo.com> wrote:
>>>
>>>> On 08/04/2015 06:33 PM, T M Smith wrote:
>>>>> In message <mpr1g1$bqm$1@news.albasani.net>
>>>>>             The Natural Philosopher <tnp@invalid.invalid> 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'.
>
>

You dont want to comment it out, but to replace inet dhcp with
inet static address 192.168.1.90 netmask 255.255.255.0 gateway 192.168.1.254
>
etc.


But this may work better for you

https://www.raspberrypi.org/forums/viewtopic.php?f=26&t=31003

get rid of wpa_supplicant line and add this

auto wlan0
iface wlan0 inet static
         address 192.168.0.21
         netmask 255.255.255.0
         gateway 192.168.0.1
         wpa-essid whatever
         wpa-psk bigseceretpassword

That should hard connect you to that SSID with that password.


-- 
New Socialism consists essentially in being seen to have your heart in 
the right place whilst your head is in the clouds and your hand is in 
someone else's pocket.

[toc] | [prev] | [next] | [standalone]

#9363

In message <mq0i9t$od6$1@news.albasani.net>
          The Natural Philosopher <tnp@invalid.invalid> wrote:

> On 06/08/15 21:51, T M Smith wrote:
>> In message <mq0cvl$8tm$1@speranza.aioe.org>
>>            alister <alister.nospam.ware@ntlworld.com> wrote:
>>
>>> On Wed, 05 Aug 2015 23:58:24 +0100, T M Smith wrote:
>>
>>>> In message <98j89c-md6.ln1@myleafnode.oneyv.org>
>>>>            JimR <NotReally@yahoo.com> wrote:
>>>>
>>>>> On 08/04/2015 06:33 PM, T M Smith wrote:
>>>>>> In message <mpr1g1$bqm$1@news.albasani.net>
>>>>>>             The Natural Philosopher <tnp@invalid.invalid> 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.
>>>>
>>>>> [snip]

>>>>>> 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'.
>>
>>

> You dont want to comment it out, but to replace inet dhcp with
> inet static address 192.168.1.90 netmask 255.255.255.0 gateway 192.168.1.254
>>
> etc.


> But this may work better for you

> https://www.raspberrypi.org/forums/viewtopic.php?f=26&t=31003

> get rid of wpa_supplicant line and add this

> auto wlan0
> iface wlan0 inet static
>          address 192.168.0.21
>          netmask 255.255.255.0
>          gateway 192.168.0.1
>          wpa-essid whatever
>          wpa-psk bigseceretpassword

> That should hard connect you to that SSID with that password.

Changed to the file give in your above reference has taken things back 
to nnormal the static address has still become 192.168.1.95 and not 
the 192.168.1.90 that is entered in the file.
Somewhere it is getting that address! which I gave it some weeks ago 
and using it in preference to the one I wish it to use.
Incidentally the last two lines of the above file were entered via 
WiFi Config and reside in the wpa_supplicant.conf file.

Is there anyway I could search the system for 192.168.1.95?

Malcolm





-- 
T M Smith
Using an ARMX6 and RISC OS 5.21 in the North Riding of Yorkshire

[toc] | [prev] | [next] | [standalone]

#9364

On 06/08/15 23:24, T M Smith wrote:
> In message <mq0i9t$od6$1@news.albasani.net>
>            The Natural Philosopher <tnp@invalid.invalid> wrote:
>
>> On 06/08/15 21:51, T M Smith wrote:
>>> In message <mq0cvl$8tm$1@speranza.aioe.org>
>>>             alister <alister.nospam.ware@ntlworld.com> wrote:
>>>
>>>> On Wed, 05 Aug 2015 23:58:24 +0100, T M Smith wrote:
>>>
>>>>> In message <98j89c-md6.ln1@myleafnode.oneyv.org>
>>>>>             JimR <NotReally@yahoo.com> wrote:
>>>>>
>>>>>> On 08/04/2015 06:33 PM, T M Smith wrote:
>>>>>>> In message <mpr1g1$bqm$1@news.albasani.net>
>>>>>>>              The Natural Philosopher <tnp@invalid.invalid> 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.
>>>>>
>>>>>> [snip]
>
>>>>>>> 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'.
>>>
>>>
>
>> You dont want to comment it out, but to replace inet dhcp with
>> inet static address 192.168.1.90 netmask 255.255.255.0 gateway 192.168.1.254
>>>
>> etc.
>
>
>> But this may work better for you
>
>> https://www.raspberrypi.org/forums/viewtopic.php?f=26&t=31003
>
>> get rid of wpa_supplicant line and add this
>
>> auto wlan0
>> iface wlan0 inet static
>>           address 192.168.0.21
>>           netmask 255.255.255.0
>>           gateway 192.168.0.1
>>           wpa-essid whatever
>>           wpa-psk bigseceretpassword
>
>> That should hard connect you to that SSID with that password.
>
> Changed to the file give in your above reference has taken things back
> to nnormal the static address has still become 192.168.1.95 and not
> the 192.168.1.90 that is entered in the file.
> Somewhere it is getting that address! which I gave it some weeks ago
> and using it in preference to the one I wish it to use.
> Incidentally the last two lines of the above file were entered via
> WiFi Config and reside in the wpa_supplicant.conf file.
>
> Is there anyway I could search the system for 192.168.1.95?
>

find / -exec grep '192.168.1.95' {} \;


> Malcolm
>
>
>
>
>


-- 
New Socialism consists essentially in being seen to have your heart in 
the right place whilst your head is in the clouds and your hand is in 
someone else's pocket.

[toc] | [prev] | [next] | [standalone]

#9368

On 2015-08-07 00:40, The Natural Philosopher wrote:

>> Is there anyway I could search the system for 192.168.1.95?
>>
> 
> find / -exec grep '192.168.1.95' {} \;

grep can search recursively:
grep -r '192\.168\.1\.95' /

I've also escaped the dot which would act as a wildcard and probably
slow down thinks a bit.

[toc] | [prev] | [next] | [standalone]

#9369

In article <d2j87nF522lU1@mid.individual.net>,
Stefan Enzinger  <mindoms@aon.at> wrote:
>On 2015-08-07 00:40, The Natural Philosopher wrote:
>
>>> Is there anyway I could search the system for 192.168.1.95?
>>>
>> 
>> find / -exec grep '192.168.1.95' {} \;
>
>grep can search recursively:
>grep -r '192\.168\.1\.95' /
>
>I've also escaped the dot which would act as a wildcard and probably
>slow down thinks a bit.

From the more than one way to do it department - use fgrep - no global expressions,
more correctly in these enlightened days is grep -F though.

It will still take time though.

Gordon

[toc] | [prev] | [next] | [standalone]

#9370

Gordon Henderson <gordon+usenet@drogon.net> wrote:
> In article <d2j87nF522lU1@mid.individual.net>,
> Stefan Enzinger  <mindoms@aon.at> wrote:
>>On 2015-08-07 00:40, The Natural Philosopher wrote:
>>
>>>> Is there anyway I could search the system for 192.168.1.95?
>>>>
>>> 
>>> find / -exec grep '192.168.1.95' {} \;
>>
>>grep can search recursively:
>>grep -r '192\.168\.1\.95' /
>>
>>I've also escaped the dot which would act as a wildcard and probably
>>slow down thinks a bit.
>
> From the more than one way to do it department - use fgrep - no global expressions,
> more correctly in these enlightened days is grep -F though.
>
> It will still take time though.

Of course in the general case of looking for an IP address in all
files in the directory you need to specify that it only should look
on word boundaries, so the correct expression is:

	'\<192\.168\.1\.95\>'

This cannot be done with fgrep.

In the case of this particular address it won't mis-hit, but when
you look for 192\.168\.1\.1 it will not only match 192.168.1.1 but
also 192.168.1.10 or 192.168.1.100 for example.

Aside from that, it is unwise to grep -r from the root directory,
because sooner or later it will hit some special file and either get
stuck or cause havoc to some service (e.g. when it is reading a FIFO
or RS232 port).

When you really want to search from / (and not only /etc which would
probably suffice in this case), it is better to use:

find / -type f -print0 | xargs -0 grep '\<192\.168\.1\.95\>'

[toc] | [prev] | [next] | [standalone]

#9366

On 05/08/15 23:58, T M Smith wrote:
> In message <98j89c-md6.ln1@myleafnode.oneyv.org>
>            JimR <NotReally@yahoo.com> wrote:
>
>> On 08/04/2015 06:33 PM, T M Smith wrote:
>>> In message <mpr1g1$bqm$1@news.albasani.net>
>>>             The Natural Philosopher <tnp@invalid.invalid> 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

There's nothing wrong with your /etc/network/interfaces file as it stands.

It should work fine - but for some reason the default dhcp client is now 
dhcpcd5 which totally ignores the interfaces file and does it's own 
thing. So what you are getting is the static address that you assigned 
and a DHCP address that dhcpcd5 has picked up and allocated.

Remove dhcpcd5 and things should work the way they are supposed to.

If you want DCHP for another interface, just install dhcpcd (no "5") 
instead and things will work properly.

[toc] | [prev] | [next] | [standalone]

#9373

In message <kHXwx.242436$ad5.18579@fx06.am4>
          Dom <domafp@blueyonder.co.uk> wrote:

> On 05/08/15 23:58, T M Smith wrote:
>> In message <98j89c-md6.ln1@myleafnode.oneyv.org>
>>            JimR <NotReally@yahoo.com> wrote:
>>
>>> On 08/04/2015 06:33 PM, T M Smith wrote:
>>>> In message <mpr1g1$bqm$1@news.albasani.net>
>>>>             The Natural Philosopher <tnp@invalid.invalid> 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

> There's nothing wrong with your /etc/network/interfaces file as it stands.

> It should work fine - but for some reason the default dhcp client is now
> dhcpcd5 which totally ignores the interfaces file and does it's own
> thing. So what you are getting is the static address that you assigned
> and a DHCP address that dhcpcd5 has picked up and allocated.

> Remove dhcpcd5 and things should work the way they are supposed to.

> If you want DCHP for another interface, just install dhcpcd (no "5")
> instead and things will work properly.
Dom, You have lost me here.
Where is, and what is dhcpcd5.
At one stage during my attempts to get things right it gave me a 
primary address of 192.168.1.90 and a secondary address of 
192.168.1.95,
My search for the 95 address is still running.

Malcolm


-- 
T M Smith
Using an ARMX6 and RISC OS 5.21 in the North Riding of Yorkshire

[toc] | [prev] | [next] | [standalone]

#9374

In message <70e693ef54.Broadband@tmsmith36.plus.com>
          T M Smith <tmsmith36@tmsmith36.plus.com> wrote:

> In message <kHXwx.242436$ad5.18579@fx06.am4>
>           Dom <domafp@blueyonder.co.uk> wrote:

>> On 05/08/15 23:58, T M Smith wrote:
>>> In message <98j89c-md6.ln1@myleafnode.oneyv.org>
>>>            JimR <NotReally@yahoo.com> wrote:

[snip]

>>>
>>>
>>>>> 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

>> There's nothing wrong with your /etc/network/interfaces file as it stands.

>> It should work fine - but for some reason the default dhcp client is now
>> dhcpcd5 which totally ignores the interfaces file and does it's own
>> thing. So what you are getting is the static address that you assigned
>> and a DHCP address that dhcpcd5 has picked up and allocated.

>> Remove dhcpcd5 and things should work the way they are supposed to.

>> If you want DCHP for another interface, just install dhcpcd (no "5")
>> instead and things will work properly.
> Dom, You have lost me here.
> Where is, and what is dhcpcd5.
> At one stage during my attempts to get things right it gave me a
> primary address of 192.168.1.90 and a secondary address of
> 192.168.1.95,
> My search for the 95 address is still running.

> Malcolm
The search has now produced the following:-
Aug 7 19-30 raspberry avahi-daemon[2377] Joining mdns multicast group 
on interface wlan0. ipv4 with address 192.168.1.95
"" etc"" Registering new address for 192.168.1.95 on wlan0. ipv4
"" etc"" Listening normally on 3 wlan0 192.168.1.95 UDP 123

Can anyone make any sense of this ?

Malcolm



-- 
T M Smith
Using an ARMX6 and RISC OS 5.21 in the North Riding of Yorkshire

[toc] | [prev] | [next] | [standalone]

#9384

On Fri, 07 Aug 2015 22:14:12 +0100
T M Smith <tmsmith36@tmsmith36.plus.com> wrote:

> The search has now produced the following:-
> Aug 7 19-30 raspberry avahi-daemon[2377] Joining mdns multicast group 
> on interface wlan0. ipv4 with address 192.168.1.95
> "" etc"" Registering new address for 192.168.1.95 on wlan0. ipv4
> "" etc"" Listening normally on 3 wlan0 192.168.1.95 UDP 123
> 
> Can anyone make any sense of this ?
> 
Those are just log entries - did you search /etc and ~/  ?

[toc] | [prev] | [next] | [standalone]

#9386

In message <20150808172617.5061b25b@ntlworld.com>
          Rob Morley <nospam@ntlworld.com> wrote:

> On Fri, 07 Aug 2015 22:14:12 +0100
> T M Smith <tmsmith36@tmsmith36.plus.com> wrote:

>> The search has now produced the following:-
>> Aug 7 19-30 raspberry avahi-daemon[2377] Joining mdns multicast group
>> on interface wlan0. ipv4 with address 192.168.1.95
>> "" etc"" Registering new address for 192.168.1.95 on wlan0. ipv4
>> "" etc"" Listening normally on 3 wlan0 192.168.1.95 UDP 123
>> 
>> Can anyone make any sense of this ?
>> 
> Those are just log entries - did you search /etc and ~/  ?
Yes, it appeared to search /etc.
I have now got the required result i.e. 192.168.1.90 in use by 
following a forum method given by Nat. Philosopher

The drawback is that WiFi Config does not appear to be used, that is 
it remains blank.

Malcolm


-- 
T M Smith
Using an ARMX6 and RISC OS 5.21 in the North Riding of Yorkshire

[toc] | [prev] | [next] | [standalone]

#9388

On 08/08/15 21:23, T M Smith wrote:
> In message <20150808172617.5061b25b@ntlworld.com>
>            Rob Morley <nospam@ntlworld.com> wrote:
>
>> On Fri, 07 Aug 2015 22:14:12 +0100
>> T M Smith <tmsmith36@tmsmith36.plus.com> wrote:
>
>>> The search has now produced the following:-
>>> Aug 7 19-30 raspberry avahi-daemon[2377] Joining mdns multicast group
>>> on interface wlan0. ipv4 with address 192.168.1.95
>>> "" etc"" Registering new address for 192.168.1.95 on wlan0. ipv4
>>> "" etc"" Listening normally on 3 wlan0 192.168.1.95 UDP 123
>>>
>>> Can anyone make any sense of this ?
>>>
>> Those are just log entries - did you search /etc and ~/  ?
> Yes, it appeared to search /etc.
> I have now got the required result i.e. 192.168.1.90 in use by
> following a forum method given by Nat. Philosopher
>
> The drawback is that WiFi Config does not appear to be used, that is
> it remains blank.
>
Tht is a general way with linux.

The raw behind the scenes way of doing things has been overlaid with 
windows like GUI tools, which have minds of their own and probably thrir 
own config files and work on the machine as a user level device.

For example, if I switch users on my desktop any USB drives already 
mounted are unavailable to the new user and give errors.

The sp0rt of rationale is that the machine is a single user desktop 
machine and therefore it ought to have everything that a user does 
vanish with that user.

However the other way of looking at a linux machine - as a multi-user 
server - has a completely different mind set associated with it,. You 
don't want ip addresses changing on a whim...
> Malcolm
>
>


-- 
New Socialism consists essentially in being seen to have your heart in 
the right place whilst your head is in the clouds and your hand is in 
someone else's pocket.

[toc] | [prev] | [next] | [standalone]

#9376

On 07/08/15 21:10, T M Smith wrote:
> Dom, You have lost me here.
> Where is, and what is dhcpcd5.
> At one stage during my attempts to get things right it gave me a
> primary address of 192.168.1.90 and a secondary address of
> 192.168.1.95,
> My search for the 95 address is still running.

Hi Malcolm, ok, maybe you don't have it installed, but it is standard on 
the latest Raspbian images and bloddy annoying if you want to set a 
static address.

dhcpcd5 is a DHCP client deamon. It handles the DHCP on your network 
interfaces. Unlike previous clients it ignores the settings in 
/etc/network/interfaces and just does its own thing. So if you set a 
manual address in /etc/network/interfaces you get two addresses - one 
from interfaces and one set by dhcp.

To check if you have it installed:

dpkg -l dhcpcd5

If it comes up with a line starting with "ii  dhcpcd5", then it is 
installed.

To remove it:

sudo apt-get remove dhcpcd5

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.sys.raspberry-pi

csiph-web