NSLU2 niet meer te benaderen

[Gast skystar]

Na flashen met demian lenny 5 kan ik via ssh niet meer de nslu2 benaderen.

Het ipadres is onverandert gebleven dus gewoon 192.168.1.77 .

De nslu2 wordt wel herkent mits ik hem direct met een crosscable aan de laptop leg?? Opnieuw flashen is dan ook geen probleem.

In de originele omgeving vn linksys kan ik ook gewoon de nslu via webbrowser benaderen.

Graag zou ik demian icm usb stick op de nslu willen hebben maar verder dan flashen kom ik niet.

Wie o wie weet hoe verder.

 

Martin

[polle58]

After writing the Debian installer to flash, you have to wait for it to start and then connect by SSH to perform the installation. When the installer is ready to accept SSH connections, it will make three beeps and set the status LED to green.

 

Some people report that they are not able to connect to the NSLU2 via SSH at this point. The most common problem is that the wrong IP address is used to connect to the NSLU2. Debian installer will read the network configuration from the original NSLU2 firmware and use that but in some cases different network settings have to be used (for example, because the settings in the original firmware were incomplete).

 

If you cannot connect to your NSLU2, here are three things you can try:

 

Read the explanation of how the Debian installer creates the network settings.

Check the logs of your DHCP server to see whether your NSLU2 has requested an IP address. The MAC address of your NSLU2 probably starts with 00:13:10.

If everything else fails, disconnect the Ethernet cable from your NSLU2 and start your NSLU2 again. In this case, it is possible that the IP address 192.168.1.77 is used

[Gast skystar]

GEEN melding dat de NSLU2 een ip heeft aangevraagd of heeft gekregen.

 

Jan 1 01:00:14 hostapd: wlan0: STA 00:22:43:67:a6:45 IEEE 802.11: authenticated

Jan 1 01:00:14 hostapd: wlan0: STA 00:22:43:67:a6:45 IEEE 802.11: associated (aid 3)

Jan 1 01:00:19 1970 dhcp client: deconfig: lease is lost

Jan 1 01:00:19 1970 dhcp client: bound IP : xx.xx.xxx.xxx from xx.xx.xxx.x

Jan 2 22:08:44 2010 ntp client: time is synchronized to time.nist.gov

 

[polle58]

Get NSLU2 Working

 

 

Avoid the Linksys Setup Wizard, as it assumes that you can immediately connect to your NSLU2.

 

Power up your NSLU2 and connect it to your router or Ethernet hub.

 

Use a web browser on your PC to try and browse to the NSLU2's home page at its factory default address. Do this by typing "http:192.168.1.77" into your web browser's address field.

 

Unfortunately, it is likely that you will not be able to see the NSLU2 owing to its default IP address of 192.168.1.77 not being allowed by your router's settings. If your router's IP address is 192.168.0.1 and its IP subnet mask is 255.255.255.0, then simply changing the mask to 255.255.0.0 (on my Netgear router this is done using the LAN set-up web page) should enable you to browse to the NSLU2's home page. However, if your router's IP address does not start with 192.168 then you have 3 options:

 

Temporarily change your router IP address to 192.168.1.1 (may be difficult).

Take your NSLU2 to a friend with a router that has a 192.168 type IP address and set the router's IP subnet mask to 255.255.0.0.

Note, this is a more technically difficult option. Use an Ethernet "crossover-cable" to connect the NSLU2 directly to a PC, and temporarily reconfigure the PC to an IP address of 192.168.1.1 with an IP subnet mask of 255.255.0.0.

You should now be able to browse to the NSLU2's home page.

 

 

 

Select the Administration page and login as user admin with password admin.

 

If this does not work, then check that your keyboard's Caps Lock is not on, as both this user name and password must be in lower case. Note, later you will change the admin password.

 

You should now be on the LAN page where you should select "Fixed IP Address". Note, selecting automatic IP address (DHCP) gives a message that a fixed IP address is recommended.

 

Enter a suitable IP Address that, if you have changed the router's configuration, allows you to return to your router's original configuration. If your router IP address is 192.168.0.1 and you have not used 192.168.0.2, then this is a suitable IP address. If the ".2" address is already in use, then use ".3", etc. Record the IP address that you have used for later use.

 

Set the Network Mask to 255.255.255.0, the Gateway to your routers address and the Primary DNS and Backup DNS to those given in your Internet Service Provider's documentation (should also be on their web site).

 

Now select Save and this will instantly change the NSLU2 network settings, so loosing the connection. If you had temporarily changed your router settings, you should now change them back and browse to the NSLU2 home page. Your router should be configured such that its DHCP server address range does not include the NSLU2's IP address (on my Netgear router this is on the LAN IP Setup page). I suggest that you save your NSLU2 home page location (typically a favourite or bookmark as supported by your web browser).

 

