business_kid: Not quite. Let me do a better job of explaining my network ASCIIly...
=================== WALLS =================================
[Linux PC]-----[gigabit switch]-----[network printer]
(Note that asterisks indicate a wireless link; all other implied links are Ethernet.)
Incidentally, the "wifi router/AP" is typical router hardware (Linksys WRT54GL) but I am running atypical router firmware on it (Tomato). I'm not really doing anything complex with it, but it does run a DHCP server that statically assigns addresses.
What I'm essentially going for here is to have all of my computers/printer appear to be on the same 192.168.1.x network. Obviously, that's easy for the laptop and Linux PC: They just connect to the wifi router and get assigned an address. But what if I want to print from the laptop? Or if I want to access the Internet from the Windows PC? In both of these cases, the Linux PC needs to act as a bridge to those packets.
I have had this "kinda working" by using NAT before, but NAT imposes the following limitations:
1. The Windows PC and printer can't get their IP from the DHCP server (which is only reachable via wireless)
2. The Windows PC and laptop can't share files easily with SMB because they are on separate networks.
I know I can refine the NAT setup more by proper routing and using a DHCP relay agent and installing a WINS server, etc. ... But bridging just looks easier on paper.