Topography and bridging question

TIA for any thoughts on this, it's NOT my day job

I'm the "technology dad" for a small school. Current setup is about 40
clients on a Server 2003 domain with a Cable Modem/router internet
connection. Call this "A" for the sake of the discussion. All addresses on
this network are 192.168.1.xxx

The new hitch is a separate network, (call it "B") with 3 wired clients and
one wireless, that I need to allow to share A's internet connection. B came
about without my knowledge or input. They currently have a Belkin F5D7231-4.
Belkin stuff likes to use 192.168.2.xxx addresses, which should work out
just fine. I don't need or want A clients to be able to see B, and vice
versa.

Here's my thought process on how to get this done with the least pain and
money, unless someone else has a better idea.

Get another Belkin F5D7231-4.

Set up the one that's wired to "B" as an access point, in bridge mode. (Call
this 1 for being brief) I know this is gonna toast DCHP (and when you set a
belkin to access point, it likes to go to 2.254 anyway), so after setting 1
as access point disconnect it from B, wire second belkin into B temporarily
and 3 finger salute.

Set up second belkin (call it 2) in bridge mode, as router, with DHCP still
up. Obviously setting same SSID and security, the usual measures, on both
sides of bridge.

Unhook 2 (set as router) from B.

Reconnect 1 to B

Hook 2's WAN port up to A's existing router.

Should be good to go ... or not???

I'm aware that this setup is not ideal network-wise from B's perspective, as
it will run all of B's network traffic over the wireless bridge ... but B's
network traffic will be limited to a few print jobs and an occasional file
transfer, B was primarily set up to share printer and internet connections,
although how they expected it to access the internet ... I have NO clue.

Comments/suggestions will be appreciated