In
Box -------- | IP: 192.168.123.4 NIC1: +-----------------------[ bound to specific ip for email ] | IP: 192.168.123.0 | NM: 255.255.255.0 | | 192.168.124.3/24 NIC2: +----------------------[ bound to specific ip for edir] IP:........ | IP: 192.168.124.0 | \ | NM: 255.255.255.0 | \ -------- | ------[client2]IP:........192.168.123.247 [client 3] IP:.........
I've been following the thread loosely, and I still have no frackin' idea what you are trying to achieve. Also, 1. 192.168.123.0 is not a valid IP under a 255.255.255.0 netmask. 2. 192.168.124.0 is not a valid IP under a 255.255.255.0 netmask. We appear to have 3 systems involved. oS (2 nics), the client (1 nic?), and the server (who knows?). What is the server IP? Why is the client sending packets through oS? Is oS playing the role of a router here? If so, have you correctly set that up that routing via (IIRC) the SuSEFirewall yast2 module? Does the server know that 192.168.123.0/24 is accessed via oS? If not, you'll probably need to do NAT. If so, you really just need to make sure oS knows to turn ip_forwarding on and either not firewall or poke enough holes through the firewall. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/