this post was submitted on 23 Jun 2023
2 points (100.0% liked)

Selfhosted

39239 readers
446 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I saved an HP Procurve 2610 switch from garbage and I am trying to get it setup. I able to get connected to it with a serial cable and move around the menu but that is as much as I understand about these things. I would like to setup a VLAN but have never worked with them before so totally lost. I did try searching for anything related to setting this up but have not had much luck.

Is there anyone that could at least give me some direction on how to do this or if it is a little over my head. TIA!

top 2 comments
sorted by: hot top controversial new old
[–] solidgrue@lemmy.world 0 points 1 year ago* (last edited 1 year ago) (1 children)

There is a lot to cover here, sorry for brevity:

Start there. I'm happy to answer questions.

Edit: Dammit! Preview, not post!

[–] solidgrue@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

New post, because I can't keep just editing stuff...

You have an enterprise class switch that can act as a switch in the traditional sense, and (technically) a router. To define a VLAN is to carve out a section of ports to act as a virtual switch. In a VLAN, the ports can all talk among themselves, but need a router to talk to ports on other VLANS. Your switch should be able to provide that function, (routing or Layer 3 gatewaying).

Each VLAN needs its own IP range. You are probably used to dealing with IO addresses like 192.168.1.10, or similar. The gateway address is the .1, and the broadcast is the .255.

In an enterprise switch, also called a "Layer 3 switch," you can assign an IP range to each VLAN. Commonly, you number the VLAN ID and the third octet of the IP address as

VLAN 2 is 192.168.2.0/24
VLAN 3 is 192.168.3.0/24
etc

Usually the gateway address, the switch's address in this case, is the .1 address. Everything on each VLAN needs to use an address in the same range (e.g., 192.168.3.x on VLAN 3) and use the VLANs gateway address on the switch 192.168.3.1 as the default gateway.

Finally your switch needs a VLAN to talk to your ISP modem. That address on the modem is usually 192.168.1.0/24, with the modem address being the .1 and your switch address being .2 or higher. For your switch, you'd set up the VLAN 1 as 192.168.1.2/24, and have it use 192.168.1.1 as its own default gateway. Finally you'd need to tell your modem to send 192.168.0.0/16 to 192.168.1.2 on its LAN port¹.

That's what I've got for you for now. Still happy to answer questions

¹ consult your ISP modem manual for advanced routing options

Edit: significant typos.