The guest interface, from the doc, can be configured this way
uci set network.guest="interface"
uci set network.guest.type="bridge"
uci set network.guest.proto="static"
uci set network.guest.ipaddr="192.168.3.1"
uci set network.guest.netmask="255.255.255.0"
I have 2 (naive) questions:
Why does the guest config not include an ifname? In my mind, it needs to have an ifname, so that the interface can actually be applied to a physical port. I would expect to set it to the wifi port. Why is it not present in the doc?
ip6assign is not present in the guest config. What is the impact of that? Does it mean the guest network will not support ipv6?
Yes, I want it wireless only. Is it not necessary to add the ifname in that case?
In what part of the config can I do that? What issue can arise if I don't do it? (I do not have a need for IPv6, so I'd prefer not enable it, simply to keep the config as simple as possible).
@slh sorry to ask again, but I feel I am missing something. I am quite happy not to have IPv6. It seems IPv6 only makes things marginally faster right now. But from your comment, I feel I might be missing something more.
I am tempted to remove "ip6assign" on all my network interfaces, including the lan, so that they only respond to IPv4. That way, I feel I can avoid the additional complexity of IPv6. Is that a reasonable thing to do? Can I also remove the wan6 interface?
There are IPv6-only services, so IPv6 connectivity is required to access them.
Even if it is not apparent now, it will definitely be in the foreseeable future.
It also increases the fault tolerance of services operating in dual-stack mode.