Replies: 3 comments
-
You goal is fine and doable. There is a major big issue in your configs on your switch configuration. The main point is that eth0-eth3 are not distinct adapters but they are DSA mappings to RJ45 switch ports. Not sure if the official Openwrt DSA drivers (not available in tch firmwares) behave differently, but here with your current config the host connected to RJ45 LAN port mapped to eth3 is able to send packets to every other host connected on other switch ports since they all belong to the same VLAN. All you said so far in configs is that packets arriving at the switch from that RJ45 port and exiting the switch from the CPU port and showing up into eth3 device will be considered as being related to lan2 interface. You need to enable VLAN on the switch and set the first three ports as part of a different VLAN then the fourth. AFAIR you must set the switch to tag packets going to the CPU even if DSA is used. But that never had much sense to me (maybe DSA driver limitation/bug by bcm? ). |
Beta Was this translation helpful? Give feedback.
-
So does that mean I need to do something like the answer in this post: |
Beta Was this translation helpful? Give feedback.
-
I have tried the config below, and it is worse than before: the DHCPDISCOVER doesn't reach dnsmasq at all. At least the other way it was just the return DHCPOFFER that was lost. EDIT: I have added a new switch stanza as follows:
and changed the device options in the switch_vlan stanzas to match, and the DHCPDISCOVER messages now arrive and the DHCPOFFER gets sent, but it still doesn't arrive back at the requesting client. The VLAN configuration has made no difference at all.
|
Beta Was this translation helpful? Give feedback.
-
I am trying to move a single LAN port (in this case eth3) to a different subnet, similar to the way that the Guest Wi-Fi runs on a different subnet.
The problem I am encountering is that there seems to be a routing issue. I can see from the logs that the router receives the DHCPREQUEST and sends the DHCPOFFER, but it never arrives back at the client. I have used iptables TRACE to ensure that it is not being blocked by a firewall rule.
I applied the changes by duplicating what the Guest network does.
Here are my config files:
/etc/config/network:
/etc/config/dhcp
To simplify the firewall settings, I just added the new
lan2
interface to the Guest1 firewall zone, as that does what I want:Output of various commands:
I am hoping I have just missed something simple...
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions