FTP problem with bridged interfaces

[Tsuroerusu]

I have my LAN interface bridged to OPT1 (And OPT1 is of course bridged to the LAN), which I have named LAN2, so that I in theory have two LAN ports. The reason for this is I have both a gigabit switch and a regular 10/100 switch, and this way I save a port on the 10/100 switch, by not using one for uplink to the gigabit switch.

The following connection paths works fine.
Workstation –> Gigabit switch --> LAN –> ftp.freebsd.org
Laptop --> 10/100 switch --> LAN2 –> ftp.freebsd.org

In other words, I can connect to FTP servers on the Internet (Eg. ftp.freebsd.org) from machines connected to both interfaces without problems.

However, I can't connect to an FTP server on one switch from a machine on the other switch. For example, my Xbox (Which has FTP access) is connected to my 10/100 switch, but I can't connect to it from my workstation which is connected to the gigabit switch.

The weirdest part is that port 21 feels like a black hole, I can ping the Xbox without issue, Samba works fine (But slow as usual when dealing with it on an Xbox), if I try telnet'ing to port 22 then I get connection refused, but if I try telnet'ing to port 21, it's like I tried telnetting to a server on the Internet on port 25 which my ISP blocks and it seems like a blackhole, it just hangs.

Does anybody have any ideas as to why FTP doesn't like crossing bridges?  ;D

Edit: After bridging the interfaces, I duplicated the default "LAN -> any" rule for LAN2.

[tommyboy180]

I apologize,
I do not have a solution to your problem but I do offer a work around. Why don't you connect the two switches together and have just one LAN. I understand that you are trying to save a port on your switch however such a model is a bad practice.
I would recommend connecting the switches.