Selfhosted

39435 readers

4 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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

ssh into raspberry without a router (lemmy.ml)

submitted 8 months ago by [email protected] to c/[email protected]

39 comments fedilink hide all child comments

Hi! I hope this is the right community to ask.

Next week I will be on the road for 5 Days for work. I have quite some spare time, so I thought I would dig up my raspberry project again and hopefully finish it.

I need it with me, because it controls some hardware, so a VPN to home does not work. So only option I could think of, is to connect the pi directly to my laptop via an ethernet cable. As far as I understood from some research is that I would need to install and run an DHCP server on my laptop, which they did not recommend. Alternatively they suggested to just take a router and plug both devices in there. I don't really have a spare router, so that's not an option either.

To be hones it confuses me a little, that there does not seem to be a standard for connecting to a device directly over a single cable and login with a user account.

Any recommendations how I can work on the pi like with ssh?

Thanks a lot!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 8 months ago* (last edited 8 months ago) (3 children)

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?

[–] [email protected] 4 points 8 months ago (1 children)

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.

[–] [email protected] 3 points 8 months ago* (last edited 8 months ago) (1 children)

Right 🤦‍♂️ It has been a while. I corrected it in the original post now.

[–] [email protected] 0 points 8 months ago

I hear ya. I know all this stuff, but dammit if it isn't hard to access sometimes! Haha

[–] [email protected] 4 points 8 months ago (1 children)

You're thinking of crossover cables, though I'm not sure if those are still necessary.

[–] [email protected] 4 points 8 months ago (1 children)

Most modern NICs can auto-negotiate the Rx/Tx circuits on either kind of cable, but I'm not sure about RPi.

[–] [email protected] 3 points 8 months ago (1 children)

Only one device needs to be able to negotiate it.

Just about everything made in the last 20 years is capable of doing this.

[–] [email protected] 2 points 8 months ago (1 children)

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.

[–] [email protected] 1 points 8 months ago

That's amazing. I would love to see the algorithm for that. Hopefully I'll find a nice explainer if I search around.

[–] [email protected] 2 points 8 months ago

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.