View Single Post
Posts: 540 | Thanked: 288 times | Joined on Sep 2009
#180
Originally Posted by kozij View Post
just checked and it is connected by the time it gives the error
Then you need to figure out what process is keeping us from binding the to interface:

Try switching the connection first manually and then running the
"executing ..." commands manually (below the icd2 dbus error message [which is just complaint about the interface missing introspection data])

Then before the dnsmasq command see what processes are listening and where "netstat -lnp" should give a list, port 53 is the one we're mostly interested in.
__________________
  • Live near Helsinki, Finland & interested in electronics ? Check this out.
  • Want anti-virus/firewall ? Read this (and follow the links, also: use the search, there are way too many threads asking the same questions over and over and over again).
  • I'm experimenting with BitCoins, if you want to tip me send some to: 1CAEy7PYptSasN67TiMYM74ELDVGZS6cCB