topic Re: Wired Ethernet Connection Self-Assigned IP Issue in RUCKUS Support for Lennar Homes

Wired Ethernet Connection Self-Assigned IP Issue

stu1720 — Sun, 09 Mar 2025 16:12:08 GMT

I have an ICX 7150-C12 switch in my home with multiple VLANs set up.

For the 1:DEFAULT-VLAN, I have one port 1/1/4 Untagged that has been added. This port is connected to one of the two ethernet wall ports in my home office. I set this up, so I could wire connect to the switch/router/APs when I wanted to make changes on their respective browser based interfaces.

Whenever I physically connect my computer (MacBook Pro M3) to the 1/1/4 wall port, the computer self-assigns the IP and no internet or switch/router/APs connection is made. (I can connect to the interfaces using the wireless WLAN that is tied to VLAN 1.)

I have the second ethernet wall port (1/1/7 Untagged) in my office connect to my “everyday use” VLAN and when I connect to that ethernet wall port, everything works fine. When I moved 1/1/7 Untagged over to 1:DEFAULT-VLAN, the computer again self-assigns the IP and does not work.

Any ideas on what I might have configured wrong?

(For what it is worth, I use an Edge Router 4 as part of my setup.)

Re: Wired Ethernet Connection Self-Assigned IP Issue

Imran_ruckus — Mon, 10 Mar 2025 12:20:31 GMT

Hi @stu1720
Greetings!!!

Thank you for contacting the RUCKUS Community forums.

Before we assist you, could you please let me know if this is a Lennar RUCKUS setup?

Please confirm.

Thank you again.

Best regards,

Imran Sanadi

RUCKUS Lennar Home Community.

Re: Wired Ethernet Connection Self-Assigned IP Issue

stu1720 — Mon, 10 Mar 2025 13:52:28 GMT

Yes, this is a Lennar Ruckus setup. The home included an ICX 7150-C12 switch and two R510 APs.

Re: Wired Ethernet Connection Self-Assigned IP Issue

Imran_ruckus — Mon, 10 Mar 2025 20:52:10 GMT

test

Re: Wired Ethernet Connection Self-Assigned IP Issue

Imran_ruckus — Mon, 10 Mar 2025 20:54:29 GMT

Hi @stu1720

Greetings!!!

Thank you for reaching out to the RUCKUS Lennar Home Community.

We appreciate your patience and understanding as we work to resolve the issues you are experiencing with your RUCKUS setup.

It sounds like you are encountering an issue where your MacBook Pro doesn't get a valid IP address when connected to a port that is part of the DEFAULT-VLAN (VLAN 1), but it works fine when connected to another VLAN (your "everyday use" VLAN). There are a few potential reasons for this issue, and I'll walk you through some troubleshooting steps to help resolve it:

1. VLAN 1 is untagged, but the switch port might not be configured correctly

Port configuration for VLAN 1: You've mentioned that port 1/1/4 is Untagged in the DEFAULT-VLAN (VLAN 1), which should allow it to work for the connected devices in VLAN 1. However, the configuration might not be fully correct or consistent across the switch.
Check VLAN Configuration on the Switch:
- Ensure that the DEFAULT-VLAN (VLAN 1) is active and correctly configured on the switch.
- Verify that VLAN 1 is indeed configured to allow communication on ports 1/1/4 and 1/1/7.
- Also, make sure the Edge Router 4 is assigning IP addresses correctly through DHCP for VLAN 1. If your Edge Router 4 is connected to a different VLAN for the DHCP pool (for example, if the router is not aware of VLAN 1), your MacBook Pro won’t be able to get an IP address.

2. DHCP Issue on the Edge Router 4 for VLAN 1

If your MacBook is self-assigning an IP address (169.254.x.x range), it indicates that it's not receiving an IP address from the DHCP server. Here’s what you need to check:

VLAN 1 on Edge Router 4: Verify that your Edge Router 4 has a DHCP server running for VLAN 1. If it's only running for another VLAN (such as the VLAN you use for "everyday use"), your MacBook will not be able to receive an IP address in VLAN 1.
- Log into your Edge Router 4 and verify that the DHCP settings for VLAN 1 are enabled. If DHCP isn't enabled, your devices connected to port 1/1/4 won’t get IP addresses and will resort to self-assigning.
VLAN Interface Setup: Ensure that the Edge Router 4 has a proper VLAN 1 interface and it's assigned an IP address that matches the network for that VLAN. For example, the router's interface for VLAN 1 should have an IP like 192.168.1.x if you're using that subnet.

3. Tagged vs. Untagged Configurations on Ports

Since port 1/1/4 is part of VLAN 1 (untagged), it's crucial to check if the switch's trunking and tagging setup is correct for other VLANs. When you move port 1/1/7 to VLAN 1, the same logic applies: the port must be correctly set to Untagged for VLAN 1, or the device won't get an IP.
Double-check how VLAN tagging is configured on all the ports, especially the ones connected to devices that should receive IP addresses via DHCP.

