[SOLVED]Wifi initialised twice, leading to temporaty netwo..

[lolo44]

Hi all,

Just upgraded from mga1 to mga2 this weekend.
All went fine during the upgrade process and after reboot got something looking functional.

After login screen is prompted, I log into the system with user/pwd as usual and go to KDE desktop fine.

I do use Wifi only for network, and link is up.

Code: Select all

May 28 08:34:51 asterix ifplugd(eth1)[1912]: ifplugd 0.28 initializing.
May 28 08:34:51 asterix ifplugd(eth1)[1912]: Using interface eth1/xx:xx:xx:xx:xx:xx with driver <ipw2200> (version: 1.2.2kmprq)
May 28 08:34:51 asterix ifplugd(eth1)[1912]: Using detection mode: SIOCETHTOOL
May 28 08:34:51 asterix ifplugd(eth1)[1912]: Initialization complete, link beat not detected.
May 28 08:34:51 asterix network[1499]: Activation de l'interface eth1 :  [  OK  ]
May 28 08:34:52 asterix ifplugd(eth1)[1912]: Link beat detected.
May 28 08:34:52 asterix avahi-daemon[1216]: Registering new address record for xx::xx:xx:xx:xx on eth1.*.
May 28 08:34:53 asterix ifplugd(eth1)[1912]: Executing '/etc/ifplugd/ifplugd.action eth1 up'.
May 28 08:34:54 asterix dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
May 28 08:34:54 asterix avahi-daemon[1216]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.1.103.
May 28 08:34:54 asterix avahi-daemon[1216]: New relevant interface eth1.IPv4 for mDNS.
May 28 08:34:54 asterix avahi-daemon[1216]: Registering new address record for 192.168.1.103 on eth1.IPv4.
May 28 08:34:54 asterix ifplugd(eth1)[1912]: client: Determining IP information for eth1... done.
May 28 08:34:54 asterix ifplugd(eth1)[1912]: client:  [  OK  ]
May 28 08:34:54 asterix ifplugd(eth1)[1912]: Program executed successfully.
May 28 08:35:13 asterix ntpd[2668]: Listen normally on 3 eth1 192.168.1.103 UDP 123
May 28 08:35:13 asterix ntpd[2668]: Listen normally on 4 eth1 fe80::213:ceff:fe3c:4f85 UDP 123
May 28 08:37:06 asterix ifplugd(eth1)[1909]: ifplugd 0.28 initializing.
May 28 08:37:06 asterix ifplugd(eth1)[1909]: Using interface eth1/00:13:CE:3C:4F:85 with driver <ipw2200> (version: 1.2.2kmprq)
May 28 08:37:06 asterix ifplugd(eth1)[1909]: Using detection mode: SIOCETHTOOL
May 28 08:37:06 asterix ifplugd(eth1)[1909]: Initialization complete, link beat not detected.
May 28 08:37:06 asterix network[1497]: Activation de l'interface eth1 :  [  OK  ]
May 28 08:37:06 asterix avahi-daemon[1208]: Registering new address record for fe80::213:ceff:fe3c:4f85 on eth1.*.
May 28 08:37:07 asterix ifplugd(eth1)[1909]: Link beat detected.
May 28 08:37:08 asterix ifplugd(eth1)[1909]: Executing '/etc/ifplugd/ifplugd.action eth1 up'.
May 28 08:37:09 asterix dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
May 28 08:37:09 asterix avahi-daemon[1208]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.1.103.
May 28 08:37:09 asterix avahi-daemon[1208]: New relevant interface eth1.IPv4 for mDNS.
May 28 08:37:09 asterix avahi-daemon[1208]: Registering new address record for 192.168.1.103 on eth1.IPv4.
May 28 08:37:09 asterix ifplugd(eth1)[1909]: client: Determining IP information for eth1... done.
May 28 08:37:09 asterix ifplugd(eth1)[1909]: client:  [  OK  ]
May 28 08:37:09 asterix ifplugd(eth1)[1909]: Program executed successfully.
May 28 08:37:18 asterix ntpd[2657]: Listen normally on 3 eth1 192.168.1.103 UDP 123
May 28 08:37:18 asterix ntpd[2657]: Listen normally on 4 eth1 fe80::213:ceff:fe3c:4f85 UDP 123

1st point, for some reason, looks there are two successive Wifi initialisations. Any idea why does this happen ?

2nd point (might be linked to point 1), after login, I open let say Firefox (with multiple tabs to predefined websites) and Thunderbird. Both claim they have no network.
Refreshing pages on firefox solves issue. Same on thunderbird, who can finally get my emails.
Maybe all issue is due to this double init of the wifi (leading to some unavailability in the middle ...)
Also, after I could read my emails, I tried to send email through smtp, which failed, saying it couldn't find the SMTP server. I have no logs of this. It finally worked but I will post again if this happens again.

I will check on another PC using wifi if there is also this double initalisation on MGA2.

Rgds
Laurent

[lolo44]

Hello,

after a couple of reboot, looks like issue 1 (multiple init of wireless adapter) is gone.. (to be confirmed)

But issue 2 still persist. look like more an issue of the DNS client to me, now, but not sure. looks like DNS requests are not always served fine leading to firefox/thunderbird and even Kopete not connecting on first attempt.
This morning, started the laptop, and waited some minutes before running firefox. Firefox came up with 7 tabs, as usual, and 2 or 3 tabs indicated network issue, while 5 other connected fine ! :S Reloading the 2 tabs solved the issue, of course :S this is weird.

