element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Raspberry Pi
  • Products
  • More
Raspberry Pi
Raspberry Pi Forum I need help connecting to internet
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Raspberry Pi to participate - click to join for free!
Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Verified Answer
  • Replies 7 replies
  • Subscribers 676 subscribers
  • Views 793 views
  • Users 0 members are here
  • raspberry_pi
Related

I need help connecting to internet

Former Member
Former Member over 12 years ago

First off, I'll introduce myself. My name is Dan, and I am a pc tech/repair guy during my free time. I am young, so I don't have a lot of knowledge yet, but I am learning. I currently have next to no knowledge of how to navigate any Linux distro.

 

My issue is in internet connections. I have connected my pi (type b with pimame/raspbian os) to my router via a normal cat5 ethernet cable, and expected the network lights to blink. The result was disappointing, the lights did not blink, neither did I have access to the web through midori. The router is configured to use DHCP (I cannot access that part of my router, however my dad can, and he is a CTO for a school district). I have looked all over the internet for why this would happen, and have found no documentation for what to do in this situation. I am not sure what to do, I really only want to install ndiswrapper, that way I can install win2k drivers for my USB Wi-Fi dongle (D-link DWA-130 version E1), that way I can have wireless connection. I have also tried connecting to my pc. I connected the two with a standard ethernet cable, and installed PuTTY in order to connect the two. I get an error that the connection timed out. I have also gone the route of modifying the cmdline.txt and adding my pc's ipv4 address (which is not static I believe). I have also gone into the terminal on my pi in order to set an ip address, but that doesn't seem to assist me at all in my connection with my pc, or router.

 

If there is any way to fix my ethernet port or board (if broken), or install ndiswrapper via and offline installer or download, I would be grateful. This "malfunction" is starting to get on my nerves. If you need any more information, I would be glad to provide it.

 

Thanks.

  • Sign in to reply
  • Cancel
