Selfhosted

40347 readers

401 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

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

ssh into raspberry without a router (lemmy.ml)

submitted 9 months ago by WbrJr@lemmy.ml to c/selfhosted@lemmy.world

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

[–] rtxn@lemmy.world 31 points 9 months ago* (last edited 9 months ago) (14 children)

Give each device a static address, and set the default gateway to whatever's on the other end of the cable. You might need a crossover cable, but most NICs can work using a straight-through.

E.g. set the laptop's address to 169.254.1.1/16 and default gateway to 169.254.1.2, and the RPi's address to 169.254.1.2/16 and default gateway to 169.254.1.1. They should be able to talk to each other then.

If those addresses seem familiar - Windows uses the 169.254.0.0/16 subnet to automatically assign random addresses if DHCP fails, so that if there are several computers in the subnet, they'll at least have addresses that can talk to each other. It's called APIPA in Windows, and Zeroconf in the Unixverse.

[–] atzanteol@sh.itjust.works 2 points 9 months ago (1 children)

Would you set a gateway? They're on the same network.

[–] thecrotch@sh.itjust.works 1 points 9 months ago

You would not. In the example given 169.254.1.1 doesn't even exist, no machine is listening on that address so it couldn't possibly do any good if it wanted to

load more comments (12 replies)