|
||||||||||
A nice feature would be just to have the DHCP-Server assigning the external DNSes to the clients just as an option. regards, Holger Bauer -----Ursprüngliche Nachricht----- Von: Steven Honson [mailto:steven at honson dot org] Gesendet: Montag, 2. Februar 2004 23:46 An: m0n0wall at lists dot m0n0 dot ch Betreff: RE: [m0n0wall] Any know issue with the DNS-forwarder? MinimumHardware requirements? I ran into the same problem setting up my m0n0wall box to connect to iiNet (a local DSL provider) using PPPoE. Cheers, Steven -----Original Message----- From: Hilton Travis [mailto:Hilton at QuarkAV dot com] Sent: Tuesday, 3 February 2004 9:41 AM To: m0n0wall at lists dot m0n0 dot ch Subject: Re: [m0n0wall] Any know issue with the DNS-forwarder? MinimumHardware requirements? Hi Holger, On Mon, 2004-02-02 at 19:58, Holger Bauer wrote: > Hello, > > this weekend I set up a monowall with using dns-forwarder (my other > monowalls have a seperate DNS-Server). At first sight it seemed, that > it doesn´t get DNS assigned by the pppoe-connection properly but my > provider assigns them for sure. After placing the two DNS of the > provider in the general settings table and unchecking the "override" > option it seemed to work, but sometimes DNS is very slow and some > adresses are never resolved (for example > http://prdownloads.sourceforge.net/vnc-tight/tightvnc-1.3dev3-setup.exe?down load). > When I setup the DNS on the clients to use the DNS of my provider > directly everything is working fine. > Does anyone know what´s going on here? Funny you should mention this, as I configured two m0n0wall boxen over the weekend, and noticed the same thing - with a PPPOE provided IP/DNS, m0n0wall fails to utilize the assigned DNS Server addresses, and you have to manually enter them on the "General Setup" page. Hhmmm, reading the General Setup page a bit more closely, it appears that the PPPOE-provided DNS Servers are not assigned to DHCP clients. That is sensible, but I think that the issue here is that even though the m0n0wall IP address is provided to DHCP-assigned clients, the m0nb0wall itself fails to receive the PPPOE-assigned DNS Servers (or it fails to act on them properly) resulting in a broken DNS system since m0n0wall cannot forward DNS requests to your ISP's DNS Servers. I have not noticed any slowdown, tho. I just enter the provider DNS Server IPs and it rocks along nicely. > By the way, what are the minimum hardware requirements? This > Monowall uses the latest CD-ROM build and consists of a Pentium 133 > MMX, 128 MB SDRAM and 3 PCI NICs, 2 of them bridged. Is 133 MHz too > weak? m0n0wall runs on a Soekris 4501 which is a 486-class CPU running at 133 MHz with 64 MiB SDRAM. I think that your P5/133 would easily handle the task - unless this is a 10Mbps or faster Internet connection. :) -- Regards, Hilton Travis Email: Hilton at QuarkAV dot com Manager, Quark AudioVisual Phone: +61-(0)7-3343-3889 Quark Computers Phone: +61-(0)419-792-394 (Brisbane, Australia) http://www.QuarkAV.com/ Open Source Projects: http://www.ares-desktop.org/ http://www.mamboband.org/ Non Linear Video Editing Solutions & Digital Audio Workstations Network Administration, SmoothWall Firewalls, NOD32 AntiVirus Conference and Seminar AudioVisual Production and Recording War doesn't determine who is right. War determines who is left. --------------------------------------------------------------------- To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch --------------------------------------------------------------------- To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch ____________ Virus checked by G DATA AntiVirusKit |