Date: Sat, 7 Jul 2001 23:12:31 -0400 From: Louis LeBlanc <leblanc+freebsd@acadia.ne.mediaone.net> To: freebsd-questions@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: IPFW/NATD or Cable Modem Trouble?? Message-ID: <20010707231231.A22041@acadia.ne.mediaone.net> In-Reply-To: <001201c10662$6043c3e0$0201a8c0@goldenrod.net> References: <001201c10662$6043c3e0$0201a8c0@goldenrod.net>
next in thread | previous in thread | raw e-mail | index | archive | help
No where near being a FreeBSD or network guru, but it seems to me that
if the gateway for your ed2 interface goes down, and you are trying to
telnet to the IP (or a hostname associated with the IP) of the ed2
interface, it *will* route through the ed1 interface to ed2, but ed2
will have to be able to reach its gateway (the router that cannot be
reached) in order to accept any connections. If you telnet to a
hostname or the IP associated with ed1, it should be fine.
Keep in mind, I am assuming you are connecting from within your
network (ed1 side) to your 'gateway' (connecting your internal network
to the cable modem), but actually telnetting to the gateway (ed2)
interface.
To my understanding, this is normal behavior. I have seen it before
on various unices. I doubt NAT will change this behavior either.
HTH
Lou
On 07/06/01 04:26 PM, Mark Kobussen sat at the `puter and typed:
>
> > natd_flags="-l -d -s -m -u -dynamic -ned2"
> >
> I added the flags you recommended above, and altogether, it seems to
> work a
> bit better. Unfortunately, the router still becomes unreachable every
> few
> minutes.
> This leads me to another question -- why, if my configuration looks
> fairly
> decent, would not only the ed2 interface stop communicating with the
> cable
> modem, but ed1 ALSO stops responding to telnet and ssh sessions.
> Also, I noticed some "ed2 NIC memory corrupt - invalid packet size"
> messages
> on the console last time I looked. It seems these JUST started
> appearing
> after I added various NATD flags.
> >
> > I also added the following to let DHCP through
> > # Allow DHCP through
> > ${fwcmd} add pass udp from any 68 to any 67 out via ${oif}
> > ${fwcmd} add pass udp from any 67 to any 68 in via ${oif}
> Added these two, seems to be working a-ok.
> > And, do you have the following in /etc/dhclient.conf:
> >
> > interface "ed2" {
> > send host-name "<your isp provided hostname here>";
> > request subnet-mask, broadcast-address, routers,\
> > domain-name-servers, domain-name, time-servers;
> > require domain-name-servers;
> > }
> >
> I added the above to my dhclient.conf file, and DHCP stopped receiving
> domain resolution information. I've left the dhclient.conf empty (as
> it was
> before), as it was not only working fine, but also providing all of
> the
> information you were requesting in your dhclient.conf.
> Thanks for the suggestions,
> Mark
--
Louis LeBlanc
Fully Funded Hobbyist, KeySlapper Extrordinaire :)
leblanc@acadia.ne.mediaone.net
http://acadia.ne.mediaone.net ԿԬ
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?20010707231231.A22041>