Parents
  • Former Member
    0 Former Member over 12 years ago

    Hello Dan,

    have you try using a cross-over cable?

    When you directly connect two client with an ethernet cable you must use a cross cable.

    You have to use a cross cable also if you connect a client directly to a router port if it has not an integrated switch.

    A straight cable is fine to connect router, server or client to a switch.

     

    Ethernet port use two pairs of the rj45 connector: pins 1-2 and 3-6.

    A standard cable (straight cable) connect pins 1, 2, 3 and 6 of one connector to the same pins of the other connector.

    A cross cable connect pair 1-2 of one end to pair 3-6 on the other end, and pair 3-6 to pair 1-2.


    Enjoy your raspy....

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Former Member
    0 Former Member over 12 years ago

    Hello Dan,

    have you try using a cross-over cable?

    When you directly connect two client with an ethernet cable you must use a cross cable.

    You have to use a cross cable also if you connect a client directly to a router port if it has not an integrated switch.

    A straight cable is fine to connect router, server or client to a switch.

     

    Ethernet port use two pairs of the rj45 connector: pins 1-2 and 3-6.

    A standard cable (straight cable) connect pins 1, 2, 3 and 6 of one connector to the same pins of the other connector.

    A cross cable connect pair 1-2 of one end to pair 3-6 on the other end, and pair 3-6 to pair 1-2.


    Enjoy your raspy....

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
  • Former Member
    0 Former Member over 12 years ago in reply to Former Member

    If the on board led's don't flash when the Pi is first plugged in then the problem is the Pi hardware.  If the lights flash and then go out leaving just the red led lit it means no connection was found so the cable is suspect.  If you are plugging into a Gigahertz port on the router or Windows PC the crossover/straight cable mentioned above isn't an issue but it does matter with the 10/100 ports.

     

    My first need is to get the Pi onto a wireless connection.  Plug in a Linux compatable dongle (Edimax used here) before applying power to the Pi.  Now power it up and in a terminal on your remote pc type:

    ssh pi@raspberrypi

    If it asks for a password everything network is working.  The default password is raspberry.

     

    Unfortunately most wireless hosts will be password protected so this will fail and a cable connection must be used to enter the  required information into /etc/network/interfaces. 

    Try adding these two lines at the bottom of that file

    wpa-ssid "FRITZ!Box 3272"

    wpa-psk  "xxxxxxxxxxxxxxxxxxx"

    replacing the above with your box and WPA-2 number from the label on the router.

    Reboot everything and DHCP should find everybody and make the connections automatically.

     

    Detailed debugging:

    On windows, a knoppix live-cd is booted to get the GNU tools or gnuwin32 on sourceforge might be preferable in some cases but I have never used it.  

     

    Here are the tools used, there are lots of others.  'WireShark' is good for packet content examination.

    lsusb

    lsmod

    traceroute raspberrypi

    The following are available in raspbian OS but are not on a default Debian install. 

    iwconfig

    ifplugstatus

    iwlist scanning

    Grep is a great help. It locates a word or phrase and then returns the line of text in which it was found.  A pipe "|" takes the output of the command to its left and uses it as input for the command on its right.

    lsusb | grep Wireless

    The Realtek RTL8187 is found on my PC and RTL8188 on the Pi.  Your Pi should be the same.

    iwconfig returns Wireless Device parameters like ESSID: Access Point: and their related MAC address.

    traceroute raspberrypi

    can be typed on the pc command line and a return gives the IP number assigned by DHCP to the Pi.

    nmap is used to find what is connected where to my router.

    nmap -v -sn 192.168.188.*

    The 188 could be 178, 202, or near anything so look in your router manual to get that information.

     

    Ifconfig is depricated, "ip" has replaced it. Either can be used to read or modify your internet configuration.

    ifconfig

    Returns the configuration of each ethernet connection available on your PC.  The MAC, and IP are given for each available interface.  When ifconfig is used to change nework parameters they are again lost on reboot.

    ifup eth0

    could bring your LAN to life if it is not set to start during the boot process.   

    Finally, to add wlan security info, sudo nano /etc/network/interfaces and modify it.

    This file must retain the lines

        auto lo  

        iface lo inet loopback

    Everything else can be changed. 

    My /etc/network/interfaces follows: 

       auto lo

       iface lo inet loopback

     

       iface eth0 inet dhcp

     

       auto wlan0

       allow-hotplug wlan0

       iface wlan0 inet dhcp

       wpa-ssid "Probably your router name"

       wpa-psk  "A very long number from the label on the router"

     

    Defaults handle everything else.  The eth0 line is only needed for a wired LAN connection

    while the wlan0 block and wpa security information are only needed for wireless. 

    A minimal wired configuration would be:

    auto lo

    iface lo inet loopback

    iface eth0 inet dhcp

    Inline comments are not allowed.  Lines beginning with a # are comments and not read.

    Putting a # in front of each line not shown above should get your system up using defaults.

     

    The howto:

    sudo nano /etc/network/interfaces and comment it to the minimal content given above with wlan0

    chmod 600 /etc/network/interfaces if it doesn't work but this should already be the default security.

    sudo ifup wlan0

    shutdown -h now

    unplug the Pi, unplug the LAN cable and plug in the USB wireless dongle (Edimax EW-7811Un in my case).

    plug in the Pi again and switch on the power.

    Open a terminal on the remote PC and type

    ssh -X pi@raspberrypi

    enter you password (raspberry)

    startx

    If you only use the internet for downloads then forget "startx" and simply test for internet connectivity with

    ping 2.2.2.2

    Check reverse name lookup with:

    ping google.com

    It may also be necessary to unplug your router for 30 seconds to get it to recognize wireless connections.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • johnbeetem
    0 johnbeetem over 12 years ago in reply to Former Member

    Andrea Pergola wrote:

     

    Hello Dan,

    have you try using a cross-over cable?

    When you directly connect two client with an ethernet cable you must use a cross cable.

    You have to use a cross cable also if you connect a client directly to a router port if it has not an integrated switch.

    A straight cable is fine to connect router, server or client to a switch.

     

    Ethernet port use two pairs of the rj45 connector: pins 1-2 and 3-6.

    A standard cable (straight cable) connect pins 1, 2, 3 and 6 of one connector to the same pins of the other connector.

    A cross cable connect pair 1-2 of one end to pair 3-6 on the other end, and pair 3-6 to pair 1-2.

     

    Enjoy your raspy....

    You shouldn't need a cross-over cable with RasPi.  The LAN9512 chip supports Auto-MDIX and I think it's enabled by default.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube