Hey all:
I wrote the list a while back about the Motorola Surfboard 4101 cable
modem. I booted up using a vanilla Dachstein RC2 floppy ( a little old,
I know) and everything on the firewall seems fine:
I get an IP and DNS servers, and I can ping yahoo.com from the firewall.
No changes to the va
On Monday 22 July 2002 17:53, Richard W. Tibbs wrote:
> Is there a trick to turning on the DNS service in Dachstein?
In /etc/network.conf, set the CONFIG_DNS=NO and point your
LAN computers to use 192.168.1.254 as their DNS server.
--
~Lynn Avants
aka Guitarlynn
guitarlynn at users.sourceforg
CONFIG_DNS = NO
is already set in lrcfg (network.conf)
and via DHCP, the lan computers get 192.168.1.254 as the DNS server.
(there is no seconday, however.)
I checked these things --- that is why I am stumped.
>>RWT
guitarlynn wrote:
>On Monday 22 July 2002 17:53, Richard W. Tibbs wrote:
>
>>
Yes, the firewall resolves fine, and the windoze machines get a DNS
address of 192.168.1.254 via DHCP from the firewall.
Still stumped
>>RWT
Erich Titl wrote:
> At 00:53 23.07.2002, you wrote:
>
>> Hey all:
>> I wrote the list a while back about the Motorola Surfboard 4101 cable
>> mode
> CONFIG_DNS = NO
> is already set in lrcfg (network.conf)
> and via DHCP, the lan computers get 192.168.1.254 as the DNS server.
> (there is no seconday, however.)
>
> I checked these things --- that is why I am stumped.
If DNSCache is running, you should be getting DNS service to your local
wor
> Yes, the firewall resolves fine, and the windoze machines get a DNS
> address of 192.168.1.254 via DHCP from the firewall.
> Still stumped
> >>RWT
Hmm...what are the contents of /etc/resolv.conf on the firewall? Is it
using DNSCache for resolving, or the ISP's name-servers?
Charles Stein
Hi
At 16:06 23.07.2002, you wrote:
>Yes, the firewall resolves fine, and the windoze machines get a DNS
>address of 192.168.1.254 via DHCP from the firewall.
>Still stumped
Ok how did you set your dnscache parameters
lrcfg -> package settings -> dnscache.
1) LRP box intern
/etc/resolv.conf contains:
search cablenet-va.com /* correct, this is the DNS suffix that
shows up when I connect windoze directly to cable modem*/
IP filters:firewall[IP Forwarding: ENABLED]
meserver 208.197.246.194 /* correct, this is second DNS server that
windoze gets via direct c
OK, via lrcfg -> package settings -> dnscache,
I get options
1) Main Configuration File
2) Startup Script
Under Main Conf. FIle, I am presented with /etc/dnscache.conf, which
contains (sans comments)
ROOT=/etc/dnscache/root
IP = 0.0.0.0
IPSEND=24.yyy.xxx.56 /* latest external IP via the cable m
woops, /etc/dnscache.conf also contains the line
CACHESIZE=100
Erich Titl wrote:
> Hi
>
> At 16:06 23.07.2002, you wrote:
>
>> Yes, the firewall resolves fine, and the windoze machines get a DNS
>> address of 192.168.1.254 via DHCP from the firewall.
>> Still stumped
>
>
> Ok how did yo
See responses in-line
Charles Steinkuehler wrote:
>>CONFIG_DNS = NO
>>is already set in lrcfg (network.conf)
>>and via DHCP, the lan computers get 192.168.1.254 as the DNS server.
>>(there is no seconday, however.)
>>
>>I checked these things --- that is why I am stumped.
>>
>
>If DNSCache is ru
> /etc/resolv.conf contains:
>
> search cablenet-va.com /* correct, this is the DNS suffix that
> shows up when I connect windoze directly to cable modem*/
> IP filters:firewall[IP Forwarding: ENABLED]
> meserver 208.197.246.194 /* correct, this is second DNS server that
> windoze gets v
This _is_ your problem.
"Dr. Richard W. Tibbs" wrote:
>
> /etc/resolv.conf contains:
>
> search cablenet-va.com /* correct, this is the DNS suffix that
> shows up when I connect windoze directly to cable modem*/
> IP filters:firewall[IP Forwarding: ENABLED]
> meserver 208.197.246.194
Hi
Michael D. Schleif wrote the following at 19:18 23.07.2002:
>Removing comments, please, verify that this is actually the exhaustive
>content of your /etc/resolv.conf:
>
> search cablenet-va.com
> IP filters:firewall[IP Forwarding: ENABLED]
> meserver 208.197.246.194
I
Yes, I came in late; and, yes, Erich is right that I missed the mark on
my previous comments.
Nevertheless, now that I study this posting's history, I am very
confused!
Which package are you using? JNilo's doesn't contain any
/etc/dnscache.conf; rather, it looks like Erich's table (below).
I
Hi
Michael D. Schleif wrote the following at 23:12 23.07.2002:
>Yes, I came in late; and, yes, Erich is right that I missed the mark on
>my previous comments.
>
>Nevertheless, now that I study this posting's history, I am very
>confused!
>Which package are you using? JNilo's doesn't contain an
I will retest configuring DNS by hand on the win2K box to verify. More
on that later.
Here is
nslookup from the win2k box (when connected behind the firewall) reports
this:
C:\>nslookup yahoo.com
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.1.2
OK, I reported the content below a few hours ago. There may have been
some strange things during plugging & unplugging cables. I rebooted the
firewall, and now resolv.conf contains:
search cablenet-va.com
nameserver 127.0.0.1
nameserver 208.197.246.195
nameserver 208.197.246.194
I am going to r
Michael D. Schleif wrote:
>Yes, I came in late; and, yes, Erich is right that I missed the mark on
>my previous comments.
>
>Nevertheless, now that I study this posting's history, I am very
>confused!
>
>Which package are you using? JNilo's doesn't contain any
>/etc/dnscache.conf; rather, it l
On 2002-07-22 at 15:48 Dr. Richard W. Tibbs wrote:
> I booted up using a vanilla Dachstein RC2 floppy ( a little old,
> I know) and everything on the firewall seems fine:
Assuming you mean Dachstein-PR2, is there a reason you are using
a pre-release version of Dachstein? There were bugs in it
The situation has improved a bit.
The main symptom now seems to be that
the command netstat -an | grep 53 yields
udp00 0.0.0.0:53 0.0.0.0:*
so it does not look like the internal iface (192.168.1.254) is being
bound to port 53.
ps grep dnscache yields
1026 daemon S /usr/bin/dnscache
An
On Wed, 24 Jul 2002 11:42:17 EDT Dr. Richard W. Tibbs wrote:
> The situation has improved a bit.
> The main symptom now seems to be that
> the command netstat -an | grep 53 yields
> udp00 0.0.0.0:53 0.0.0.0:*
> so it does not look like the internal iface (192.168.1.254) is being
> bound
Hi
Brad Fritz wrote the following at 17:56 24.07.2002:
>On Wed, 24 Jul 2002 11:42:17 EDT Dr. Richard W. Tibbs wrote:
>
>...> dmesg outputs a lot of identical lines like:
> > Packet log: input DENY eth0 PROTO=17 10.1.20.1:67 255.255.255.255:68
> > L=328 S=0x0 I=414nn F=0x000 T=255 (#8)
>
>Not
On Wed, 24 Jul 2002 22:19:26 +0200 Eric Titl wrote:
> Hi
>
> Brad Fritz wrote the following at 17:56 24.07.2002:
>
> >On Wed, 24 Jul 2002 11:42:17 EDT Dr. Richard W. Tibbs wrote:
> >
> >...> dmesg outputs a lot of identical lines like:
> > > Packet log: input DENY eth0 PROTO=17 10.1.20.1:6
Brad Fritz wrote:
>
> On Wed, 24 Jul 2002 22:19:26 +0200 Eric Titl wrote:
>
> > Brad Fritz wrote the following at 17:56 24.07.2002:
> >
> > >On Wed, 24 Jul 2002 11:42:17 EDT Dr. Richard W. Tibbs wrote:
> > >
> > >...> dmesg outputs a lot of identical lines like:
> > > > Packet log: input DE
Hello
At 23:51 24.07.2002, you wrote:
>On Wed, 24 Jul 2002 22:19:26 +0200 Eric Titl wrote:
>
> > Hi
> >
> > Brad Fritz wrote the following at 17:56 24.07.2002:
> >
> > >On Wed, 24 Jul 2002 11:42:17 EDT Dr. Richard W. Tibbs wrote:
> > >
> > >...> dmesg outputs a lot of identical lines like:
>
Thanks all on list for your patience.
I have been moving my entire household, so being focused on the firewall
for more than an hour at a time has been tough.
First, let me say that I will get the latest Dachstein (or other Berg)
floppy burned at first opportunity. One question at this point:
Wh
>>But, here is an update on this rather wierd problem. The Dachstein
>>firewall has allowed access more-or-less continuously for several days
>>now, since the last reboot. The "less" part has been that every so
>>often it appears that DNS service "goes away", that is hosts become
>>unreachabl
On Sun, 28 Jul 2002 09:39:48 EDT Dr. Richard W. Tibbs wrote:
> The Dachstein
> firewall has allowed access more-or-less continuously for several days
> now, since the last reboot. The "less" part has been that every so
> often it appears that DNS service "goes away", that is hosts become
>
The LAN hosts are configured manually with the DNS servers from Charter.
Rather not do it this way, but I couldn't seem to get dnscache to serve
up names. Hope to resolve this with a newer Dachstein or other leaf.
Over 3 million boxes unpacked only a few thousand more
Brad Fritz wrote
I also have the charter service, though not using leaf on it. I have a
linksys plugged into the cable modem. The linksys receives the address
via dhcp, with the linksys serving addresses to my internal network.
I'm out of the Kennewick, WA branch. While not daily by any means (but
very frequen
Well, this is reassuring. For the record, we had a hiccup here in the
Roanoke VA area that (probably) hosed the cable modem. I had to
power-cycle the modem (and rebooted the Dach firewall) before
connectivity was restored. The "muliple modems off-line" problem might
be due to flaky head-end eq
32 matches
Mail list logo
