You are not logged in.

#1 2009-08-18 15:49:01

hypnotic_meat
Member
Registered: 2009-04-15
Posts: 32

mklarch issues and 100% packet loss [SOLVED]

I'm trying to use the mklarch tool to make a bootable arch linux cd, and when I run the ./mklarch -p <profile> command, the package databases get synchronized without problem, but it fails when trying to install selected packages:

libdownload package not found, searching for group...
error: 'libdownload': not found in sync db

I did some digging and it turns out that libdownload was replaced by libfetch, so I tried replacing it and it failed on hwd.  I figured I wasn't getting all the packages from the ftp mirrors, so to test my network, I pinged www.google.com and came back with 100% package loss:

PING www.1.google.com (64.233.161.147) 56(84) bytes of data.
38 packets transmitted, 0 received, 100% packet loss, time 36999ms

I checked rc.conf and ran /sbin/ifconfig: all the details are correct, and the network is being detected correctly.  Does anyone have any suggestions on what might be causing the 100% packet loss?  I'm not very well versed in networking...at all.

Any help is greatly appreciated.

Last edited by hypnotic_meat (2009-08-19 19:26:38)

Offline

#2 2009-08-18 16:45:05

perbh
Member
From: Republic of Texas
Registered: 2005-03-04
Posts: 765

Re: mklarch issues and 100% packet loss [SOLVED]

Hmmm - other than stating the obvious (your dns is working or you wouldn't have the google ipaddy), can you post the output of 'ifconfig' ?

Usually when this kind of things happens - its a lack of dns-server (/etc/resolv.conf) and/or a wrong /etc/hosts (though in the latter case, you would just have a loooong timeout ...). You better post your two /etc files as well ...

[edit]
Also - can you ping your gateway? (usually 192.168.0.1 or 192.168.1.1)
On 2nd thought - gateway must be ok since you can access the dns-server ...

Last edited by perbh (2009-08-18 16:46:57)

Offline

#3 2009-08-18 18:06:58

hypnotic_meat
Member
Registered: 2009-04-15
Posts: 32

Re: mklarch issues and 100% packet loss [SOLVED]

Thanks for the reply.  First, the rc.conf file:

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="EST"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(natsemi ac97_bus snd-mixer-oss snd-pcm-oss snd-page-alloc snd-pcm snd-timer snd snd-ac97-codec snd-ali5451 soundcore)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="live"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth0="eth0<IP> netmask 255.255.255.0 broadcast <BROADCAST IP>"
INTERFACES=(eth0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw <GATEWAY IP>"
ROUTES=(gateway)
 
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng dbus hal network netfs crond cups)

Next, the hosts file:

#
# /etc/hosts: static lookup table for host names
#

#<ip-address>    <hostname.domain.org>    <hostname>
127.0.0.1    localhost.localdomain    localhost
<IP>  live.<my-domain>    live

# End of file

Last, here's the output of ifconfig:

eth0      Link encap:Ethernet  HWaddr <HW>  
          inet addr:<IP>  Bcast:<BROADCAST IP>  Mask:255.255.255.0
          inet6 addr: <IPV6> Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:878 errors:0 dropped:0 overruns:0 frame:0
          TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:79940 (78.0 Kb)  TX bytes:7060 (6.8 Kb)
          Interrupt:10 Base address:0x6000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:54 errors:0 dropped:0 overruns:0 frame:0
          TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4592 (4.4 Kb)  TX bytes:4592 (4.4 Kb)

I removed all the actual addresses and replaced them with appropriate labels.  But I checked them all before doing so and everything matches up correctly.

Hope this helps.

Offline

#4 2009-08-19 03:55:57

perbh
Member
From: Republic of Texas
Registered: 2005-03-04
Posts: 765

Re: mklarch issues and 100% packet loss [SOLVED]

Hmmm - I cant see anything out-of-the-usual here - other than a missing space between eth0 and ipaddy in /etc/rc.conf, but then that could have happened when you edited it ...
I appreciate your wish to remain anonymous, but if your addresses are in the 192.168-range - then just about _everyone_ have the same! The reason being simply that these are non-web addresses which means that any router you have will have 192.168.something (usually 192.168.0.1) on _your_ side and something else (provided by your isp) on the 'outside'

Have you tried to ping your gateway?
Have you tried to ping your nameserver? (you can find it in /etc/resolv.conf)
Sometimes a router will be set up to stop ping-packets (my employer does that, so it means I cant ping anything on the www from work).

Do you have any firewalls set up? Any proxies?

Is there anything in /etc/hosts.deny and /etc/hosts.allow (though these have more to do about others reaching _you_, not you reaching out ...)

Offline

#5 2009-08-19 19:26:26

hypnotic_meat
Member
Registered: 2009-04-15
Posts: 32

Re: mklarch issues and 100% packet loss [SOLVED]

I talked to my network administrator and there was a firewall setup blocking the incoming packets.  Thanks for all your help, marking this one as solved.

Offline

Board footer

Powered by FluxBB