MSGID: <10karg2$kfs6$1@dont-email.me> b91b1f0d
REPLY: <10kaqbp$csiv$1@dont-email.me> 4f478b44
PID: PyGate 1.5.2
TID: PyGate/Linux 1.5.2
CHRS: CP1252 2
TZUTC: 0000
REPLYADDR jrwalliker@gmail.com
REPLYTO 3:633/10 UUCP
On 15/01/2026 13:33, Pancho wrote:
> On 1/14/26 21:13, Lawrence D?Oliveiro wrote:
>> On Wed, 14 Jan 2026 17:57:35 +0000, John R Walliker wrote:
>>
>>> Some routers will let you use the source mac address in routing rules
>>> which nicely overcomes the problem with varying IPv6 addresses.
>>
>> That could also be handled with a VLAN.
> 
> If your network hardware handles VLAN tags.
> 
> I have numerous switches (unmanaged) and WiFi access points, none of the 
> ones I tested were compatible with VLAN tags (i.e. The network device 
> stripped the VLAN tag off packets rather than dumbly passed the packet 
> through with VLAN tag intact).
> 
> VLANs also aren't ideal as you may wish to implement policy routing on a 
> protocol (e.g. VoIP) or WAN destination, not just upon a LAN host.

There does seem to be a lot of variation in how different switches
behave.  The HP 1820 and 1810 series web managed switches along with
a variety of Netgear web managed switches all propagate vlan tags in
their default state.
They can can be configured to detag vlans on specific ports if
necessary.
I have some Allied Telesis managed switches that block vlans by default.

John


--- PyGate Linux v1.5.2
 * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
SEEN-BY: 105/81 106/201 128/187 129/14 305 153/7715 154/110 218/700
SEEN-BY: 226/30 227/114 229/110 112 134 200 206 275 300 317 400 426
SEEN-BY: 229/428 470 616 664 700 705 266/512 291/111 292/854 320/219
SEEN-BY: 322/757 342/200 396/45 460/58 633/10 280 414 418 420 422
SEEN-BY: 633/509 2744 712/848 770/1 902/26 2320/105 5020/400 5075/35
PATH: 633/10 280 229/426