How to monitor my LAN network traffic

[Haggis Veteran]

As budman says your ip has been updated with opendns as your other box is blocking it

-

there should be an option on the drop down that says use dhcp for IP address only or soemthing like that

[mcloum]

I alwasy find it funny when people blur out their MAC addresses of internal cards when they have a none routable IP address set :)

[Koshur]

dyndns is not going to update opendns. You need something to update opendns, dnsomatic can do that for you - but you would have to run a dnsomatic client on some machine on your network if your router does not support dnsomatic. Or run the opendns client on some machine on your network

Ok.. so here is what i did - ran the client updater software on a win client. It updated the IP for Dyndns (cancelled open DNS for the moment)

So did those dns come from your dhcp - or did you set them static in your windows.

Win client is set to get it dynamically and the filtering works well, when i update the IP through the updater software.

Windows allows you to easy set static dns while getting IP from dhcp. If it came from your dhcp server then linux should be getting it as well unless at somepoint you had set your isp dns statically on the box?

I have set Dyndns servers as static in my router page, and it shows up in the status page as well. Exactly, if its coming dynamically for win, they why not for the linux box? why does it still show my ISP DNS? I have to put the static on my linux box (putting in Dyndns servers) so that i can get online.

Clearly your linux box is not using opendns- it was using your isp dns. So it would not be blocked.

If your IP changed you better make sure that opendns reflects that change or even if your using opendns blocks wont work how you set them.

Bottom line -

>If by putting static Dyndns servers on router only,

>updating IP through updater client (on win client)

= the win client picks up the servers dynamically + the filtering works on win client ONLY

BUT

>If by putting static Dyndns servers on router only,

>updating IP through updater client (on win client)

>putting the same DNS servers as static on linux box ( have to do this - i cant go online without this step) - see this link for IPV4 setting tab option

filtering does not work and the dig command to last.fm shows ISP DNS servers being used.

As budman says your ip has been updated with opendns as your other box is blocking it

-

there should be an option on the drop down that says use dhcp for IP address only or soemthing like that

Check this link(see the steps - #4) which shows the various option for IPv4 settings tab.

P.S - i ran a clean format of my zorin installation, just incase it was some already existing messed up config files that were interfering with the DNS cache. and ofcourse i messed up my boot too... :/

[+BudMan MVC]

Your making something so freaking simple so complicated.. I just don't know what you are not understanding about such a simple concept.

Does not matter if you use opendns, dyndns, scubit.com, https://dns.norton.c...b/dnsForHome.do etc.. etc.. etc...

They all need to know what your public IP is - this is where the queries will come from. Be it your router on behalf of your clients, your clients directly, some other local dns your running that forwards there, etc.

So that they can setup the policies you want, level of filtering, custom blocks, etc.. Now as long as they have your current IP you don't have to worry about updating them -- UNLESS your ip changes. But like you said until you reboot your router this does not change. So DONT reboot you router for a while.

Now what should happen is your router dhcp server should tell your clients to use opendns, googledns, etc. directly!!! ie hand out 1.2.3.4 (ip address of service dns) Or hand out itself as dns for your dhcp clients. So windows/linux/beos/freebsd/aix/openbsd/hp-ux/suse/etc will either use the service dns directly or ask your router! (192.168.1.1)

If they are asking your router - then your router needs to ask 1.2.3.4 vs your ISP.

So either your dhcp is not handing out opendns/googledns/dyndns like you think it is! Your windows box clearly was using opendns - so on the IPv4 properties tab.. What do you have set??

If this got opendns from DHCP then your linux box should be setup the SAMEWAY!!! Then just doing

dig something.tld will tell you what server it is asking! If still asking your ISP. Then contact your support for that OS (never heard of it btw - why not just use a commong distro like ubuntu if that is what its based off of)

This is should take you all of about 2 minutest TOPS to configure and get working on every single box on your network!! As I told you I don't use opendns and had my boxes being blocked from using last.fm in 30 seconds.

Once you know how your clients are getting their dns servers be it static or what your routers dhcp is handing out. And what your router is doing if asked for dns. Then you can worry about running an update client on one of your computers to keep the service you picked updated for when your public IP changes.

If you are still having issues - PM me and I will teamviewer into your network and get it working for you in 2 minutes.

[Haggis Veteran]

Change the setting to DCHP Addresses only

[Koshur]

Removing dnsmasq from the network config file did the trick. Thanks again all of you guys especially the champ "Budman" who really nailed it this time..

[+BudMan MVC]

To give a bit more detail for anyone interested, been PMing back and forth on this with him.

For some reason his linux box had dnsmasq installed, which is a dns forwarder. Not sure how that happened or why, but so his resolv.conf on his linux box was pointing to loopback 127.0.0.1, dnsmasq was listening and would forward his request to his ISP dns vs what dhcp was handing out or what he setup manually in the network manager.

resolv.conf has gotten a bit more complicated over the years and its being updated with scripts and such vs just being a static file. So it can be a bit tricky sometimes understanding how your box is resolving vs just looking in resolv.conf which in his case pointed to his loopback address.

This really should not be so complicated - change your dhcp to hand out the dns you want your clients to use. Or have the dns they use, ie your router forward to what dns you want to use. Or set your clients to use whatever dns you want to use manually.

The problem in the case with this linux box was understanding how/where to change it from pointing to his isp dns.