OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: Pushing mail through a certain interface.

From: Andrew (jasari_iyahoo.com)
Date: Mon Dec 13 2004 - 15:22:48 CST

So do you think I need to so some subnetting? When you
say unroutable outside their address block do you mean
192.168.1.0/24 is not routable between and
192.168.2.0/24 too? I'm assuming that is the case too.

Thanks

--- Michael McDaniel <pfautosys.us> wrote:

> On Mon, Dec 13, 2004 at 09:11:06AM -0800, Andrew
> wrote:
> > No I'm not trying to connect to the internet, I'm
> > trying to connect to the back of another
> multihomed
> > machine. At present email is received on
> 192.168.2.201
> > and then sent to 192.168.1.12. Instead I want to
> > receive email on 192.168.2.201 then push it to
> > 10.0.0.2.
> >
> > Thanks
> >
> >
> > --- Michael McDaniel <pfautosys.us> wrote:
> >
> > > On Mon, Dec 13, 2004 at 08:54:26AM -0800, Andrew
> > > wrote:
> > > > I have two network cards in a machine,
> > > > 192.168.2.201/24, the other
> > > > 10.0.0.1/24. I want to receve mail on
> > > 192.168.2.201/24
> > > > and push it to 10.0.0.2 using
> "smtp_bind_address"
> > > But
> > > > I haven't got that far.
> > > >
> > > > When only the 192.168.2.201/24 is active I can
> > > access
> > > > the
> > > > postfix running on it from any other machine,
> > > postfix
> > > > is set to listen on all interfaces at the
> moment.
> > > The
> > > > second I switch the
> > > > 10.0.0.2 one on, nothing from either. I can't
> > > connect
> > > > to any services, postfix, apache anything. I
> can
> > > get
> > > > out of the machine, ping and view websites but
> > > nothing
> > > > seems to able to get in.
> > > > I can ping 10.0.0.2 from the machine fine.
> > > >
> > > > The firewall is off and the the only thing I
> > > change is
> > > > whether or not the second card is enabled.
> > > >
> > > > What do I need to do? Is it something to do
> with
> > > > routing?
> > > >
> > > > My routing table looks like this:
> > > >
> > > > 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth1
> > > > 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth0
> > > > 169.254.0.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth1
> > > > 0.0.0.0 0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0
> 0
> > > eth1
> > > <znip>
> > >
> >
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > google for: unrouteable IP 10.0.0.0
> > >
> > > I infer from your information you are trying to
> > > connect to the Internet with
> > > a private address block (i.e. 10.0.0.0). See
> also
> > > RFC1918.
> > >
> > > Michael McDaniel
> > > Portland, Oregon, USA
> > > http://autosys.us
> > >
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> DISCLAIMER: I did not research, the following is
> from
> memory...
>
> I think 192.168 and 10. nets are unrouteable outside
> of their
> address block (even on an internal network), and
> that is
> causing you a problem.
>
> Apologies if this is totally off track.
>
> ~Michael
>
>
>

                
__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com