Differences

This shows you the differences between two versions of the page.

--- fuss:raspberry_pi [2020/04/20 20:06] – office
+++ fuss:raspberry_pi [2020/05/08 21:55] – [Connecting to a Bridge Automatically] office
@@ Line 89: / Line 89: @@
 The Raspberry can now be connected to a PC via its USB port (not the USB port marked ''PWR''). The PC that the Raspberry Pi connects to will act as a router and should forward packets to the Raspberry Pi.
-Assuming that the Raspberry has been freshly set up, to connect via SSH, issue: ''ssh pi@raspberry.local'' and enter ''raspberry'' at the password prompt.
+When the RNDIS interface is brought up, if Apple bonjour is installed and running on the machine that the Raspberry Pi is connected to, then the Raspberry Pi is supposed to register the DNS address ''raspberry.local'' via mDNS with Windows. Even if Apple bonjour is installed, the name might not be assigned even though the Rasbperry Pi might be configured properly as per the above. Also, it seems that in some cases when the RNDIS interface is brought up, the Raspberry Pi does not send any packets as all making an ARP table query via ''arp -a'' entirely futile.
+The first attempt would be to try connecting via the assigned DNS address: ''ssh pi@raspberry.local'' and enter ''raspberry'' at the password prompt. if that fails, a packet sniffer such as WireShark or TcpDump may reveal the initial Raspberry Pi's ARP requests for Google's DNS servers (''8.8.8.8''). Sometimes just restarting the bonjour service and disabling and re-enabling the RNDIS interface may get the Raspberry Pi to register its name.
+===== Connecting to a Bridge Automatically =====
+In order to connect the Raspberry Pi to a bridge as it is connected to a server, [[fuss/linux#automatically_add_all_rndis_devices_to_a_bridge|an udev rule can be written]] that will match all RNDIS adapters and connect them to a bridge.
+The only changes required on the Raspberry Pi is to edit ''/etc/network/interfaces.d/usb0'' and add the lines:
+<code>
+auto usb0
+iface usb0 inet dhcp
+</code>
+and save the file. This will make sure that when the Raspberry Pi boots, an IP address will be requested over the ''usb0'' interface and will work provided that the computer that the Raspberry Pi is connected to is running a DHCP server on the other end.
 ====== Enabling Monitor Mode via Nexmon Drivers ======