Thank you for the responses. Basically you have to do tagging of packets for something like this to work. I wasn't sure if with all the changes in Fire Engine if maybe this was possible now. it isn't, at least not in any practical sense that I would implement. On 7/26/07, Chris <kingsqueak@gmail.com> wrote: > First, this network is badly broken, that much I already know...however. > > Seeing if there is a host based solution for my Sol 10 host "Server A". > > Two hosts > > Server A > ce0 is on 192.168.0.2 > ce1 is on 172.16.0.2 > > Client B > eth0 is on 192.168.0.5 > > Connect from Client B to 172.16.0.2 on Server A, the routing permits > this, the traffic arrives inbound but the replies are via Server A's > default router via the ce0 interface. > > Is there any way to pin the routing based on its source rather than > the default based on destination? Meaning if the packet originates on > the ce1 interface, so too should the replies go back out that > interface. _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Fri Jul 27 16:04:38 2007
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:44:06 EST