Sabayon Community

by **johanPO** » Wed May 30, 2007 10:06

I am new to Sabayon, I must say that so far I like it. Yesterday I had some strange issues that I never had before (I used to use Ubuntu). The webbrowsers firefox and opera lost the connection to the web, the strange thing though was that at command level I could ping the web pages that the browser claimed were not available. Restarting the browsers did not help. Parallel to this I had azeures running...
I must say that I am a bit confused about this. Any ideas anyone

by **wolfden** » Wed May 30, 2007 10:25

Can you provide any more information?

version? wired? wireless? dial-up? dsl? network configured properly? router?

by **johanPO** » Wed May 30, 2007 11:51

Not at my computer, will try to dig in the log files tonight.

Version from Sabayon 3.4 Loop 2
Wireless connection, using a card with prism54. Module is correctly loaded, lsmod gave the expected
Network is to my understanding correctly configured. I used the net-setup script as the network manager freezes up my machine. This is has been the case also with Ubuntu...

DSL, with router.

All of these things are working as I am getting a correct response to ping http://www.gmx.de or my router for example. Trying to access these with the browsers did not work I got some timeout. Also the web pages did work earlier yesterday, without any changes to the PC

I have to my understanding a working network. File sharing worked, and I was able to download and install some programs with emerge. Also the network is running, as my wifes PC (WinXP) is being able to access these pages.

Could this somehow be a case of an upset firewall? I did not activate firestarter. Maybe iptables is doing something in the background...

Greatful for any hints

by **Fitzcarraldo** » Wed May 30, 2007 18:13

Curious. I have had the same thing happen a few times yesterday and today with my freshly-installed SL 3.4 Loop 2b. Firefox displays the white screen with the 'Try Again' button. I thought that my home hub or ADSL connection were playing up and so did not bother to mention it in this thread, but now I'm beginning to wonder if it's a problem with SL 3.4 Loop 2b. If I close Firefox and relaunch it then it connects. Actually, once today I had to unplug my Ethernet cable and plug it in again to get the connection. This never happened to me with SL 3.3. Most of the time browsing with Firefox under SL 3.4 Loop 2b works fine, though.

by **johanPO** » Wed May 30, 2007 19:57

I am also a bit curious about this. Looking in my /varlog messages there is a lot of things (I hope logrotate is enabled by default)

First of all I see this mDNSResponder conflicts alot

May 29 21:42:00 localhost mDNSResponder: Excessive name conflicts (68) for 2.0.168.192.in-addr.arpa. (PTR); rate limiting in effect
May 29 21:42:03 localhost mDNSResponder: Excessive name conflicts (69) for 2.0.168.192.in-addr.arpa. (PTR); rate limiting in effect
May 29 21:42:10 localhost mDNSResponder: Excessive name conflicts (70) for 2.0.168.192.in-addr.arpa. (PTR); rate limiting in effect

I did not use to have that on my Ubuntu machines. In general there was lots less info stored

by **rye_** » Wed May 30, 2007 21:11

hi,

I believe I too have experienced this.

ryan

by **johanPO** » Thu May 31, 2007 9:20

I found out that the mDNSResponder conflicts are caused by Azureus.

by **johanPO** » Thu May 31, 2007 20:38

I think I am getting a bit closer now. To me it looks like it is actually my router that is causing the problem. Somehow I do belive that that is caused by the mDNS functionality.

When I look in the log of my firewall, D-Link DI-524

I did try to activate firestarter and that does change the root cause of this is somewhere in Sabayon. I have had filesharing up and running with this router for several months with Ubuntu and it never crached.

Does anyone know if it isafe to deinstall mDNS? It would at least be worth a try

by **johanPO** » Thu May 31, 2007 20:46

I just had another interesting thing. Somehow it seemed like my PC lost the connection to the router

See below.

johan@localhost ~ $ ping http://www.gmx.de
PING http://www.gmx.de (217.72.204.254) 56(84) bytes of data.

--- http://www.gmx.de ping statistics ---
20 packets transmitted, 0 received, 100% packet loss, time 19003ms

johan@localhost ~ $ sudo ifconfig
eth0 Link encap:Ethernet HWaddr 00:17:31:90:02:4E
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:21

