Sorry for long message but I try to explain better:
the scenario I would like to implement is:
internet/intranet ----+
+--------------+ |
| PC with | +-----------+
| connectivity |----------------------| switch |
| manager | +-----------+
+--------------+ | | |
| | |
| | |
+------------+ +------------+ | | |
| PC guest 1 |----------| embedded |------+ | |
+------------+ eth1 | linux BOX 1| eth0 | |
+------------+ | |
| |
+------------+ +------------+ | |
| PC guest 2 |----------| embedded |--------+ |
+------------+ eth1 | linux BOX 2| eth0 |
+------------+ |
|
Others PC guest & BOX --+
The embedded linux box have software like web browser, multimedia player
working in internet/intranet through static configuration of eth0 with a
pool of 10.x.x.x Ip addresses. When I connect a generic PC guest on eth1
all the layer2 traffic tagged to a vlanX need to be "sniffed" from the
"connectivity manager PC" This PC take charge to detect the guest PC
operating system and it's needs for connecting to internet, give to that
PC the requested infos and the PC start to navigate.
Actually this is already working in this scenario:
internet/intranet ----+
+--------------+ |
| PC with | vlan2-vlanX +-----------+
| connectivity |----------------------| switch |
| manager | +-----------+
+--------------+ | | | |
+------------+ vlan2 | | | |
| PC guest 1 |--------------------------+ | | |
+------------+ | | |
+------------+ vlan3 | | |
| PC guest 2 |----------------------------+ | |
+------------+ vlanX | |
Others PC guest & BOX -----------------+ |
|
+-----------+
| switch |
+-----------+
+-------------+ | | |
| embedded |-------------------------+ | |
| linux BOX 1 | eth0 | |
+-------------+ | |
+-------------+ | |
| embedded |---------------------------+ |
| linux BOX 2 | eth0 |
+-------------+ |
Others Linux BOX -------+
I would like to half the expenses for the cat5 wiring, switches, etc.
The cost for adding eth1 to our board is very low, if needed i have the
chance to develop a software/device driver on our linux BOX, but I
Prefere (if possible) to do the job in a "standard" linux way. The
critical point for me is the "not configuration" of eth1, in effect I
don?t' have a specific ip address but need all layer2 traffic...
Pierantonio.
> -----Messaggio originale-----
> Da: vlan-bounces@xxxxxxxxxxxxxxx
> [mailto:vlan-bounces@xxxxxxxxxxxxxxx] Per conto di Peter Stuge
> Inviato: venerd? 2 settembre 2005 9.51
> A: vlan@xxxxxxxxxxxxxxx
> Oggetto: Re: [VLAN] vlan with two interfaces
>
>
> On Thu, Sep 01, 2005 at 02:13:28PM +0200, Tabaro Toni wrote:
> > It's feasible only with linux vlan or i need more like for example
> > linux bridge?
>
> If all traffic is on top if IP and you only need routing,
> just VLANs and IP forwarding will be enough.
>
> If you need a clean layer 2 network you have to use bridging.
>
>
> > There is a FAQ about that?
>
> Perhaps http://marc.theaimsgroup.com/?m=105098558615614 can help?
>
> If you want dhcpd, you have to set the REORDER_HDR flag on
> all appropriate VLANs before starting it.
>
>
> //Peter
> _______________________________________________
> Vlan mailing list
> Vlan@xxxxxxxxxxxxxxx http://www.lanforge.com/mailman/listinfo/vlan
>
>
> -----Messaggio originale-----
> Da: vlan-bounces@xxxxxxxxxxxxxxx
> [mailto:vlan-bounces@xxxxxxxxxxxxxxx] Per conto di Peter Stuge
> Inviato: venerd? 2 settembre 2005 9.51
> A: vlan@xxxxxxxxxxxxxxx
> Oggetto: Re: [VLAN] vlan with two interfaces
>
>
> On Thu, Sep 01, 2005 at 02:13:28PM +0200, Tabaro Toni wrote:
> > It's feasible only with linux vlan or i need more like for example
> > linux bridge?
>
> If all traffic is on top if IP and you only need routing,
> just VLANs and IP forwarding will be enough.
>
> If you need a clean layer 2 network you have to use bridging.
>
>
> > There is a FAQ about that?
>
> Perhaps http://marc.theaimsgroup.com/?m=105098558615614 can help?
>
> If you want dhcpd, you have to set the REORDER_HDR flag on
> all appropriate VLANs before starting it.
>
>
> //Peter
> _______________________________________________
> Vlan mailing list
> Vlan@xxxxxxxxxxxxxxx http://www.lanforge.com/mailman/listinfo/vlan
>
>
