help on login into Raspberry pi headless

[RameshNB]

Hi,

I am trying to login into raspberry pi headless, i have tried using NOOBS and Raspian IMG file.

I get my host assigned the local network IP Address (198.168.8.11) after booting the Pi connected to Host using a cross cable.

but could not able to get PI Board address, i have tried using NMAP and Zenmap to get the PI Board IP address. the output is as below,

--------------------------------------------------

Starting Nmap 6.46 ( http://nmap.org ) at 2014-05-20 22:39 India Standard Time

Skipping SYN Stealth Scan against 192.168.8.11 because Windows does not support scanning your own machine (localhost) this way.

Nmap scan report for 192.168.8.11

Host is up


------------------------------------------------------------

Not able to get PI Board address. Please help in this regards,

Thanks & Regards,
Ramesh N B

[allfox]

Is a cross cable means a specially rewired Ethernet cable for connecting two PC directly without a switch? If so, you don't need that, as Pi could detect that situation and make necessary change on herself. You could just plug in a normal cable between PC and Pi.

Raspbian image default to DHCP, so using a network scaner won't find Pi, because Pi don't ever have an address on her own.
Three solutions here:
1 - Give your PC DHCP capability. So PC will assign Pi an address. Dnsmasq is cool. (http://www.thekelleys.org.uk/dnsmasq/doc.html)
2 - Just edit the Pi's network config to give her a static address (directly edit /etc/network/interfaces on SD card). You would need a Linux PC to do this as Pi is using ext4 file system who Windows won't work with.
3 - Plug Pi to a router, as most router have DHCP capability, Pi will just act like a normal PC.

I'm using No. 3

[stevech]

I've long used VNC to access remote PCs.
I also do so with RPi. VNC on it, in server mode.
Works great.
There's a how-to on this kicking 'round Pi circles.
Not hard, but assumes you know some of the jargon

I have my home router setup with a DHCP reservation for the PI's WiFi and ethernet MAC addresses. So I know those to LAN IP addresses will be the ones I put in the router's reservation table. Most routers support that.

[DougieLawson]

To pre-assign an IP address add
ip=169.254.3.14
to the end of /boot/cmdline.txt (or F:\cmdline.txt if you're editing it on Windows)

Wire that directly to your laptop, boot the Pi and log in with putty 169.254.3.14, no router, no DHCP need.

Beware, if you leave that on the end of cmdline.txt and don't have a cable connected you WILL delay your Pi booting by 120 seconds.

[allfox]

To pre-assign an IP address add
ip=169.254.3.14
to the end of /boot/cmdline.txt (or F:\cmdline.txt if you're editing it on Windows)

Wire that directly to your laptop, boot the Pi and log in with putty 169.254.3.14, no router, no DHCP need.

Beware, if you leave that on the end of cmdline.txt and don't have a cable connected you WILL delay your Pi booting by 120 seconds.

Wow, I'm first time to know this!

[RameshNB]

Hi DougieLawson,

Thanks For Reply,

Your solution worked. But i have used with DHCP, used ip for Rasberry Pi in the subnet of ip of host assigned by DHCP.

I got Destination not Reachable if i dont use DHCP, mostly i have to configure Gateway properly.

Thanks,
Ramesh

To pre-assign an IP address add
ip=169.254.3.14
to the end of /boot/cmdline.txt (or F:\cmdline.txt if you're editing it on Windows)

Wire that directly to your laptop, boot the Pi and log in with putty 169.254.3.14, no router, no DHCP need.

Beware, if you leave that on the end of cmdline.txt and don't have a cable connected you WILL delay your Pi booting by 120 seconds.

[RameshNB]

Thanks,

Using DHCP was useful,
but DHCP didn't assign any IP to PI Board,
i used nmap to scan the IP range in host Subnet. I did find only IP of Host from nmap.
Can you tell me why DHCP not assigned IP to PI?

Thanks,
Ramesh N B

Is a cross cable means a specially rewired Ethernet cable for connecting two PC directly without a switch? If so, you don't need that, as Pi could detect that situation and make necessary change on herself. You could just plug in a normal cable between PC and Pi.

Raspbian image default to DHCP, so using a network scaner won't find Pi, because Pi don't ever have an address on her own.
Three solutions here:
1 - Give your PC DHCP capability. So PC will assign Pi an address. Dnsmasq is cool. (http://www.thekelleys.org.uk/dnsmasq/doc.html)
2 - Just edit the Pi's network config to give her a static address (directly edit /etc/network/interfaces on SD card). You would need a Linux PC to do this as Pi is using ext4 file system who Windows won't work with.
3 - Plug Pi to a router, as most router have DHCP capability, Pi will just act like a normal PC.

I'm using No. 3