You are not logged in.

#1 2012-08-13 14:22:09

Aldain
Member
Registered: 2012-08-13
Posts: 2

Cabeled Networking via Proxy-Server

Hello everyone

I have a networking problem in my students dorm recently. Network there is provided via cable and a proxyserver. Up until now it has worked without any problems without me changing the default settings in rc.conf. Hence my rc.conf looks like this

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

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
#   Note: Using "localtime" is discouraged, using "" makes hwclock fall back
#   to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
#   Note: if unset, the value in /etc/localtime is used unchanged
# 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.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Berlin"
KEYMAP="dvp"
CONSOLEFONT="Agafari-16"
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
#   Replace every !module by an entry as on the following line in a file in
#   /etc/modprobe.d:
#     blacklist module
#   See "man modprobe.conf" for details.
#
MODULES=(acpi-cpufreq cpufreq_powersave)

# Udev settle timeout (default to 30)
  UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
  USEDMRAID="no"

# Scan for BTRFS volumes at startup
  USEBTRFS="no"

# 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="grandano"

# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
#   - interface: name of device (required)
#   - address: IP address (leave blank for DHCP)
#   - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
#   - broadcast: broadcast address (ignored for DHCP) (optional)
#   - gateway: default route (ignored for DHCP)
# 
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

  interface="eth0"
  address=
  netmask=
  broadcast=
  gateway=
#eth0="dhcp"
#INTERFACES=(eth0)

# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
  NETWORK_PERSIST="no"

# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as 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 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
#
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
#
  DAEMONS=(dbus hwclock syslog-ng network netfs crond bitlbee cupsd @bumblebeed)

Recently it has stopped working, I don't really know why. When I startup Windows, it still works perfectly fine and Wireless Networking in the cafeteria also works.

Here is the result of "dmesg | grep eth0" after bootup

[    5.683320] r8169 0000:05:00.0: eth0: RTL8168evl/8111evl at 0xffffc900059c4000, e0:69:95:f5:f3:d1, XID 0c900800 IRQ 50
[    5.683324] r8169 0000:05:00.0: eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[   11.626721] r8169 0000:05:00.0: eth0: link down
[   11.626806] r8169 0000:05:00.0: eth0: link down
[   11.628242] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   13.287119] r8169 0000:05:00.0: eth0: link up
[   13.288653] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   23.541862] eth0: no IPv6 routers present

and here the result of "grep -C 2 dhcpcd /var/log/everything.log | tail -n 30" after boot

Aug 13 15:28:13 localhost dhcpcd[424]: eth0: sendmsg: Cannot assign requested address
Aug 13 15:28:13 localhost dhcpcd[424]: eth0: broadcasting for a lease
Aug 13 15:28:17 localhost dhcpcd[424]: eth0: sending IPv6 Router Solicitation
Aug 13 15:28:18 localhost dhcpcd[424]: eth0: NAK: from 192.168.2.1
Aug 13 15:28:19 localhost dhcpcd[424]: eth0: sending IPv6 Router Solicitation
Aug 13 15:28:19 localhost dhcpcd[424]: eth0: broadcasting for a lease
Aug 13 15:28:19 localhost dhcpcd[424]: eth0: NAK: from 192.168.2.1
Aug 13 15:28:21 localhost dhcpcd[424]: eth0: sending IPv6 Router Solicitation
Aug 13 15:28:21 localhost dhcpcd[424]: eth0: broadcasting for a lease
Aug 13 15:28:21 localhost dhcpcd[424]: eth0: NAK: from 192.168.2.1
Aug 13 15:28:24 localhost kernel: [   23.541862] eth0: no IPv6 routers present
Aug 13 15:28:25 localhost dhcpcd[424]: eth0: sending IPv6 Router Solicitation
Aug 13 15:28:25 localhost dhcpcd[424]: eth0: sending IPv6 Router Solicitation
Aug 13 15:28:25 localhost dhcpcd[424]: eth0: broadcasting for a lease
Aug 13 15:28:25 localhost dhcpcd[424]: eth0: NAK: from 192.168.2.1
Aug 13 15:28:29 localhost dhcpcd[424]: eth0: sending IPv6 Router Solicitation
Aug 13 15:28:29 localhost dhcpcd[424]: eth0: NAK: from 192.168.2.1
Aug 13 15:28:33 localhost dhcpcd[424]: eth0: sending IPv6 Router Solicitation
Aug 13 15:28:33 localhost dhcpcd[424]: eth0: NAK: from 192.168.2.1
Aug 13 15:28:37 localhost dhcpcd[424]: eth0: sending IPv6 Router Solicitation
Aug 13 15:28:37 localhost dhcpcd[424]: eth0: no IPv6 Routers available
Aug 13 15:28:37 localhost dhcpcd[424]: eth0: NAK: from 192.168.2.1
Aug 13 15:28:41 localhost dhcpcd[424]: eth0: offered 172.16.131.169 from 172.16.128.1
Aug 13 15:28:41 localhost dhcpcd[424]: eth0: NAK: from 192.168.2.1
Aug 13 15:28:42 localhost dhcpcd[424]: eth0: sending IPv6 Router Solicitation
Aug 13 15:28:42 localhost dhcpcd[424]: eth0: broadcasting for a lease
Aug 13 15:28:42 localhost dhcpcd[424]: eth0: NAK: from 192.168.2.1
Aug 13 15:28:42 localhost dhcpcd[424]: timed out
Aug 13 15:28:42 localhost /usr/sbin/crond[535]: (CRON) STARTUP (1.4.8)
Aug 13 15:28:42 localhost /usr/sbin/crond[535]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory

Thank you in advance for any tips,
      max

PS.: I am currently updating in the cafeteria. Maybe this already does the trick.

Offline

#2 2012-08-13 15:02:30

Aldain
Member
Registered: 2012-08-13
Posts: 2

Re: Cabeled Networking via Proxy-Server

Ok, the full system upgrade did not help. In the contrary, it broke part of my graphics driver, yay.
(Written via cell phone)
Greetins

Last edited by Aldain (2012-08-13 15:03:35)

Offline

#3 2012-08-13 23:33:08

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,237
Website

Re: Cabeled Networking via Proxy-Server

Aug 13 15:28:33 localhost dhcpcd[424]: eth0: NAK: from 192.168.2.1
.....
Aug 13 15:28:41 localhost dhcpcd[424]: eth0: offered 172.16.131.169 from 172.16.128.1

You are requesting an address that is not valid on the network; most probably from a previous DHCP on another network. The DHCP server is telling you that it is NOT OK to use that address (NAK). It then offers you 172.16.131.169, but your client refuses to acknowledge and take that lease.

Why dhcpcd is ignoring the lease offer is the real question here... Here's one suggestion to look at:
http://www.linuxquestions.org/questions … ost3536538

Offline

#4 2012-08-14 03:45:42

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,692

Re: Cabeled Networking via Proxy-Server

What is the output of ls -l /var/lib/dhcpcd/

As a workaround, can you try dhclient in lieu of dhcpcd ?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

Board footer

Powered by FluxBB