techsupport

3040 readers

4 users here now

The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.

If something works or if you find a solution to your problem let us know it will be greatly apreciated.

Rules: instance rules + stay on topic

Partnered communities:

You Should Know

Software gore

Recommendations

founded 2 years ago

MODERATORS

GatoB@lemmy.world

How can I configure Fresh Tomato to act as an access point so I can access Samba shares on the other side? (leminal.space)

submitted 1 week ago* (last edited 1 week ago) by CorrodedCranium@leminal.space to c/techsupport@lemmy.world

4 comments fedilink hide all child comments

I have a router with a fresh install of Fresh Tomato so none of the settings have been changed yet. The Samba server is on the other side of the access point.

It seems like it should be as simple as making the following alterations in the Network tab:

WAN0 Settings

Type: DHCP -> Disable

LAN

IP address 192.168.1.1 -> 192.168.0.2, DHCP -> Disable

Default Gateway 0.0.0.0 -> 192.168.0.1, Static DNS 0.0.0.0 -> 192.168.0.1

On my other server I would set the Fresh Tomato router as a static IP address.

Whenever I make all these alterations and click save computers connected to the Fresh Tomato router become disconnected from the internet and I can no longer seem to access the router. I've had to reset it.

Is there something I am missing?

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

[–] CorrodedCranium@leminal.space 1 points 1 week ago* (last edited 1 week ago) (1 children)

I don't know if that will be necessary if this is all the same network. I saw a couple posts mentioning VPNs and reverse proxies but they were all for accessing the network remotely.

Kind of similar but I thought VLANs might work as well but all I could really find online was people separating branches their network using them.

I appreciate the comment though.

[–] just_another_person@lemmy.world 1 points 1 week ago

Well you don't want to disable DHCP on the WAN. That's how it gets it's address most likely.

The VPN creates a bridged network between the client and the internal network. VLANs don't do that.

If you want to make the internal server behind the router accessible to you securely when you're out in the world, you want a VPN. That's what it's for.