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
[-- Attachment #1 --]
> 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
[-- Attachment #2 --]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4616.200" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2><BR></FONT><FONT size=3>> natd_flags="-l -d -s -m -u
-dynamic -ned2"<BR>><BR><BR>I added the flags you recommended above, and
altogether, it seems to work a<BR>bit better. Unfortunately, the router
still becomes unreachable every few<BR>minutes.<BR><BR>This leads me to another
question -- why, if my configuration looks fairly<BR>decent, would not only the
ed2 interface stop communicating with the cable<BR>modem, but ed1 ALSO stops
responding to telnet and ssh sessions.<BR><BR>Also, I noticed some "ed2 NIC
memory corrupt - invalid packet size" messages<BR>on the console last time I
looked. It seems these JUST started appearing<BR>after I added various
NATD flags.<BR><BR>><BR>> I also added the following to let DHCP
through<BR>> # Allow DHCP
through<BR>> ${fwcmd} add pass udp from any 68 to any
67 out via ${oif}<BR>> ${fwcmd} add pass udp from any
67 to any 68 in via ${oif}<BR><BR>Added these two, seems to be working
a-ok.<BR><BR>> And, do you have the following in
/etc/dhclient.conf:<BR>><BR>> interface "ed2"
{<BR>> send host-name
"<your isp provided hostname
here>";<BR>> request
subnet-mask, broadcast-address, routers,\<BR>> domain-name-servers,
domain-name,
time-servers;<BR>> require
domain-name-servers;<BR>>
}<BR>><BR><BR>I added the above to my dhclient.conf file, and DHCP stopped
receiving<BR>domain resolution information. I've left the dhclient.conf
empty (as it was<BR>before), as it was not only working fine, but also providing
all of the<BR>information you were requesting in your
dhclient.conf.<BR><BR>Thanks for the
suggestions,<BR>Mark</FONT></DIV></BODY></HTML>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001201c10662$6043c3e0$0201a8c0>