Sunspot Home. . . . . . Joggler menu
Set a fixed LAN address
I have several Linux devices on my wired ethernet network - they need to know how to talk to each other.
There is a startup script /etc/init.d/dysentry that resets dhcp after you thought you had set a fixed address - very confusing!
- so kill it -
root@joggletop:~# update-rc.d -f dysentry remove
Removing any system startup links for /etc/init.d/dysentry ...
Remove NetworkManager (since it allows no control of addresses [why not?] )
apt-get remove network-manager
it says -
The following packages will be REMOVED
- and replace it with -
apt-get install gnome-network-admin
You should be able to use the new GUI for network in System to set the various network files
- but I got mixed results (it wrote in values for eth4 for some reason) and I ended up setting these files by hand using ftp.
- but then on the next boot, and only sometimes (!), the Joggler has no network connection.
Then use the network GUI tool and reset to the address you thought you had set manually by modifying the files.
It then works fine but you find on inspecting the files that eth2 or perhaps eth4 has been created in /etc/network/interfaces.
But it is working now, who cares? - - - - I do - help!
- for a LAN address of 192.168.0.43 -
# The following lines are desirable for IPv6 capable hosts
In System - Startup Apps Prefs untick Network Manager
(and to save memory I untick Screensaver and Cups)
This seems to be working - but in dmesg I still see
[ 33.344559] type=1505 audit(1104537654.478:13): operation="profile_replace" pid=1082 name=/usr/lib/NetworkManager/nm-dhcp-client.action
So why is that still there? - I think I see a related error as the Joggler boots? - but it seems not to matter.
Can an expert help to sort this out please? - email me here
At times (but not very often) my Joggler slows to a crawl - several 10s of seconds per action. I suspect network activity in the background - or perhaps overheating ?????
Anyway - I have my fixed address . . . . . . .
To run a hard disk modify a short USB extension lead (the Joggler can't supply enough current from the USB socket).
Cut the red wire and connect the part going to the socket on the extension lead to the +5V line from the wall power supply.
The red wire going to the extension lead plug is taped up (no power from the Joggler is used by the hub).
Connect the black wire in the USB extension cable (do not cut it) to the power supply earth.
Plug the USB cable into the Joggler and the hub.
Apply power to the USB cable first to spin up the drive then power up the Joggler. (Actually, I am not sure if that is necessary - after a controlled poweroff you can leave it all connected and switch on at the wall)
To backup a USB memory stick or disk drive
Plug the empty drive into a Linux PC (assume this becomes /dev/sdb)
Plug the working drive into the same PC (assume this becomes /dev/sdc)
I check the drive numbers in System/Administration/Partition Editor - and while there I completely empty the drive that will receive the new files. (This is perhaps similar to crossing your fingers - you get a lot of that with a Joggler)
Then copy from sdc to sdb
dd if=/dev/sdc of=/dev/sdb bs=10M
I also make a backup image
dd if=/dev/sdc of=/path/to/disk_back_up_image.img bs=10M
and to use that image on a new drive -
dd if=/path/to/disk_back_up_image.img of=/dev/sdc bs=10M
I find dd is not fully reliable - in the Joggler some memory sticks or disks boot to a command line, some do not boot at all - but try again and they may work.
(I had expected to be able to set the 2 partitions to FAT32 and ext2 then just copy the files from a good memory stick - but that never works even though on my other Linux routers etc it always works.)
Best to shutdown rather than reboot (it is said) - after clicking shutdown (top right menu) you see the terminal screen asking you to log in !!
Just wait - the shutdown messages can take some time to appear with a memory stick.
(Much faster with a hard disk)
Sunspot Home . . . . . . . Joggler menu