I really don’t understand what you beleive you will acomplish with this scheme, but…
IPs from within the same subnet CANNOT be used on distinct interfaces, the router will not have any way to determine the proper egress interface. Proxy arp will not get around that. Not only is it a bad idea, it simply won’t work without some byzantine hackery.
Never the less, here are a couple of byzantine hacks you could try if you are determined to set it up similar to what you describe… (not recomended)
You could split the subnet on the MT (i.e. if it is a /23 cut it into 2 /24s), and use one on each interface, and enable proxy arp on both interfaces. Then, so long as you keep the machines on either side within the appropriate /24, and configure them with a /23 netmask, they should be able to reach you. This is about the closest sort of semi-functional setup I can imagine to what you describe.
Another bad, but perhaps semi-workable, way would be to setup /32 addresses on the MT for every device on the two networks, assigned to the appropriate interface, and enable proxy arp on each interface.
But, rather than trying to come up with a bizzare way to re-invent the wheel, why not set things up “right”.
If you want to segment the network, then you should do it the normal routing way; as small as the setup appears to be, static routes would probably be easiest . If you don’t want to setup static routes on your routers, then explore OSPF, or even RIP.
If you only want to filter, then bridge the interfaces, and use the firewall.
Both of the above could probably be easily done on the MTs doing the radio link, without much extra load. If your main router is a 3640, and it is doing NAT (a very costly operation on Ciscos, especially small ones like the 3600 series), then I suspect you don’t move enough traffic to strain the procs on your existing MTs.
I don’t mean to sound condecending, and I wish you success. But with such an apparently simple network, I don’t understand why you are trying such an unusual approach.
Good luck,
–Eric