does someone knows what this line in logs says :

user.warn igmpproxy[2726]: MRT_DEL_MFC; Errno(2): No such file or directory

?

@starcms
Just made your DNS/DHCP config suggestion. I did restore the WAN settings to defaults just so I would know that I was making use of the latest settings. Working really well so far. Yes I did do a reboot to clear things out.  So glad to have LEDE running the way I think it should. Very fast and reliable. Always has been my go to except for when I started having lookup issues. Not sure why this suddenly became an issue as I have been doing the same setting for quite a few releases back and with driver changes I tend to do a new configuration just in case there is something new that an old backup might mess up.

(Last edited by bill1228 on 7 Aug 2017, 19:45)

@starcms

I recently made the changes you suggested for DNS server settings to be made in DHCP and DNS and noticed that I could no longer opkg update from my router. My other devices on the network could connect to the internet just fine. but it seems my router was not resolving certain requests correctly. I was able to ping 8.8.8.8 but not google.com. Anyways I unchecked the box for ignore Resolve file and everything started working correctly. and my devices were still using the custom DNS server I had set. Are you sure the ignore Resolve file should be checked, if so maybe you could provide insight as to why that is happening when it is checked.

I made the changes as suggested by starcms. I can ping google.com by name and IP address without issue. Am using Level 3 DNS servers 4.2.2.2 and 4.2.2.4 in the DNS/DHCP config without DNS servers defined anyplace else. I can also do opkg update without issues. Updates just fine. Not sure where your issues are. Maybe re-read what starcms suggested and check your LEDE config or worst case start over with a clean config.

Update
Just a thought, I rebooted after the changes. Did you? If not I would give that a try.

(Last edited by bill1228 on 8 Aug 2017, 02:16)

If you don't check the ignore resolve file box, dnsmasq will use a combination of your ISP's DNS servers as well as the custom ones you enter into DNS forwardings under DHCP and DNS settings -- as opposed to using only the custom DNS servers you enter into DNS forwardings.

As @bill suggested, a reboot of the router is highly recommended, if not mandatory, to getting everything working correctly.

Edit: Just a little more info on the ignore resolv file box.  If you don't have it checked, as I said before, it will use any custom DNS servers you entered in DNS forwardings PLUS any DNS servers from your ISP which can be viewed  with the command:

cat /etc/resolv.conf 

(Last edited by starcms on 8 Aug 2017, 05:53)

@bill, great to hear it's working for you!!

Not sure what that exact error means, but if you don't use igmpproxy (it is mostly/only used for those with IPTV -- those who get TV over their broadband connection -- pretty sure only those who have Fiber; don't get this confused with Cable TV and a Cable modem -- yes, you get both over the same coaxial line, but the cable modem uses different frequencies than Cable TV.  The Cable TV isn't carried over IP.), you can simply disable it on start-up or uninstall it.

(Last edited by starcms on 8 Aug 2017, 05:16)

thanks ! i will disable it my logs was full with this warn, and i do not use IPTV....tnx!

I'm using stock (Cox) DNS.  Is there anything I can do?  Also will this be fixed in future builds? Thanks

(Last edited by BIOHazard87 on 8 Aug 2017, 11:16)

Hi All,
I will say that when I originally setup my LEDE/OpenWRT router (WRT1900ACSv2), I disabled the "Ping" and "IGMP" rules.  I found out last night that the "IGMP" rule being disabled, prevented my ability to watch HBO, SHO, MAX  ondemand programming on Directv.

once I enabled the rule and restarted the firewall, everything was good in the world  :-)

(Last edited by jefftk99 on 8 Aug 2017, 14:00)

I want to thank everyone for the help and feedback in the past weeks.

I was an avid user of DD-WRT router software and have recently moved over to David's LEDE builds.  I will say I do see a significant improvement in stability of the running software.  I also see an improvement in wireless connection speeds and the stability of the wireless radios.

As I tweak the settings I may have additional questions and it is great to know that this forum has such an active community.

Best regards

Since you are using the DNS servers provided by your ISP and not doing any DNS server configuration I do not know what your problem might be. I suppose the ISP DNS servers are slow, but suspect that highly unlikely in this day and age. I cannot speak to fixes in future builds as I am an end user not a dev.

@starcms
At one point I managed DNS for a large company, retired now,  and once I got to looking at what you were suggesting it was like a head slap, why didn't I know this? Your suggestion about configuring DNS servers in dnsmasq makes perfect sense and seems like what I was always looking for. Never could find a good writeup on Openwrt about doing it this way and since it was working, until recently, I never researched further. Probably a case of knowledgeable folks thinking it is obvious.

