Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
Forum Thread Details
  • State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 705 subscribers
  • Views 821 views
  • Users 0 members are here
Related

Help on bridging raspberry pi to laptop with Ethernet for internet

e14 Contributor
e14 Contributor

I am trying to bridge my internet from my laptop over to my Rpi with an Ethernet cable, I have successfully been able to created a bridge on the laptop end and the raspberry pi says it is getting internet, but I can not go on Midori or the Pi Store. When I go to WIFI config it says "Could not get status from wpa-supplicant" What could I bee doing wrong?

  • 0

    can the PI and laptop talk, that is the first challenge, the Laptop and PI may need a cross over cable depending on model and drivers, using a hub between the two would be simpler

     

    if you have a cross over cable or the drivers on the LT support it, once the bridge is established you should be able to get an IP address etc via DHCP on the PI or you can configure both manually with the tcp/ip details (IE. PI on 192.168.200.2, laptop on 192.168.200.3, subnet mask 255.255.255.0, default gateway on the PI would be 192.168.200.3, default gateway on the LT would be the WiFi hub IP address , DNS in all cases would be the same as the LT gets from the WIFI

     

    So, what are you getting in your setup

     

    Hope this help

     

    Peter

  • 0

    provide a quick drawing to show your connections and the IP values for the nodes.

  • e14 Contributor
    0 e14 Contributor in reply to Robert Peter Oakes

    Thanks, but I am going to try to use a WIPI for the sake of simplicity and less wires

  • 0

    One problem with bridging (on Windows or OSX) is that there's nothing in Linux to automatically assign an IP address from the 169.254.xxx.xxx address range. Windows picks an address from that range when there's no DHCP server that's reachable. Linux doesn't do that.

     

    So to get it working (and it doesn't need a cross over cable) you need to pre-assign an IP address for the Raspberry Pi.

     

    The simple way to do that is in /boot/cmdline.txt

     

    Add ip=169.254.3.14 to the end of the stuff that's already there.

     

    dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait quiet ip=169.254.3.14

     

    Reboot and the eth0 interface will be running with that IP address and a netmask of 255.255.0.0. When you connect that to the Windows Laptop it should "just work" and 169.254.3.14 will be pingable and (assuming sshd is running on your RPi) connectable with PuTTY.

  • 0 in reply to e14 Contributor

    To use WiPi you need to update your /etc/network/interfaces and /etc/wpa_supplicant/wpa_supplicant.conf files

     

    /etc/network/interfaces

    auto lo
auto wlan0
iface lo inet loopback
iface eth0 inet dhcp

allow-hotplug wlan0
#wireless-power off
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp

     

     

    /etc/wpa_supplicant/wpa_supplicant.conf

    ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
 ssid="YourWiFISSIDhere"
 scan_ssid=1
 psk="yourWiFiPasswordhere"
}

    HTH