Problem regarding Bridging, MTU, Masquerading 802.1q VLANs on SuSE 9.0

Hi,

currently I am setting up a quite unusual configuration.

A SuSE Linux Box with 2 3C905-X NICs follows shall get tow
tagged VLANS on one NIC, masq the second network behind a
single IP of the first Network (Layer 3 Networks match the
Layer 2 Networks), and bridge only one of the VLANs to the
second NIC.

VLAN/Vconfig-tools are installes, the two VLANs on eth0 are
up. I will have to patch the drivers for the 3C905-X Cards
to support MTUs of 1504 Bytes.

Questions to the group:
- Looking into the patch code, I doubt if I could configure
the NICs with MTU=1504 on eth0 and MTU=1500 on eth1. Any
Experiences here?

- Is ist possible to bridge a tagged VLAN to a native
eth1 with the packets appearing untagged on eth1?

- I would prefer bridging the first tagged vlan on eth0
to the same tagged vlan on eth1. This leads to vlan per NIC
instead of VLAN per kernel and this leads to a conflict to
the SuSE configuration abstractions, so I will to have to
patch suseconfig scripts, conventions and eventually
structure. Any Experiences here?

Subnet x
VLAN x
| | | SuSE 9.0 Win NT
-------+ VLANx +-----------+ Subnet x +--------+
HP2524 |-------------| Router |----VLANx----| Server |
-------+ VLANy +-----------+ +--------+
| | | masqu'ing Subnet y
VLAN y
Subnet y


The first concept was to use the windows NT Server to mask
one net behind an IP of the other net. As Windowss NT is
unable to do this by concept (AFAIK) and an update to Win2k
cannot be done for about the next 12 Months, and because all
switchports and outlets are used, I have to insert the
routing box between the switch and the server.

I do not want to insert an additional switch between the
server, connecting the HP2524, the routing box and the
server, I want the Linux Box to do the bridging.

After the upgrade to W2k the Win Box could do the masking
and the router could be removed without having to reconfigure
the HP2524.

Regards

Michael
--
In Planung