On 4/2/09 11:40 AM, "Boyd Stephen Smith Jr."
In
, Chris Arnold wrote: 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. 2 systems oS (2 nics), the client (1 nic?) Yes, I nic , and the server (who knows?). What is the server IP? 192.168.123.x and 192.168.124.x Why is the client sending packets through oS? Email and edir resons Is oS playing the role of a router here? No If so, have you correctly set that up that routing via (IIRC) the SuSEFirewall yast2 module? Suse firewall is off 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. Holes already exist on the firewall. This has been working in the past, up until I added a 2nd nic so I could bind edir to it.
What I do know is when I add 192.168.123.0 and gw of 192.168.123.x and the subnet in yast->routing, email starts working again and other stuff stops working. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org