Logs

I think so.

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

You can view recent messages (which are held in a 16k? buffer) with the dmesg command.

dmesg -T

---druck

Try one or more of :-

dmesg more /var/log/messages more /var/log/syslog

and see what comes up ...

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

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.

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

"dmesg | less" generally works better since most version of dmesg don't have built-in pagination. In any case, 'less' is considerably more than 'more' when it comes the general usability.

Also /var/log/dmesg which is a snapshot of the boot messages. Usefull if you have a system that continually dumps more stuff.

Gordon

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

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

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

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.

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

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:

''

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

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

Malcolm