Same with thunderbird. at startup (while firefox already got some tabs OK), got no connection. Then clicked on 'get mail', I received the emails...

very strange issue which looks to me like an issue of one of the IP stack elements, maybe the avahi mDNS ?

Any help welcome, this is annoying that network does'nt work from 1st attempt.

with mga1, all was OK on this side.


Rgds
Laurent

[doktor5000]

very strange issue which looks to me like an issue of one of the IP stack elements, maybe the avahi mDNS ?

Avahi or mDNS does not belong to the IP stack, and is not involved with this. Also mdns has nothing to do with DNS in the classical sense for what client applications use it.

[lolo44]

Thank you for clarifying.

nevertheless, still having troubles at startup with pages not accessible / email blocked then unblocks suddenly after reload... while wifi is initialised fine before starting apps.

What kind of log may I provide to help digging into this issue ?

Rgds
Laurent

[lolo44]

Tonight I did some more testing and discovered Kopete could only connect to gmail (no MSN, no Yahoo )
After a discussion with a friend, I changed the DNS server in the configuration ( to 8.8.8.8, instead of the default livebox2 ), restarted kopete,
it worked like a charm.

It might be that my livebox2 decided to become irresponsive or erratic in the DNS side just when installing/testing MGA2.

I will reboot the box and try again later. In the meantime I keep 8.8.8.8 as DNS .

Rgds
Laurent

[doktor5000]

Probably your livebox doesn't have it's own DNS server, it will use the one from your ISP, maybe that one is malfunctioning?

[lolo44]

Hi,

this box seems to be known as ... unstable
I could try the ISP DNS instead of google ones, to identify wether the DNS proxy in the box is the cause(which is the highest probability).
I will reset the box tonight also, and hopefull all will get back fine.

this thread might be marked as 'solved' I guess.

[doktor5000]

this thread might be marked as 'solved' I guess.

Please do that yourself by editing the subject of the first post and prefix it with [SOLVED].
Thanks.

[lolo44]

Hi again

After reboot of the livebox, using the DNS proxy of the box still doesn't work. weird.
I then tried the ISP DNS hardcoded, it works fine, like google ones.
=> ISP DNS are OK
but still either the livebox has an issue, or mga has trouble with the DNS proxy at 192.168.1.1 in the box.

need to dig into this (might involve a factory reset of the box... )

Rgds
Laurent

[lolo44]

Hi,

I think I might have caught the root cause this time !
Thanks to wireshark, clearly I see the DNS relay in the livebox is not working as expected by MGA2 when opening Kopete :

Code: Select all

536 78.948074 192.168.1.103 192.168.1.1 DNS 75 Standard query A login.yahoo.com
537 78.948144 192.168.1.103 192.168.1.1 DNS 75 Standard query AAAA login.yahoo.com
538 78.992022 192.168.1.1 192.168.1.103 DNS 75 Standard query response, Not implemented
539 79.018793 192.168.1.1 192.168.1.103 DNS 193 Standard query response CNAME login-global.lgg1.b.yahoo.com CNAME eulogin.lga1.b.yahoo.com CNAME eu-eulogin.lga1.b.yahoo.com A 217.12.8.76 A 217.146.187.123

while the ISP DNS pegged directly (through the same livebox, though ...) would answer :

Code: Select all

802 350.259246 192.168.1.103 80.10.246.130 DNS 75 Standard query A login.yahoo.com
803 350.259314 192.168.1.103 80.10.246.130 DNS 75 Standard query AAAA login.yahoo.com
804 350.287658 80.10.246.130 192.168.1.103 DNS 193 Standard query response CNAME login-global.lgg1.b.yahoo.com CNAME eulogin.lga1.b.yahoo.com CNAME eu-eulogin.lga1.b.yahoo.com A 217.146.187.123 A 217.12.8.76
805 350.297655 80.10.246.130 192.168.1.103 DNS 222 Standard query response CNAME login-global.lgg1.b.yahoo.com CNAME eulogin.lga1.b.yahoo.com CNAME eu-eulogin.lga1.b.yahoo.com


I'm not really familiar to this but sounds like MGA2 somehow hasIPV6 enabled, while the livebox2 doesn't support it
Pretty sure prior to upgrade, my MGA1 was IPv4 only.

I'm going to look into this and make sur IPV6 is disabled on my system until Orange provide some functionnal livebox (ok ... this is likely to be an infinite loop ... )

Rgds
Laurent

[doktor5000]

No, this isn't about IPv6, as both records (A record -> ipv4, AAAA-record -> ipv6) are queried.
Seems this is really a problem of your livebox. But why bother, just use an external DNS server if that works better ...

[lolo44]

All,

Just checked the 'disable' IPV6 in the network config and guess what ?
no more AAAA request from MGA2, and .. all runs fine now !

Clearly the box relay DNS is saying IPV6 not supported (which I guess is somehow a good answer to indicate the system that it should not expect good answer on this side) , and clearly the system seems to be unhappy with this, as connections are unstable in such case.

So for me, the LB2 does not support IPV6 in its relay DNS. that's a fact.
but pretty sure the system does something wrong with the 'not supported' answers to AAAA record requests.
(typically, in firefox, 1st access can fail, then next ones OK. in kopete, it won't connect to yahoo or MSN, but XMPP for gmail works ... very strange)

Rgds
Laurent