DNS problem

Yevhen Kyriukha kirgene at gmail.com
Mon Nov 12 04:50:11 PST 2012


Thanks, Sameer! It works now.

2012/11/12 <connman-request at connman.net>

> Send connman mailing list submissions to
>         connman at connman.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.connman.net/listinfo/connman
> or, via email, send a message with subject or body 'help' to
>         connman-request at connman.net
>
> You can reach the person managing the list at
>         connman-owner at connman.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of connman digest..."
>
>
> Today's Topics:
>
>    1. Re: Connman 1.9 won't attempt connecting to wifi service
>       (Sameer Naik)
>    2. Re: DNS problem (Sameer Naik)
>    3. Re: Connman 1.9 won't attempt connecting to wifi service
>       (Patrik Flykt)
>    4. Re: Connman 1.9 won't attempt connecting to wifi service
>       (Patrik Flykt)
>    5. Re: Connman 1.9 won't attempt connecting to wifi service
>       (Sameer Naik)
>    6. Re: Connman 1.9 won't attempt connecting to wifi service
>       (Patrik Flykt)
>    7. Re: Connman 1.9 won't attempt connecting to wifi service
>       (Sameer Naik)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 12 Nov 2012 11:31:26 +0530
> From: Sameer Naik <sameer.subscriptions at damagehead.com>
> To: connman at connman.net
> Subject: Re: Connman 1.9 won't attempt connecting to wifi service
> Message-ID:
>         <CAJ5s_ihOAPGjiji4WXUz+Fvq8GAKX=
> jS_cXR78vcAPKXuJDNqA at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hello Patrik,
>
> On Fri, Nov 9, 2012 at 1:38 PM, Patrik Flykt
> <patrik.flykt at linux.intel.com> wrote:
> >
> >         Hi,
> >
> > On Fri, 2012-11-09 at 11:38 +0530, Sameer Naik wrote:
> >> I noticed that connman had appended
> >> a line 'Failure=invalid-key' in the settings file of the saved wifi
> >> profile due to which the connection was not happening even after
> >> restarting connman multiple times.
> >
> > ConnMan won't autoconnect to a network that has been marked failed. One
> > option is to successfully connect manually for example from the command
> > line to get the failure mark removed.
> >
> >> I had to remove that line for it to
> >> start working again.
> >
> > That works also. In general it is advisable not to edit any files
> > in /var/lib/connman/*/* as their format can change without any notice.
> >
> > Any /var/lib/connman/*.config file is another matter, those are used for
> > WiFi provisioning. If you had provisioned the WiFi network, simply
> > removing the .config file and adding it back would make ConnMan first to
> > remove the failed service and then to recreate a new service for it. The
> > new service would not have the baggage of invalid keys failure attached.
> >
> >> I would have expected that connman would attempt connecting to the
> >> service at least once and figure out whether the key was invalid or
> >> not and then stop connection attempts to the service if the key was
> >> found to be invalid.
> >
> > Yep, exactly this happened.
> >
> >> At the moment I don't have an agent registered,
> >> so i don't know if there is something more that occurs in this case.
> >
> > The agent is needed should ConnMan need a passphrase or any other input
> > from the user. If everything is preprovisioned
> > in /var/lib/connman/*.config files, ConnMan needs nothing from the
> > Agent.
> >
> >> The condition that occured in my case was purely a side effect of
> >> being in developer mode. I am not sure if this could occur in
> >> production mode.
> >
> > ConnMan does not know about the product being in developer of production
> > mode, thus it thought the invalid key was a valid reason.
> >
> >> One last thing, Is connman compatible with wpa_supplicant-1.0?
> >
> > Yes, up and running here at the moment.
>
> I think i found out why connman would not work after upgrading to
> wpa_supplicant-1.0. What i noticed is that connections will not happen
> if the passphrase is specified in ASCII format. For example i created
> a config file named aircrack.conf with the following config.
>
> [service_aircrack]
> Type=wifi
> Name=aircrack
> Passphrase="my psk password"
>
> I put quotes around the passphrase to indicate that is was specified
> in ASCII (but i dont think connman cares about the quotes). With this
> config, the connection would always fail. So i used wpa_passphrase to
> generate coded passphrase and changed the above config to the
> following:
>
> [service_aircrack]
> Type=wifi
> Name=aircrack
> Passphrase=025f1e0cf5b394d09c35e8e47c0da00346b8a9a4450d001b7952070f623ad804
>
> After this connman was able to connect to the wifi network. With
> wpa-supplicant-0.7.3 i was able to use ASCII passphrases in connman
> configs. But after the update it does not seem to work.
>
> I also checked if i was able to specify ASCII passphrases using
> wpa_cli (wpa_supplicant was configured to use the file interface) and
> ASCII passphrases worked just fine with wpa_supplicant and wpa_cli.
>
> >From the above it looks like connman is not able to work with ASCII
> passwords when used with wpa_supplicant-1.0 or i am missing some
> configuration.
>
> Regards
> ~Sameer
>
> >
> > Cheers,
> >
> >         Patrik
> >
> > _______________________________________________
> > connman mailing list
> > connman at connman.net
> > http://lists.connman.net/listinfo/connman
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 12 Nov 2012 11:35:59 +0530
> From: Sameer Naik <sameer.subscriptions at damagehead.com>
> To: connman at connman.net
> Subject: Re: DNS problem
> Message-ID:
>         <CAJ5s_ijTgjm8rzMR=LD2FnVvyb0uOFR-2r=
> xpvsvBv-G3Tu+ag at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hello All,
>
> I am also noticing the same issue. Except in my case, i am using a USB
> wifi dongle.
> If i unplug the usb dongle and plug it back in, dnsproxy is no longer
> able to perform DNS resolutions.
>
> Yevhen, my _TEMPORARY_ workaround for this is to disable use of
> dnsproxy until this is fixed. This done by specifying the --nodnsproxy
> option to the connmand command line.
>
> Regards
> ~Sameer
>
> On Sun, Nov 11, 2012 at 7:47 AM, Yevhen Kyriukha <kirgene at gmail.com>
> wrote:
> > Hi!
> >
> > I connect to internet using 3G modem.
> > For that purpose I use connman and ofono.
> > I set "auto connect" property for my 3G connection, so that connman
> > reconnects if connection is lost.
> >
> > The problem is when I connect to internet second and further times (after
> > reconnection), I can't access any host by its name (only by IP address).
> >
> > I'm getting "Temprary failure in name resolution" error when I execute
> > "wget ya.ru" command in console and the following messages in connman
> logs:
> > ----------------------------
> > connmand[3519]: src/dnsproxy.c:udp_listener_event() Received 23 bytes (id
> > 0xc19a)
> > connmand[3519]: src/dnsproxy.c:parse_request() id 0xc19a qr 0 opcode 0
> > qdcount 1 arcount 0
> > connmand[3519]: src/dnsproxy.c:parse_request() query ya.ru.
> > connmand[3519]: src/dnsproxy.c:resolv() server 193.41.63.162 enabled 1
> > connmand[3519]: src/dnsproxy.c:ns_resolv() Cannot send message to server
> > 193.41.63.162 sock 17 protocol 17 (Invalid argument/22)
> > connmand[3519]: src/dnsproxy.c:resolv() server 193.41.60.18 enabled 1
> > connmand[3519]: src/dnsproxy.c:ns_resolv() Cannot send message to server
> > 193.41.60.18 sock 18 protocol 17 (Invalid argument/22)
> > connmand[3519]: src/dnsproxy.c:request_timeout() id 0xc19a
> > ----------------------------
> >
> > I attached debug logs of connman and ofono to this message.
> >
> > --
> > Best regards,
> > Yevhen
> >
> > _______________________________________________
> > connman mailing list
> > connman at connman.net
> > http://lists.connman.net/listinfo/connman
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 12 Nov 2012 09:25:47 +0200
> From: Patrik Flykt <patrik.flykt at linux.intel.com>
> To: connman at connman.net
> Subject: Re: Connman 1.9 won't attempt connecting to wifi service
> Message-ID: <1352705147.4951.7.camel at pflykt-mobl1>
> Content-Type: text/plain; charset="UTF-8"
>
>
>         Hi,
>
> On Fri, 2012-11-09 at 21:37 +0530, Sameer Naik wrote:
> > They actually have an updated driver released for the chip.
>
> When you say "they" here, do you mean some particular vendor (which
> one?) or a newer version of the Linux kernel?
>
> Cheers,
>
>         Patrik
>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 12 Nov 2012 09:37:04 +0200
> From: Patrik Flykt <patrik.flykt at linux.intel.com>
> To: connman at connman.net
> Subject: Re: Connman 1.9 won't attempt connecting to wifi service
> Message-ID: <1352705824.4951.10.camel at pflykt-mobl1>
> Content-Type: text/plain; charset="UTF-8"
>
> On Mon, 2012-11-12 at 11:31 +0530, Sameer Naik wrote:
> > Passphrase="my psk password"
>
> With the quotation marks attached, ConnMan will think the quotation
> marks are part of the passphrase. Just try with:
>
> Passphrase=my psk password
>
> Does that fix the problem?
>
> Cheers,
>
>         Patrik
>
>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 12 Nov 2012 13:54:48 +0530
> From: Sameer Naik <sameer.subscriptions at damagehead.com>
> To: connman at connman.net
> Subject: Re: Connman 1.9 won't attempt connecting to wifi service
> Message-ID:
>         <
> CAJ5s_ijkqSwtsKakg1Ao7rxmRTwiwk51N5J+MM4qawHD8Ee37A at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> They means the wifi chip manufacturer, Realtek.
>
> Regards
> ~Sameer
>
> On Mon, Nov 12, 2012 at 12:55 PM, Patrik Flykt
> <patrik.flykt at linux.intel.com> wrote:
> >
> >         Hi,
> >
> > On Fri, 2012-11-09 at 21:37 +0530, Sameer Naik wrote:
> >> They actually have an updated driver released for the chip.
> >
> > When you say "they" here, do you mean some particular vendor (which
> > one?) or a newer version of the Linux kernel?
> >
> > Cheers,
> >
> >         Patrik
> >
> > _______________________________________________
> > connman mailing list
> > connman at connman.net
> > http://lists.connman.net/listinfo/connman
>
>
> ------------------------------
>
> Message: 6
> Date: Mon, 12 Nov 2012 11:05:40 +0200
> From: Patrik Flykt <patrik.flykt at linux.intel.com>
> To: connman at connman.net
> Subject: Re: Connman 1.9 won't attempt connecting to wifi service
> Message-ID: <1352711140.4951.11.camel at pflykt-mobl1>
> Content-Type: text/plain; charset="UTF-8"
>
> On Mon, 2012-11-12 at 13:54 +0530, Sameer Naik wrote:
> > They means the wifi chip manufacturer, Realtek.
>
> Too bad. I hope their newer driver fixes any issues you have.
>
> Cheers,
>
>         Patrik
>
>
>
> ------------------------------
>
> Message: 7
> Date: Mon, 12 Nov 2012 15:57:14 +0530
> From: Sameer Naik <sameer.subscriptions at damagehead.com>
> To: connman at connman.net
> Subject: Re: Connman 1.9 won't attempt connecting to wifi service
> Message-ID:
>         <CAJ5s_ijuJMB3oYu_EFU-8aKgANaE=w=
> AhCcHZWxDUN33grkDyg at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> On Mon, Nov 12, 2012 at 1:07 PM, Patrik Flykt
> <patrik.flykt at linux.intel.com> wrote:
> > On Mon, 2012-11-12 at 11:31 +0530, Sameer Naik wrote:
> >> Passphrase="my psk password"
>
> I used to specify the password without the quote before. But i made a
> mistake, i mistook the connect-failed error to be related to
> wpa-supplicant-1.0 upgrade. Frequent "connect-failed" errors lead me
> to believe that it was because of the wpa_supplicant update. Its
> sorted now, ASCII pass phrases do work after the wpa_supplicant
> update. Earlier, the invalid-key error was due to a wpa_supplicant
> config option.
>
> I also updated the wifi driver with the latest sources. I have not
> noticed any changes in the behaviour ATM. However there were a _LOT_
> of changes in the driver.
>
> Regarding the frequent 'connect-failed' error at observed, i have the
> following observations:
>
> Test Procedure:
> 1. Start connmand with wifi plugged in
> 2. Check if connection established or failed
> 3. Disconnect wifi dongle
> 4. Connect wifi dongle
> 5. repeat 2.
>
> 1. If i launch connmand with the -d option, i.e.
> # connmand -W wext -I eth0 -n -d
> , then the connection works 90% of the time. Rarely there is a
> connect-failed error.
>
> 2. If i launch connmand without the -d option, i.e.
> # connmand -W wext -I eth0 -n
> , then the connection works 50% of the time.
>
> Attached is the log generated for Case 2. In this log you will notice
> that every alternate connection attempt fails.
> Typically connman is launched at boot time without the '-n -d' options
> which more or less is represented by Case 2.
>
> Could there be a race condition occurring for this issue to show up?
> which occurs less frequently due to the large number of debugs printed
> when -d is specified.
>
> Hopefully these test results will throw some light on the cause of this
> issue.
>
> Thanks and Regards
> ~Sameer
>
> >
> > With the quotation marks attached, ConnMan will think the quotation
> > marks are part of the passphrase. Just try with:
> >
> > Passphrase=my psk password
> >
> > Does that fix the problem?
> >
> > Cheers,
> >
> >         Patrik
> >
> > _______________________________________________
> > connman mailing list
> > connman at connman.net
> > http://lists.connman.net/listinfo/connman
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: connmand.log
> Type: application/octet-stream
> Size: 8411 bytes
> Desc: not available
> URL: <
> http://lists.connman.net/pipermail/connman/attachments/20121112/0fcebd8a/attachment.obj
> >
>
> ------------------------------
>
> _______________________________________________
> connman mailing list
> connman at connman.net
> http://lists.connman.net/listinfo/connman
>
> End of connman Digest, Vol 46, Issue 32
> ***************************************
>



-- 
Best regards,
Yevhen



More information about the connman mailing list