4. Check for Inter-VLAN Routing (If Applicable)

If you're using multiple VLANs and you want the Edge Router 4 to route between them (including routing traffic from VLAN 1 to the internet), ensure that Inter-VLAN routing is properly configured. If your router isn't routing between VLANs or if VLAN 1 traffic is blocked, devices on that VLAN won’t get access to the network.

5. Test with Static IP

As a test, try manually configuring your MacBook Pro with a static IP address in the same subnet as the router's VLAN 1 interface. This will help you verify if it's a DHCP issue specifically.
If static IP works but DHCP doesn’t, it further confirms that the issue is with the DHCP server configuration for VLAN 1.

6. Physical Connectivity

Ensure that the physical wiring of the port and the device is sound. If your MacBook Pro can connect to VLAN 1 wirelessly but not through the wired connection, there might be an issue with how the switch port (1/1/4) or wall port is wired.

Suggested Steps to Resolve:

1. Verify Edge Router 4 DHCP settings: Ensure that the DHCP server is running for VLAN 1 and correctly configured.

2. Check VLAN 1 interface: On the Edge Router 4, ensure the VLAN 1 interface has a valid IP address (for example, 192.168.1.x).

3. Double-check VLAN configuration on the ICX 7150: Verify that both ports 1/1/4 and 1/1/7 are configured correctly in their respective VLANs (untagged for VLAN 1).

4. Test static IP assignment on the MacBook to see if it can connect to the network manually.

5. Ensure Inter-VLAN routing is configured (if using multiple VLANs that need routing).

By following these steps, you should be able to pinpoint the issue and get your MacBook connected to the network correctly via the wired connection on VLAN 1. Let me know how it goes.

Additionally, could you please share the outputs of the mentioned commands?

enable

show vlan

show vlan 1

show vlan brief

show vlan ethernet 1/1/7

show running config vlan

Thank you again for your patience and understanding.

Best regards,

Imran Sanadi

RUCKUS Lennar Home Community.

Re: Wired Ethernet Connection Self-Assigned IP Issue

stu1720 — Tue, 11 Mar 2025 15:45:35 GMT

Thank you for your write up.

My router/switch/APs are all on the 192.168.1.0/24 range.

On my EdgeRouter, the 192.168.1.0/24 range is associated with the below interface:

DHCP is setup as follows:

On the ICX 7150-C12 switch, the VLAN is setup as follows:

I did attempt to manually assign an IP address to my MacBook within the range while connected to the wall ethernet port with no success.

In the past, this setup has allowed me to use the ethernet wall port in my home office to connect to the 192.168.1.0/24 range.

For what it is worth, I do have an WLAN/SSID setup that is tied to VLAN 1 and when I am on that wireless network, I can access the router/switch/APs browser based interfaces on the 192.168.1.0/24 range.

Is there a setting that needs to be changed to allow the wired option to work again?

Re: Wired Ethernet Connection Self-Assigned IP Issue

Imran_ruckus — Tue, 11 Mar 2025 16:44:01 GMT

Hi @stu1720

Greetings!!!

Thank you for your response and the detailed information.

Could you please share the output of the CLI commands mentioned in my previous response?

Thank you again.

Best regards,

Imran Sanadi

RUCKUS Lennar Home Community.

Re: Wired Ethernet Connection Self-Assigned IP Issue

stu1720 — Tue, 11 Mar 2025 17:15:42 GMT

I apologize for not doing that. Just to clarify, do you want the command line for the switch or router?

Re: Wired Ethernet Connection Self-Assigned IP Issue

Imran_ruckus — Tue, 11 Mar 2025 17:37:55 GMT

Hi @stu1720

Thank you for your response and the update.

Kindly provide the information from the RUCKUS Switch CLI.

Thank you once again.

Best regards,
Imran Sanadi
RUCKUS Lennar Home Community

Re: Wired Ethernet Connection Self-Assigned IP Issue

stu1720 — Wed, 12 Mar 2025 22:13:49 GMT

In running the requested switch CLI and reading through it, I realized that the untagged ports for the router and APs had been assigned to the wrong VLAN. Moving them back to 1:DEFAULT-VLAN solved my issue. I sincerely appreciate your help and effort in helping me to realize my error.

Re: Wired Ethernet Connection Self-Assigned IP Issue

Imran_ruckus — Thu, 13 Mar 2025 12:19:37 GMT

Hi @stu1720

Thank you for your response.

We are pleased to hear that the issue has been resolved and that you were able to find a solution.

We truly appreciate your time and patience throughout this process.

Thank you again for reaching out to RUCKUS Lennar Home Community.

Should you have any further questions or concerns, please do not hesitate to contact us.

Wishing you a wonderful day ahead!

Did I answer your queries? If yes, hit the Kudos buttons and also accept the answers as Accepted solutions.

Best regards,

Imran Sanadi

RUCKUS Lennar Home Community.