Hello. Can someone please help with setting up VLANs on my Procurve 1810G-24, firmware P.1.6. This is an example what I would like to achive: Eg.: 1 VLAN, subnet 1, port 2. 2 VLAN, subnet 2, ports 13,15,17,19. 3 VLAN, subnet 3, ports 14,16,18. Port 1 connects up to DHCP server, that's why I need all three VLANs can see Port 1 and connect it.
You haven't said where your router is connected and on which VLAN. Your router is what will forward the DHCP request packets from the clients on VLANs 2 and 3 to the DHCP server (using the "ip helper-address" option)
I have no router, only Procurve 1810G-24. Several interfaces with the ip-addresses of three subnets were set up on the network card at dhcp-server. Now without VLAN-s all works. But I want to organize VLAN-s.
So your server supports VLAN tagging and you've assigned the same VLAN IDs to the server as you have on the switch? If so the only thing you're missing is tagging all the client VLANs on the port that the DHCP server is connected to.
Ok, I'm not 100% on creating virtual interfaces on linux servers but the problem appears to be that you have setup IPs on the server that are in different subnets but all on the same VLAN (vlan_raw_device eth0). Once you've fixed that then you need to tag all the client vlans onto the port that the DHCP server is connected to.
> What do you mean, saying your phrase > "tagging all the client VLANs on the port > that the DHCP server is connected to"?
What switch is your DHCP server connected to? You want to tag VLANs 2 and 3 (from your example) onto that port if you want it to be able to see subnets 2 and 3.
I have to point out this isn't the recommended method of doing this. What you want is a switch that can perform routing which would hold the gateway IP addresses for each of the other subnets. All you would need to do then is add ip helper-addresses onto the vlans (that point to your DHCP server) on that switch and make sure your routing is correct and then you'd be done.
The 1810G switches don't do routing and hence you can't add ip helper-addresses to them. I know you said you don't have a router but how is your traffic routed to the internet?
The user in the thread that you are linking to was using a router to route between their subnets so your setup isn't the same. The problem that you have is making sure your DHCP server can see clients on each of the different subnets/VLANs. You didn't answer the question:
To determine whether your DHCP IP addressing config is correct do this:
Statically assign an IP address in, for example, subnet 2 (vlan 2) to a client PC. Connnect that client to a vlan 2 port and see if you can ping the subnet 2 IP on your dhcp server. If you can't do that then your IP address setup on your DHCP server is wrong.
DHCP (Proxy) server connects up to Port 1 of this switch.
According to your manual and information received from the forum topics, I did something like it shown in the attached scheme (this is just an example). But the fact is that computers from the subnets do not see a server connected to the first port, even if the ip-address to enter manually. And, it's actually a fundamental condition.
Would you be so kind to draw schematicly how to correct my scheme.
The attached file doesn't really make sense without any VLAN labels :) But if I assume that the top is VLAN 1 and the bottom VLAN 2... Are you saying that you connected a statically addressed client on VLAN 2 and plugged it into either port 4 or 5 and you couldn't ping the VLAN 2 IP address on the DHCP server? If that is true then the IP addressing on your DHCP is incorrect.
Why wrong? Yes, the top VLAN1, the bottom VLAN2. Without organization VLANs all pinged fine. So why with VLAN, configured as in the scheme, addressing is incorrect?
