Date: Tue, 3 Jul 2001 14:20:20 -0700 From: "Crist J. Clark" <cclark@globalstar.com> To: "Lavender, Ben" <LavenderB@nctldno.navy.mil> Cc: "'freebsd-questions@freebsd.org'" <freebsd-questions@freebsd.org> Subject: Re: interface aliases and routing Message-ID: <20010703142020.A55237@sec-tools.corp.globalstar.com> In-Reply-To: <78202F9B9BB8D311846100805F577DFF274096@nctams01.nctldno.navy.mil>; from LavenderB@nctldno.navy.mil on Tue, Jul 03, 2001 at 06:29:59AM -0500 References: <78202F9B9BB8D311846100805F577DFF274096@nctams01.nctldno.navy.mil>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 03, 2001 at 06:29:59AM -0500, Lavender, Ben wrote:
> > On Mon, Jul 02, 2001 at 10:28:44AM -0500, Lavender, Ben wrote:
> > > Like this?
> > > xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> > > inet6 fe80::210:5aff:fe28:ca1f%xl0 prefixlen 64 scopeid 0x1
> > > inet 164.229.1.72 netmask 0xffffffc0 broadcast 164.229.1.127
> > > inet 164.229.1.74 netmask 0xffffffff broadcast 164.229.1.74
> > > ether 00:10:5a:28:ca:1f
> > > media: autoselect (100baseTX <full-duplex>) status: active
> > > supported media: autoselect 100baseTX <full-duplex> 100baseTX
> > > 10baseT/UTP <full-duplex> 10baseT/UTP 100baseTX <hw-loopback>
> > >
> > > This didn't work.
> >
> > What does not work? In a setup like this, an outgoing connection will
> > use the 164.229.1.72 address unless the application explicitly
> > requests 164.229.1.74 as the source address. It should be able to use
> > that address if it wants. Incoming connections to the machine should
> > reply using whatever address the incoming packets came in on.
> >
> > What is not working?
>
> 164.229.1.74 does not have connectivity to machines outside the subnet.
> Using dig v9 to bind to the source address of 1.74 does not get me a
> response from a name server on another subnet. Pinging 164.229.1.74 from
> another subnet does not work, nor does any tcp service. However,
> connectivity to other machines on the same subnet (164.229.1.64-128) works
> just fine.
Sounds like the problem might not be at this machine, but rather at
the router. Run a,
# tcpdump -nvv host 164.229.1.74
And try,
$ telnet -s 164.229.1.74 <host on LAN>
$ ping -S 164.229.1.74 <host on LAN>
$ telnet -s 164.229.1.74 <host not on LAN>
$ ping -S 164.229.1.74 <host not on LAN>
Then try the reverse, that is, run the commands on the other hosts
and going to 164.229.1.74.
> Ive also got a sizeable portion of static routes to other gateways for other
> networks (speaking of which, I cant find how one might add a static route to
> rc.conf in /etc/defaults/rc.conf, I'm currently using a shell script. Any
> ideas on that one?).
man rc.conf
Example:
static_routes="route_1 route_2" # Use more meaningful names
route_route_1="net 10.10.0.0/16 164.229.1.125"
route_route_2="net 10.128.0.0/16 164.229.1.124"
> relevent rc.conf:
> network_interfaces="xl0 lo0"
> ifconfig_xl0="inet 164.229.1.72 up netmask 255.255.255.192"
> defaultrouter="164.229.1.66"
> ifconfig_xl0_alias0="inet 164.229.1.74 up netmask 255.255.255.192"
^^^
Still need to fix that.
--
Crist J. Clark Network Security Engineer
crist.clark@globalstar.com Globalstar, L.P.
(408) 933-4387 FAX: (408) 933-4926
The information contained in this e-mail message is confidential,
intended only for the use of the individual or entity named above. If
the reader of this e-mail is not the intended recipient, or the employee
or agent responsible to deliver it to the intended recipient, you are
hereby notified that any review, dissemination, distribution or copying
of this communication is strictly prohibited. If you have received this
e-mail in error, please contact postmaster@globalstar.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010703142020.A55237>