Timeline for Struggling to configure VLAN properly (LANCOM, no internet)
Current License: CC BY-SA 4.0
21 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 21 at 10:50 | history | reopened | Zac67♦ | ||
| May 21 at 10:39 | history | edited | ImanityDev | CC BY-SA 4.0 |
added 129 characters in body
|
| S May 21 at 10:36 | review | Reopen votes | |||
| May 21 at 10:55 | |||||
| S May 21 at 10:36 | history | suggested | CommunityBot | CC BY-SA 4.0 |
Added detailed device configurations as requested
Added to review
|
| May 21 at 10:34 | review | Suggested edits | |||
| S May 21 at 10:36 | |||||
| May 14 at 14:26 | comment | added | FrameHowitzer | Yes, the DHCP server must have pools configured for every network where you want DHCP to work. And you need to configure a DHCP Helper/Relay feature on your network equipment to allow a single server to provide configuration for multiple networks. | |
| May 14 at 12:21 | history | closed | Zac67♦ | Needs details or clarity | |
| May 14 at 12:03 | answer | added | Ron Trunk | timeline score: 2 | |
| May 14 at 9:19 | comment | added | ImanityDev | @FrameHowitzer I found the config in the IPv4 settings. However, I would need to add the new subnets to the DHCP server, correct? | |
| May 14 at 5:00 | comment | added | ImanityDev | @FrameHowitzer There are no such settings in the GUI Interface of the router, so I don't know how or where to configure this. | |
| May 14 at 4:59 | comment | added | ImanityDev | @RonMaupin As I said, DHCP Relay is not configured at the moment, as well as NAT. I didn't change anything about these settings for now. | |
| May 14 at 4:58 | comment | added | ImanityDev | @RonTrunk The default config is untagged on each port. | |
| May 13 at 14:13 | comment | added | FrameHowitzer | You can't use a single subnet of IP addresses over multiple VLANs. Each VLAN will need its own subnet and gateway address configured on a VLAN sub interface of your router. The router must 'trunk' or tag all VLANs on its port to the main switch and the main switch must 'trunk' or tag all VLANs on ports to any switches where you want those VLANs to be used. | |
| May 13 at 13:05 | comment | added | Zac67♦ | You only show us VLAN memberships. It's also essential whether a VLAN is tagged (on a trunk, towards switches or routers) or not (towards end nodes). From dim memory, Lancom routers used a "Port-VLAN-ID" for untagged membership. Generally, check the switch's MAC table to see whether a node is on the desired VLAN - using Windows NLA is a rather unreliable method. | |
| May 13 at 13:02 | comment | added | Ron Maupin♦ | We really need the full configurations, including things like DHCP relay and NAT configurations. Please list out the configurations in CLI and paste them into the question using the Preformatted Text option. | |
| May 13 at 13:00 | comment | added | Ron Trunk | I'm not familiar with LANCOM, but somewhere you need to indicate what VLAN is untagged on each port.. | |
| May 13 at 12:54 | comment | added | ImanityDev | @RonMaupin Did so. I thought it wouldn't be necessary because the basic configuration is very rudimentary. | |
| May 13 at 12:53 | history | edited | ImanityDev | CC BY-SA 4.0 |
added 434 characters in body
|
| May 13 at 12:43 | comment | added | Ron Maupin♦ | Please edit your question to include the network device configurations. We cannot guess where you may have gone wrong. | |
| S May 13 at 12:36 | review | First questions | |||
| May 14 at 12:25 | |||||
| S May 13 at 12:36 | history | asked | ImanityDev | CC BY-SA 4.0 |