Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 104701 - Major networking issues after "emerge world"
Summary: Major networking issues after "emerge world"
Status: VERIFIED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: AMD64 Linux
: Highest blocker (vote)
Assignee: Konstantin Arkhipov (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-03 04:38 UTC by Jason Cox
Modified: 2006-01-03 22:48 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Cox 2005-09-03 04:38:51 UTC
I have just emerged world only to find networking issues with varring apps.. 
I can run command line tools like nslookup and they work fine, but tools like 
wget, emerge, evolution and firefox do not work and always resolve addresses 
to 1.0.0.0 
In order to get around the problem I have started to manualy 
populate /etc/hosts and to do nslookup's before requesting sites for emerge or 
firefox. Any nslookup only lasts for 60 seconds sice last ip use. ( konqueror 
dosn't suffer and has work regardless )  
I have tried 2005.1 version and an emerge world but with no differace. 
my /etc/resolve only has one line in it pointing to my adsl gateway, which 
other pc's are using with out problems. 
have also run etc-update 
 
thanks  
Jason Cox
Comment 1 Carsten Lohrke (RETIRED) gentoo-dev 2005-09-03 05:22:17 UTC
"I did 'emerge world' and now FOO doesn't work" isn't really a usable bug
report, but more a cry for help. Did you at least ask for help in
forums.gentoo.org or the gentoo-user mailinglist, before filing this bug?
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2005-09-03 11:58:28 UTC
/etc/resolve - hmm, but it should be /etc/resolv.conf

This is not a bug. 
Comment 3 Jason Cox 2005-09-03 14:29:00 UTC
sorry but I ment /etc/resolv.conf and like I said it is only some software that 
has been affected with resolving all named to an ip addr of 1.0.0.0 
Comment 4 Jakub Moc (RETIRED) gentoo-dev 2005-09-03 15:06:54 UTC
So post some useful relevant information. Also, this is really not a support forum.
Comment 5 Jason Cox 2005-09-03 15:38:13 UTC
This appears it might be a bind issue 
the log show *LOTS* of the following ( has restart in the middle ) 
Bind 9.3.1 
 
Sep  4 08:28:49 globelock named[9254]: unexpected end of input resolving 
'A.ROOT-SERVERS.NET/AAAA/IN': 193.0.14.129#53 
Sep  4 08:28:49 globelock named[9254]: unexpected end of input resolving 
'A.ROOT-SERVERS.NET/AAAA/IN': 128.63.2.53#53 
Sep  4 08:28:49 globelock named[9254]: unexpected end of input resolving 
'A.ROOT-SERVERS.NET/AAAA/IN': 192.228.79.201#53 
Sep  4 08:28:49 globelock named[9254]: unexpected end of input resolving 
'A.ROOT-SERVERS.NET/AAAA/IN': 202.12.27.33#53 
Sep  4 08:28:49 globelock named[9254]: unexpected end of input resolving 
'A.ROOT-SERVERS.NET/AAAA/IN': 192.33.4.12#53 
Sep  4 08:28:49 globelock named[9254]: unexpected end of input resolving 
'A.ROOT-SERVERS.NET/AAAA/IN': 192.5.5.241#53 
Sep  4 08:28:49 globelock named[9254]: unexpected end of input resolving 
'A.ROOT-SERVERS.NET/AAAA/IN': 192.36.148.17#53 
Sep  4 08:28:49 globelock named[9254]: unexpected end of input resolving 
'A.ROOT-SERVERS.NET/AAAA/IN': 192.58.128.30#53 
Sep  4 08:28:49 globelock named[9254]: unexpected end of input resolving 
'A.ROOT-SERVERS.NET/AAAA/IN': 218.214.227.3#53 
Sep  4 08:28:49 globelock named[9254]: unexpected end of input resolving 
'A.ROOT-SERVERS.NET/AAAA/IN': 202.154.83.53#53 
Sep  4 08:30:01 globelock cron[9272]: (root) CMD (test -x /usr/sbin/run-crons 
&& /usr/sbin/run-crons ) 
Sep  4 08:30:55 globelock kernel: process `nslookup' is using obsolete 
setsockopt SO_BSDCOMPAT 
Sep  4 08:33:29 globelock named[9254]: shutting down 
Sep  4 08:33:29 globelock named[9254]: stopping command channel on 
127.0.0.1#953 
Sep  4 08:33:29 globelock named[9254]: stopping command channel on ::1#953 
Sep  4 08:33:29 globelock named[9254]: no longer listening on 127.0.0.1#53 
Sep  4 08:33:29 globelock named[9254]: exiting 
Sep  4 08:33:35 globelock named[9417]: starting BIND 9.3.1 -u named -n 1 
Sep  4 08:33:35 globelock named[9417]: loading configuration from 
'/etc/bind/named.conf' 
Sep  4 08:33:35 globelock named[9417]: listening on IPv4 interface lo, 
127.0.0.1#53 
Sep  4 08:33:35 globelock named[9417]: command channel listening on 
127.0.0.1#953 
Sep  4 08:33:35 globelock named[9417]: command channel listening on ::1#953 
Sep  4 08:33:35 globelock named[9417]: zone 127.in-addr.arpa/IN: loaded serial 
2002081601 
Sep  4 08:33:35 globelock named[9417]: zone localhost/IN: loaded serial 
2002081601 
Sep  4 08:33:35 globelock named[9417]: running 
Sep  4 08:34:21 globelock kernel: device eth0 left promiscuous mode 
Sep  4 08:34:21 globelock kernel: device lo left promiscuous mode 
Sep  4 08:34:44 globelock named[9417]: unexpected end of input resolving 
'mail.multiskilled.com.au/AAAA/IN': 218.214.227.3#53 
Sep  4 08:34:56 globelock named[9417]: unexpected end of input resolving 
'mail.multiskilled.com.au/AAAA/IN': 128.8.10.90#53 
Sep  4 08:34:56 globelock named[9417]: unexpected end of input resolving 
'mail.multiskilled.com.au/AAAA/IN': 128.63.2.53#53 
Sep  4 08:34:56 globelock named[9417]: unexpected end of input resolving 
'mail.multiskilled.com.au/AAAA/IN': 192.228.79.201#53 
Sep  4 08:34:56 globelock named[9417]: unexpected end of input resolving 
'mail.multiskilled.com.au/AAAA/IN': 192.33.4.12#53 
Sep  4 08:34:56 globelock named[9417]: unexpected end of input resolving 
'mail.multiskilled.com.au/AAAA/IN': 198.41.0.4#53 
 
 
 
 
Comment 6 Jakub Moc (RETIRED) gentoo-dev 2005-09-04 02:56:05 UTC
Hmm, assigning to bind maintainers.
Comment 7 Jason Cox 2005-09-06 00:25:58 UTC
More info on bug. It appears in the stage3 install from the universal install
for amd64 2005.1
In order to install, once agin I must ping distfiles.gentoo.org which gives me
an ip address and all works.However after the cache expires(10 mins aprox) It
all stop agin and I must ping again.
Comment 8 Jason Cox 2005-09-06 19:30:32 UTC
tracked down problem to ipv6. after setting a USE variable to -ipv6 and
reemergeing world with --deep --newuse the probel is solved and all ip addresses
can now be resolved.

The problem only exists when ipv6 and ipv4 are use on an ipv4 only network.
hope this helps.

will leave this bug open for bind group to close once solution is found


THIS AFFECTS GENTOO BASE INSTALL !!!!!
Comment 9 Konstantin Arkhipov (RETIRED) gentoo-dev 2006-01-03 15:16:46 UTC
i can't reproduce this issue with bind-9.3.2 built with ipv6 support on ipv4-only network.

please, provide your `emerge info` output and your named.conf, if you're still able to reproduce it.
Comment 10 Jason Cox 2006-01-03 22:48:34 UTC
over Xmas I pulled down the system and found that the cause was to do with a router. This router was alowing M$ to work fine but scrambling Linux. I don't know how or why but it is now replaced.