30
ssh into raspberry without a router
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Feb 2024
30 points (87.5% liked)
Selfhosted
40183 readers
491 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Or simply set up the Pi with a static IP.
There is. A cable. You just need two non-identical IPs from the same subnet, e.g. 10.0.0.1 and 10.0.0.2 or whichever you want from the private ranges.
I think this method should be the top answer.
I connect directly to devices without a router most working days for work and this is the method we use because it's simple and effective.
I remember from back in the day that you need a ~~"twisted pair”~~ edit: ”cross-over” cable though, or do modern ethernet ports automatically adapt to that now?
Twisted pair refers to the twisting of the wires in the cable to reduce crosstalk.
Crossover cables enable permit connecting two non-sensing ports together.
Right 🤦♂️ It has been a while. I corrected it in the original post now.
I hear ya. I know all this stuff, but dammit if it isn't hard to access sometimes! Haha
You're thinking of crossover cables, though I'm not sure if those are still necessary.
Most modern NICs can auto-negotiate the Rx/Tx circuits on either kind of cable, but I'm not sure about RPi.
Only one device needs to be able to negotiate it.
Just about everything made in the last 20 years is capable of doing this.
If I remember correctly, 1000Base-T standard has a requirement that device has to negotiate pinout on the fly. No matter which pin is connected to which. Obvioiusly just randomly wiring a cable up has other problems, like signal-to-noise, but in theory it should work even if you make a cable that's as unstandard as you can make it.
That's amazing. I would love to see the algorithm for that. Hopefully I'll find a nice explainer if I search around.
I think it doesn't matter nowadays. Network interfaces are smart enough to twist them internally, or at least, this is what I experienced. I have no idea when did I had to use specifically a crosswire cable, all of my ethernet cables are patch cables for a while now.
So, it shouldn't be a problem.
This for sure, and bonus points for "USB Ethernet gadget" mode if you have a 4 or zero ;)