eth1 Link encap:Ethernet HWaddr 00:01:36:0D:CD:BC
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:145390 errors:0 dropped:0 overruns:0 frame:0
TX packets:127021 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:125186805 (119.3 Mb) TX bytes:46750182 (44.5 Mb)
Interrupt:20 Base address:0x4000

sudo dhclient
Internet Systems Consortium DHCP Client V3.0.5-Gentoo-r1
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:17:31:90:02:4e
Sending on LPF/eth0/00:17:31:90:02:4e
Listening on LPF/eth1/00:01:36:0d:cd:bc
Sending on LPF/eth1/00:01:36:0d:cd:bc
Sending on Socket/fallback
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.2 -- renewal in 489447 seconds.

johan@localhost ~ $ sudo ifconfig
eth0 Link encap:Ethernet HWaddr 00:17:31:90:02:4E
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:21

eth1 Link encap:Ethernet HWaddr 00:01:36:0D:CD:BC
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:145396 errors:0 dropped:0 overruns:0 frame:0
TX packets:127026 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:125187501 (119.3 Mb) TX bytes:46752213 (44.5 Mb)
Interrupt:20 Base address:0x4000

johan@localhost ~ $ ping http://www.gmx.de
PING http://www.gmx.de (217.72.204.254) 56(84) bytes of data.
64 bytes from gmx.net (217.72.204.254): icmp_seq=1 ttl=56 time=53.3 ms
64 bytes from gmx.net (217.72.204.254): icmp_seq=2 ttl=56 time=53.0 ms
64 bytes from gmx.net (217.72.204.254): icmp_seq=3 ttl=56 time=52.3 ms

--- http://www.gmx.de ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 52.372/52.904/53.334/0.479 ms

Here the relevant parts from /var/log/messages

May 31 21:43:01 localhost mDNSResponder: mDNSPlatformSendUDP got error 1 (Operation not permitted) sending packet to 224.0.0.251 on in
terface 192.168.0.2/eth1/2
May 31 21:43:01 localhost avahi-daemon[7992]: Withdrawing address record for 192.168.0.2 on eth1.
May 31 21:43:01 localhost avahi-daemon[7992]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.0.2.
May 31 21:43:01 localhost avahi-daemon[7992]: Interface eth1.IPv4 no longer relevant for mDNS.
May 31 21:43:01 localhost avahi-daemon[7992]: Recieved packet from invalid interface.
May 31 21:43:01 localhost avahi-daemon[7992]: Recieved packet from invalid interface.
May 31 21:43:01 localhost avahi-daemon[7992]: Recieved packet from invalid interface.
May 31 21:43:02 localhost avahi-daemon[7992]: Recieved packet from invalid interface.
May 31 21:43:02 localhost dhclient: Listening on LPF/eth0/00:17:31:90:02:4e
May 31 21:43:02 localhost dhclient: Sending on LPF/eth0/00:17:31:90:02:4e
May 31 21:43:02 localhost dhclient: Listening on LPF/eth1/00:01:36:0d:cd:bc
May 31 21:43:02 localhost dhclient: Sending on LPF/eth1/00:01:36:0d:cd:bc
May 31 21:43:02 localhost dhclient: Sending on Socket/fallback
May 31 21:43:03 localhost avahi-daemon[7992]: Recieved packet from invalid interface.
May 31 21:43:05 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
May 31 21:43:05 localhost dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
May 31 21:43:05 localhost dhclient: DHCPACK from 192.168.0.1
May 31 21:43:05 localhost avahi-daemon[7992]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.0.2.
May 31 21:43:05 localhost avahi-daemon[7992]: New relevant interface eth1.IPv4 for mDNS.
May 31 21:43:05 localhost avahi-daemon[7992]: Registering new address record for 192.168.0.2 on eth1.IPv4.
May 31 21:43:05 localhost dhclient: bound to 192.168.0.2 -- renewal in 462557 seconds.

by **johanPO** » Thu May 31, 2007 21:01

And now I have to make a sudo dhclient avery minute or so, I keep getting the same IP adress all the time.... something must very strange here. ( The router is still OK, does not need any reset and I can see that the firewall is blocking some incoming traffic every second or so...)

--------------------- additional info--------

I had a second PC running in parallell (Xubuntu) and it did not disconnect, it kept pinging for an hour without problems

Sabayon Community

Firefox and Opera lost connection

Firefox and Opera lost connection

Who is online