THANKS for your help and support! You are a big asset to this forum and thread.

Hi Bill1228,

Prior to configuring DNS within the DHCP/DNS section, did you have the DNS servers listed in the WAN interface ?  Did you experience the issue where your system would no respond to a page reload ?

When you changed the WAN interface back did you still uncheck the "Use DNS servers Advertised by peer" ?
Did moving DNS under DHCP/DNS resolve that issue ?

(Last edited by jefftk99 on 8 Aug 2017, 17:53)

Running Davidc502 2017-07-30 firmware on my WRT3200ACM-EU, I'm having some issues to my local network...

I have an raspberry pi on my network doing freeradius and cups, and sometimes cannot ssh to the raspberry pi... and only one time I was able to go cups web page...

Also sometime I also run issues to ssh to the router... (ssh: connect to host 192.168.1.1 port 22: No route to host
)

And sometimes the Internet is slow (hungup on "resolving host") (I have 200 Mbit connection)

changed the setting suggested "option nonwildcard    '0'" in /etc/config/dhcp, but did not set custom DNS servers...

Ok, here is the history of my DNS server settings quest.
Sometime ago I read somewhere that you set the DNS servers on the LAN interface, which I did for sometime without issues. Then started getting DNS timeouts with more recent builds which chased me over to DD-WRT as I did not have the issues there. @Starcms suggested, at first, to set on WAN rather then LAN. This took care of the DNS timeouts for me. He later suggested the settings on DNS/DHCP in Luci, which controls config of dnsmasq service. This sets things so only the wanted DNS servers are queried if done as he directed. As I understand things now, before the ISP DNS servers may still be queried as well as the defined ones. As I recall I saw this in the resolv.conf file, both defined and ISP servers listed. Since making the last change I have not had any slowdowns/timeouts. 

Of course this all assumes you are wanting to use certain DNS servers and not just the default ISP DNS servers.

(Last edited by bill1228 on 8 Aug 2017, 19:22)

Regarding firewall rules, it's safe to disable ping.  And perhaphs Allow-IPSec-ESP and Allow-ISAKMP depending on your usage.  Nothing else or you will have issues.

However, regarding the igmpproxy package, it is save to disable or remove this package unless you have IPTV -- plus that package needs extensive configuration based on your IPTV set-up.

The igmpproxy package and the Allow-IGMP firewall rule are two entirely different things...