Change to the System page and set:

 

Server Name - suggest Downloader

Comment - suggest Linksys NSLU2

Workgroup - this is your Windows work group name (as shown in Windows by the Control Panel, System, Computer Name page).

Language Support, Time Zone, Local Date and Time for your location.

Enable WINS - suggest this is disabled.

Enable Guest Logins - this must be enabled.

Convert failed logins to "guest" logins - this must be enabled.

Enable FTP Server - suggest that this is disabled.

Enable uPNP Support - suggest that this is disabled.

Port number for HTTP - this should be 80.

Password for guest account ... - the value appears as a row of dots, but simply ignore.

Now select Save.

 

Plug the pen drive into the NSLU2 USB2 port. Wait a minute. Change to the Advanced page and then select the Disk page. The Disk 2 Status field should show the pen drive is formatted as FAT16/32. If the pen drive is unformatted then you should format it as described in the earlier Getting the Components section.

 

From Windows select My Network Places and drill-down in Entire Network to check that you can see "Linksys NSLU2" and below that "DISK 2". Open the "DISK 2" folder and check that you can both create a file in this folder and then delete the file. By default Windows automatically scans for network folders and creates shortcuts to them in the "My Network Places" folder. These shortcuts are useful, but you should always try a drill-down if the shortcut is not working (bad shortcuts can simply be deleted). Note, ignore any shares named "ADMIN 2" or "hdd*" on the NSLU2.

You are now ready to install unslung on your pen drive

 

[Gast skystar]

probleem is dat de nslu2 in upgrade modus blijft staan lampje knippert rood en groen?

 

Martin

[Big fellow]

Voor alle duidelijkheid, alle berichten dienen in het Nederlands te wezen. Dit staat duidelijk in de huis regels.

Wil je een engelstalig bericht plaatsen dan dien je voor een goede vertaling (dus niet van een vertaalmachine op internet) te plaatsen.

 

Ik zal het deze keer laten staan, maar een volgende keer verwijder ik het bericht.

[Gast skystar]

De nlu2 is weer na veel 5en en 6en benaderbaar nu debian op de usb stick en me verder verdiepen in linux. Weet niet wat het was.

 

Martin

[Gast skystar]

debian draait nu alleen een foutje gemaakt oeps.

In plaats van een / neer te zetten heb ik daar een .(punt) neergezet.

Als linux nono weet ik daar de uitwerking niet van.

Het gaat hier om:ln -s /emu/mpcs/mpcs.cert /usr/local/etc/mpcs.cert (ingevoerd ln -s /emu.mpcs/mpcs.cert /usr/local/etc/mpcs.cert).

Wie weet hoe ik dit weer moet herstellen?

 

Martin

[Lamko]

Maakt niet zoveel uit, gewoon nog een keer doen en nou goed!

Je zou het eventueel op kunnen ruimen maar das niet nodig.

[Gast skystar]

bedankt, ook weer gelukt, nu de smargo reader installeren, protocollen schrijven en die cam kan uit de pc. Kids ook blij boven dus ook tv.

Als linux non freak toch al een aardig eind gekomen vind ik zelf.

 

Martin

[Gast skystar]

helaas draait de cccam server niet. blijkbaar is er geen goed armel bestand geschreven. feest gaat niet door. openslug 3.10 dan maar proberen.

 

martin

[Rigolo]

controleer op een "echte" linux box eens de binaries die aangeleverd worden door CCcam met het "file" commando.

 

Dan krijg je zo iets als dit:

 

Code:

CCcam.mipsel:        ELF 32-bit LSB executable, MIPS, MIPS-I version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.4.0, strippedCCcam.ppc:           ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, strippedCCcam.x86:           ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, strippedCCcam.x86_64:        ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped

 

 

Dan kan je zien voor wat voor een systeem/kernel etc het gecompileerd is.

 

hein

[Gast skystar]

De kernel ed zullen niet het probleem zijn denk dat het te maken heeft met de versie van linux, in dit geval dus debian, hiervoor moet dus de armelversie gebruikt worden. Deze werkt alleen met een little endian icm debian, openslug en unslug gebruiken de big endian versie dus de armeb of armeb.eabi. deze zijn volop te downloaden en zitten zelfs standaart al in het cccam pakket.

 

martin

[Cobus R]

Wat is hier (armeb of armeb.eabi) het verschil van dan ?

 

[Gast skystar]

dit zal het verschil zijn:

EABI is a new application binary interface (ABI) for Linux.

Armeb mist deze applicatie dus.

 

Martin