pCP does VLANs but only after boot. You'll get multiple interfaces.
There is no VLAN "bootcode" and I am pretty sure pCP would be upset if
you'd nuke the native interface.
If you want to completely remove a pCP machine from the native network
and make it live only within the VLAN, I think the
>From the IP stack POV there's no difference between separate network
devices, IP aliases and VLANs. If they are local it will respond to
packets on them.
That does however mean you either have to feed the Pi a trunked
connection or all your LAN segments are carried on the same physical
In my experience LMS will listen on all IP addresses unless you direct
it to do otherwise. I'm not certain if that would be the same as
listening on all network interfaces.
In any case, it should be very simple to test.
Ah - interesting - not a straight no then. So, as to why I
have 3 subnets on my home LAN. The LMS is in 192.168.3.x, whereas most
of the clients are on 192.168.1.x and there's various bits on 2.x. 1.x
and 2.x can both see 3.x, but 1.x can't see 2.x. So, I can specify the
ip of the
It doesn't choose which interface to listen on unless you deliberately
lock it down to do so with a firewall rule. 99.9% of programs will just
open a listener socket without specifying. If you do that, you listen to
all local interfaces.
-Transcoded from Matt's brain by Tapatalk-
--
psketch wrote:
> I think I know the answer to this one anyway, but ... is there a way to
> make LMS listen on multiple network interfaces - either physical or
> virtual. Seems not, but just wondered if there was a clever plugin out
> there or the like.
>
> Ta
>
> Pete S
Well depends of
I think I know the answer to this one anyway, but ... is there a way to
make LMS listen on multiple network interfaces - either physical or
virtual. Seems not, but just wondered if there was a clever plugin out
there or the like.
Ta
Pete S
