Date: Fri, 6 Jul 2001 16:26:22 -0500 From: "Mark Kobussen" <kobes@usermail.com> To: <freebsd-questions@freebsd.org> Subject: Re: IPFW/NATD or Cable Modem Trouble?? Message-ID: <001201c10662$6043c3e0$0201a8c0@goldenrod.net>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
------=_NextPart_000_000F_01C10638.6539B320
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
> natd_flags=3D"-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
------=_NextPart_000_000F_01C10638.6539B320
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4616.200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2><BR></FONT><FONT size=3D3>> natd_flags=3D"-l -d =
-s -m -u=20
-dynamic -ned2"<BR>><BR><BR>I added the flags you recommended above, =
and=20
altogether, it seems to work a<BR>bit better. Unfortunately, the =
router=20
still becomes unreachable every few<BR>minutes.<BR><BR>This leads me to =
another=20
question -- why, if my configuration looks fairly<BR>decent, would not =
only the=20
ed2 interface stop communicating with the cable<BR>modem, but ed1 ALSO =
stops=20
responding to telnet and ssh sessions.<BR><BR>Also, I noticed some "ed2 =
NIC=20
memory corrupt - invalid packet size" messages<BR>on the console last =
time I=20
looked. It seems these JUST started appearing<BR>after I added =
various=20
NATD flags.<BR><BR>><BR>> I also added the following to let DHCP=20
through<BR>> # Allow DHCP=20
through<BR>> ${fwcmd} add pass udp from any =
68 to any=20
67 out via ${oif}<BR>> ${fwcmd} add pass udp =
from any=20
67 to any 68 in via ${oif}<BR><BR>Added these two, seems to be =
working=20
a-ok.<BR><BR>> And, do you have the following in=20
/etc/dhclient.conf:<BR>><BR>> interface "ed2"=20
{<BR>> send host-name =
"<your isp provided hostname=20
here>";<BR>> =
request=20
subnet-mask, broadcast-address, routers,\<BR>> domain-name-servers,=20
domain-name,=20
time-servers;<BR>> =
require=20
domain-name-servers;<BR>> &nb=
sp;=20
}<BR>><BR><BR>I added the above to my dhclient.conf file, and DHCP =
stopped=20
receiving<BR>domain resolution information. I've left the =
dhclient.conf=20
empty (as it was<BR>before), as it was not only working fine, but also =
providing=20
all of the<BR>information you were requesting in your=20
dhclient.conf.<BR><BR>Thanks for the=20
suggestions,<BR>Mark</FONT></DIV></BODY></HTML>
------=_NextPart_000_000F_01C10638.6539B320--
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?001201c10662$6043c3e0$0201a8c0>