pfSense assigning two IP's to a single machine
-
Hello,
I am running a VLAN for IoT devices and recently acquired an ODroid that I want to be in this IP range, nonetheless it remains within the LAN range.
So far I have tried:
-
Assigning a static mapping within the DHCP server of the VLAN and rebooting, which results in the machine having two ip addresses but only being reachable in the LAN one (via ping).
-
Adding the mac address of this machine to the "deny" list on the LAN DHCP, but achieving the same results.
-
This is all going through a TP-Link TL-SG108PO switch, so I've tried to assign the specific port's untagged traffic to the specific VLAN while removing its membership from the other VLANs. Prior configuration had all ports on all VLANS via tagged traffic.
So far I have been unable to achieve the desired results.
Thanks in advance for any pointers.
-
-
@04CC40 You have a problem with your VLANs and switch, not pfSense.
-
@Bob-Dig
The switch mentioned does not appear to be L3 so we can only presume the VLANs and DHCP are managed via pfSense in a router-on-a-stick configuration.
️ -
@RobbieTT Even if, still it is most probably a problem with the switch-config.
-
@04CC40 said in pfSense assigning two IP's to a single machine:
ODroid
Confirm that this ODroid device is wired only?
The port on the switch should only have the desired VLAN set - nothing else.
The only port with both your LAN and VLAN(s) set should be the (trunk) port to the router.
️ -
@04CC40 said in pfSense assigning two IP's to a single machine:
TP-Link TL-SG108PO
Some TP-Link models have a problem with VLANs.
-
Can we assume the ODroid is not configured with the VLAN directly?
-
Solution: I had to set the tagging and PVID on different sections within the TP'Link GUI.
@JKnott This one has been running the same VLAN's for a while, so that was not the issue. Clearly a configuration error.
@RobbieTT Yes, wired only, direct to a specific port on the switch. I assumed setting the port as "untagged" would suffice, but an extra PVID definition was required.
@stephenw10 The ODroid wasn't configured at all at this point, simply booting and getting an IP from the DHCP server.
Thanks.
-
@04CC40
Good update.
