Bug Reports

[Description]

Description

Similar to exigent's post below, tonight I suddenly couldn't reach www.google.ca from my laptop. My wife then reported the same thing, and I verified the same problem on my desktop. I tried to ping www.google.ca from all three machines and all three gave the same host not found error.

I went to m0n0's diagnostics and was able to both ping and traceroute www.google.ca servers from the router. I then tried connecting to the IP address of www.google.ca from all 3 machines which worked fine.

I then connected to a friend's wireless down the street on the same ISP (Rogers) and was able to load www.google.ca from there, so concluded I had a m0n0 problem. I rebooted the router and was immediately able to access www.google.ca from all three machines.

Unlike exigent I only have two ports forwarded on the router with all other traffic denied, but I don't know the details of this DNS patch that people are talking about so this may be a non issue. I installed the router on Friday Sept 5 (previous router was D-Link DGL4300) and never had this sort of problem on the old router.


Configuration

m0n0 1.3b14
Soekris net5501-70, 512Mb CF card
WAN port connected to Rogers cable modem
Vonage VoIP modem connected to LAN port as DHCP client
CM9 wireless running on OPT2 interface
2 Dell laptops and a homebuilt desktop as WiFi DHCP clients

I don't know if this is really a bug or just a simple mishap on my side, but this morning I have realized I am experiencing some random problems with the dns forwarder too with the new 1.3b14 .

I am using an alix embedded system with simple wan configuration (ethernet wan using dhcp straight to the cable modem). Just 2 ethernet ports, no wifi, no dmz. I am using "default" magic traffic shaping (share bw evenly setting) and I am forwarding just 6 ports to 2 different lan ips (from 14182 to 14188).

Some dns requests randomly fails, some other take too long to get processed. The 3 upstream DNSes have been set manually with the option to ovverride isp ones (provided via dhcp) and are working fine for sure, but the dns server at 192.168.1.1 (mono, that is) is definitely slow at times.
The only "custom" setting I have been using, influencing DNS, is the one to register DHCP leases in the DNS table, and even those queries (ie. "host m0n0wall.local 192.168.1.1") are quite slowly answered (like 1 sec delay).

Bah.

Again, maybe is a mishap on my side: pfsense (switched CF) works fine though.