I also have directv.  If you use adblock, do a search of this thread. I posted quite a while back a domain you need to add to your whitelist to ensure all On-Demand content works (it shoudn't affect HBO, SHO, etc, but does affect on-demand content where there are commercials).

(Last edited by starcms on 8 Aug 2017, 20:49)

I also have Cox.  For the heck of it, I disabled my custom DNS servers (dnscrypt) and went back to the stock config.  No issues with Cox DNS resolving.  Did you see my post a few pages back regarding editing one option (option nonwildcard    '0') of your /etc/config/dhcp file and rebooting to see if that helps?

If that doesn't help, it won't be fixed in future builds unless the LEDE (soon to be OpenWRT again) team fixes it.  @david builds based on the LEDE development branch -- he can't fix random issues.

(Last edited by starcms on 8 Aug 2017, 20:26)

@all,

Guys, please remember.  @david makes his builds straight from the LEDE development branch.  He adds more packages in his build than are included in the stock LEDE build, removes one troublesome one, and makes at least one tweak (the tweak to disable amsdu to fix the ping issue -- right now it is only in the modified driver (which is HIGHLY recommended that you install, especially if you play online gaming or make VoIP phones calls or anything else where ping is vital), it will be included with his build starting with the next version he puts out).

He puts out amazing builds, but isn't capable of fixing issues that exist on the LEDE development branch.  Any issues with LEDE should be reported on a LEDE forum or on github so that they can be investigated and resolved.

Also, many recent questions have been asked over and over recently.  Please do a quick search before asking.

I realize we have many new members recently and that is great!  And I know the thread is too long to read every post, but please search before asking.  And any LEDE generic questions really don't belong here, but as long as they are somewhat on topic or at least asked nicely, they will most likely be answered

Thanks all, and I'm sure @david is very proud to see his build getting so much attention, because at least IMO, it's the best build out there for the WRT1200/1900/3200 series.

@david,

Thanks for everything, all of your countless time and effort making these builds what they are!

@those who use the lede repos to keep all their packages up to date between @david's releases

a new version of dnscrypt is out, 1.9.5-5.  Unless you like tons and tons of log spam, I'd highly recommend issuing the command

opkg flag hold dnscrypt-proxy

and staying on version 1.9.5-4 until the problem is resolved.

(Last edited by starcms on 8 Aug 2017, 21:01)

I accidentally upgraded it last night and it broke dnscrypt from starting due to invalid options and not being compiled with plugins. Reinstalled 1.9.5-4 from David's repo and issue went away.

Looking through the dnscrypt options in the LEDE Configuration menu, there are 3 things to include or not.

1. Enable Plugins = Y
2. dnscrypt proxy = Y
3. proxy resolvers = Y

Are there any other modules that need to be included that aren't listed above?

*EDIT*

No issues here resolving using dnscrypt, but I'm not connected to a modem, as my router connects to a ONT which just converts ethernet to optical and then to a switch at the fibre hut. I've tested with both the 3200acm and 1900acs V1, and rebooted several times to see if there was a timing issue.

(Last edited by davidc502 on 9 Aug 2017, 01:40)

I am facing issues with the latest David's built.
It is like it doesn't boot completely.
Some commands i have inside rc.local are not executed, and i cannot perform a reboot neither from command line, nor from Luci (it just refreshes the page when i hit reboot).
I checked the logs, but i didn't see something relevant there.
Tried a couple of times to re-flash it, but the problem remained.
Any idea what can cause it?

@david,

When I mentioned dnscrypt today or yesterday (just a few posts up), I was referring to the new 1.9.5-5 version that was just released, not the 1.9.5-4 version that is included in your r4651 build that works perfectly. 1.9.5-6 is about to be released to fix the issues with 1.9.5-5.

However those compile-time options (I'm guessing) look good.  Are those what you have been using?  Just keep doing whatever you've been doing.

Enable plugins is definitely yes, thank you so much for including those!  I'm guessing dnscrypt proxy is talking about the dnscrypt-proxy package itself and proxy resolvers is referring to the dnscrypt-proxy-resolvers package.  So that sounds like everything to me.

• Note to users of dnscrypt:

To get ready for version 1.9.5-5 (and newer, 1.9.5-6 is about to come out), for those of you who always save your settings, you will need to add the following to the very top of /etc/config/dnscrypt-proxy:

# config global
     # start dnscrypt-proxy from procd interface trigger rather than immediately in init
     # if needed you can restrict trigger to certain interface(s)
     # list procd_trigger 'wan'
     # list procd_trigger 'wan6'

Once you decide to upgrade to 1.9.5-5 (or newer) manually, or you upgrade to @david's next build (which is better than upgrading it manually, because if you upgrade manually you lose plugin support), be sure to uncomment (at least) the config global line and I would recommend uncommenting the list procd_trigger 'wan' line.  This only affects those that use dnscrypt and always save and restore their settings.

1.9.5-5 is meant to fix any remaining timing issues; although I have never encountered any, and 1.9.5-6 is a quick patch to fix a bug causing log spam in 1.9.5-5.

(Last edited by starcms on 9 Aug 2017, 05:34)

@starcms & @bill1228

Ok so I've restarted from scratch loading LEDE fresh from factory. First thing I did was I set the DNS settings as per @starcms instructions. Put custom DNS in DNS forwardings of DHCP and DNS settings, and checked the box for ignore resolve file and everything worked as advertised. So appears you are correct sir's.

Now If one of you could maybe help me further troubleshoot? I continued my setup for the rest of the router and what do you know I get the same problem as before after installing and setting up openvpn-policy-routing package. again unchecking the checkbox for ignore resolve file fixes it. I have done a check for any DNS leaks after unchecking ignore resolve file and it appears that DNS is not going through the ISP DNS server. So do either of you have any insight that could maybe help me out?

NOTE 1: I noticed that before checking the box for ignore resolve file that the line below it "Resolve file" was populated with one of the /tmp/resolv.conf files. After unchecking ignore resolve file again the line "Resolve file" no longer was populated with the /tmp/resolv.conf file it is just blank now. So maybe just deleting this line has the same effect as checking the box?

NOTE 2: I did reboot the router after changing any of the settings just to be sure.

Thanks for all your help fellas, I really appreciate it!

Hi,

Any idea when the next build will be released with the "amsdu" patch incorporated into the build ?