Netcfg - static eth0 / wlan0 configuration

Hi all,
I am trying to setup a home router with Arch Linux and having some difficulty with network profiles.
eth0 and wlan0 are for my LAN and will be part of the bridge br0
eth1 is the external interface which uses DHCP to get an IP from the cable modem / FIOS box etc.
My problem is, I cannot seem to set the IP address for either wlan0 or eth0.
My configuration looks like:
CONNECTION='ethernet'
DESCRIPTION='internal WLAN'
INTERFACE='wlan0'
IP='static'
ADDR='192.168.2.2'
DNS='127.0.0.1'
I configured it as ethernet because I will use hostapd to serve out wireless from that interface.
What else am I missing?  The ip address is never set and the interface is not brought up.
Walter

I will give that a try, but as far as why the interfaces eth0 and wlan0 are not being set, that appears to be a different problem altogether.
Walter

Similar Messages

  • [SOLVED] netcfg static IP not persisting across reboots in VM

    I ran into an issue with netcfg static IP not persisting across reboots in a VM. I figured it out, but it took me awhile as a brand new user, so I thought I'd post it.
    Setup
    Using VMWare Workstation 8.0.3 build-703057 with bridged networking
    Host OS: Linux Mint 14 64-bit
    Guest OS: Arch Linux 2013.03.01 x86_64
    Given a fresh install on the guest, setup netcfg:
    cd /etc/network.d
    cp examples/ethernet-static ./myprofile
    nano myprofile
    # customize this file. I also added NETMASK='255.255.255.0'
    systemctl enable netcfg@myprofile
    systemctl start netcfg@myprofile
    Test the configuration. It should be successful:
    ping google.com
    Problem
    See if the changes survive a reboot.
    reboot
    ping google.com
    I got the error "connect: Network is unreachable".
    Check the logs:
    journalctl
    G
    I found the following netcfg failure..
    [email protected]: main process exited, code=exited, status=1/FAILURE
    ..prior to the following device initialization:
    kernel: e1000 0000:02:00.0 eth0: Intel(R) PRO/1000 Network Connection
    system-udevd[117]: renamed network interface eth0 to emp2s0
    Solution
    It looks like netcfg is being started before the device it depends on has been initialized. Inform systemd of the
    dependency so they start in the proper order:
    # nano /etc/systemd/system/multi-user.target.wants/[email protected]
    # Add the following to [Unit]. Remember to replace enp2s0 with your device name.
    Requires=sys-subsystem-net-devices-enp2s0.device
    After=sys-subsystem-net-devices-enp2s0.device
    Test again:
    reboot
    ping google.com
    This should now be successful.

    fukawi2 wrote:
    $ man netcfg-profiles wrote:
           Miscellaneous options
               IPCFG
                   Array of arguments to pass to ip. The power of this options is
                   that it allows both simple and complicated routing
                   configurations, within the framework of netcfg.
               SKIPNOCARRIER
                   ‘yes’/‘no’. Don’t abort interface setup if no carrier is
                   found.
    Thank you, [Solved].

  • [SOLVED] eth0-wlan0 AP using bridge AND keep internet access

    Hi there!
    This is my very first post here, so please forgive me if I (unintentionally) violate some rule.
    I have set up my system as an eth0-wlan0 access point with hostapd using a bridge.
    The IP addresses are provided by a separate dhcp-server (router resp. cablemodem).
    My problem is: when I work on the AP I would like to have a working connection to the
    Internet/Router. But to get there I have to execute
    systemctl restart dhcpcd.service
    The AP via the eth0-wlan0 bridge keeps working and I now have a working Internet connection.
    AFAIK the dhcpcd service acts (invoked by netcfg) on the bridge-profile to assign an IP
    to eth0. After that the bridge is set up and (now hostapd.service is up) the wlan0 is
    added to the bridge in AP mode.
    It would be great if someone could point out the problem for me.
    Thx, Benedikt
    Last edited by benedikt (2013-04-30 19:16:43)

    After switching from netcfg to netctl everything worked "out-of-the-box". The bridge gets to be the new standard network interface and all traffic on the machine gets directed through it. YAY

  • [Solved] Ask4 Student Internet, eth0-wlan0 AP using bridge

    Didn't want to 'pollute' the wiki, in case this isn't the best way of doing, what I did; but it caused me enough frustration to not document it.
    Basically, needed to create an access point using a wireless dongle to get my Nexus on the internet (Ask4's wireless routers aren't great ). Also as NAT stuff is "forbidden" on their servers/whatevers, needed to use bridging. Be warned - may kill your system/do funky stuff.
    So...
    1. Need to find out if your dongle is compatible with Master Mode (or AP mode) - loads of websites/wikis on this
    2. Install hostapd (see Arch's wiki)
    3. Create a hostapd.conf file in your home directory (just for testing - the one in /etc/hostapd is 'large'
    #change wlan0 to your wireless device
    interface=wlan0
    driver=nl80211
    ssid=test
    channel=1
    bridge=br0
    4. Create the /etc/network.d/bridge file (see Arch's wiki)
    INTERFACE="br0"
    CONNECTION="bridge"
    DESCRIPTION="Bridge wired and wireless connection"
    # Only add wired interface here, hostapd will add wireless
    BRIDGE_INTERFACES="eth0"
    IP="dhcp"
    #IP="static"
    #ADDR='10.0.0.10'
    #GATEWAY='10.0.0.1'
    #DNS='10.0.0.1'
    To get it to work with Ask4, you need eth0 to have DHCP enabled for this bit
    5. enable and start [email protected]
    6. stop dhcpcd.service
    7. Start hostapd
    hostapd ~/hostapd.conf
    to see if everything works
    8. Try connecting to the network using your device (should work)
    9. Once you've finished using it, kill the hostapd process
    10. Stop [email protected]
    11. Start [email protected] to get the internet working again.
    If everything works, you probably want to go back and edit the hostapd conf to give it some security.
    Useful sites:
    http://nims11.wordpress.com/2012/04/27/ … ess-point/

    After switching from netcfg to netctl everything worked "out-of-the-box". The bridge gets to be the new standard network interface and all traffic on the machine gets directed through it. YAY

  • Netctl will not start my static IP network configuration

    Hi,
    I've never been able to set up a simple static IP configuration for my wired network adapter. Now I need to in order to reset a router I have at home. I use (only) netctl profiles to manage my wireless and wired network connections. I've Googled for solutions to my problem, and the most common solution (disable dhcpcd) does not apply to me, since dhcpcd is not running when I try to enable my static IP profile. Can you guys see what I am doing wrong?
    I ran the following commands to generate debugging information.
    systemctl --type=service --no-pager
    ip addr
    cat /etc/netctl/wired-static
    netctl start wired-static
    systemctl --type=service --no-pager
    systemctl status netctl@wired\x2dstatic.service
    journalctl -x -n 26 --no-pager
    Here is the output.
    [root@fenrir ~]# systemctl --type=service --no-pager
    UNIT LOAD ACTIVE SUB DESCRIPTION
    acpid.service loaded active running ACPI event daemon
    dbus.service loaded active running D-Bus System Message Bus
    [email protected] loaded active running Getty on tty1
    kmod-static-nodes.service loaded active exited Create list of required static device nodes for the
    slim.service loaded active running SLiM Simple Login Manager
    systemd-backlight@backlight:acpi_video0.service loaded active exited Load/Save Screen Backlight Brightness of backlight:
    systemd-backlight@backlight:intel_backlight.service loaded active exited Load/Save Screen Backlight Brightness of backlight
    [email protected] loaded active exited File System Check on /dev/sda1
    [email protected] loaded active exited File System Check on /dev/sda3
    systemd-journald.service loaded active running Journal Service
    systemd-logind.service loaded active running Login Service
    systemd-random-seed.service loaded active exited Load/Save Random Seed
    systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
    [email protected] loaded active exited Load/Save RF Kill Switch Status of rfkill0
    [email protected] loaded active exited Load/Save RF Kill Switch Status of rfkill1
    [email protected] loaded active exited Load/Save RF Kill Switch Status of rfkill2
    [email protected] loaded active exited Load/Save RF Kill Switch Status of rfkill3
    systemd-sysctl.service loaded active exited Apply Kernel Variables
    systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
    systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories
    systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
    systemd-udevd.service loaded active running udev Kernel Device Manager
    systemd-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown
    systemd-user-sessions.service loaded active exited Permit User Sessions
    systemd-vconsole-setup.service loaded active exited Setup Virtual Console
    [email protected] loaded active running User Manager for UID 1000
    LOAD = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB = The low-level unit activation state, values depend on unit type.
    26 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    [root@fenrir ~]# ip addr
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
    2: enp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 20:cf:30:58:d9:30 brd ff:ff:ff:ff:ff:ff
    3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 1c:4b:d6:40:e3:c2 brd ff:ff:ff:ff:ff:ff
    [root@fenrir ~]# cat /etc/netctl/wired-static
    Description='A basic static ethernet connection'
    Interface=enp1s0
    Connection=ethernet
    IP=static
    Address="192.168.1.23/24"
    [root@fenrir ~]# journalctl -x -n 13 --no-pager
    -- Logs begin at Fri 2014-01-10 12:13:41 CET, end at Tue 2014-06-17 16:09:10 CEST. --
    Jun 17 16:08:55 fenrir systemd[1]: Started User Manager for UID 1000.
    -- Subject: Unit [email protected] has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit [email protected] has finished starting up.
    -- The start-up result is done.
    Jun 17 16:08:55 fenrir slim[253]: /usr/bin/xauth: file /home/willard/.Xauthority does not exist
    Jun 17 16:08:55 fenrir slim[253]: setterm: $TERM is not defined.
    Jun 17 16:08:55 fenrir slim[253]: The XKEYBOARD keymap compiler (xkbcomp) reports:
    Jun 17 16:08:55 fenrir slim[253]: > Warning: Symbol map for key <RALT> redefined
    Jun 17 16:08:55 fenrir slim[253]: > Using last definition for conflicting fields
    Jun 17 16:08:55 fenrir slim[253]: > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    Jun 17 16:08:55 fenrir slim[253]: > Ignoring extra symbols
    Jun 17 16:08:55 fenrir slim[253]: Errors from xkbcomp are not fatal to the X server
    Jun 17 16:09:10 fenrir sudo[325]: willard : TTY=pts/0 ; PWD=/home/willard ; USER=root ; COMMAND=/usr/bin/su
    Jun 17 16:09:10 fenrir sudo[325]: pam_unix(sudo:session): session opened for user root by willard(uid=0)
    Jun 17 16:09:10 fenrir su[326]: (to root) willard on pts/0
    Jun 17 16:09:10 fenrir su[326]: pam_unix(su:session): session opened for user root by willard(uid=0)
    [root@fenrir ~]# netctl start wired-static
    Job for netctl@wired\x2dstatic.service failed. See 'systemctl status netctl@wired\x2dstatic.service' and 'journalctl -xn' for details.
    [root@fenrir ~]# systemctl --type=service --no-pager
    UNIT LOAD ACTIVE SUB DESCRIPTION
    acpid.service loaded active running ACPI event daemon
    dbus.service loaded active running D-Bus System Message Bus
    [email protected] loaded active running Getty on tty1
    kmod-static-nodes.service loaded active exited Create list of required static device nodes for th
    ●netctl@wired\x2dstatic.service loaded failed failed Networking for netctl profile wired-static
    slim.service loaded active running SLiM Simple Login Manager
    systemd-backlight@backlight:acpi_video0.service loaded active exited Load/Save Screen Backlight Brightness of backlight
    systemd-backlight@backlight:intel_backlight.service loaded active exited Load/Save Screen Backlight Brightness of backlight
    [email protected] loaded active exited File System Check on /dev/sda1
    [email protected] loaded active exited File System Check on /dev/sda3
    systemd-journald.service loaded active running Journal Service
    systemd-logind.service loaded active running Login Service
    systemd-random-seed.service loaded active exited Load/Save Random Seed
    systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
    [email protected] loaded active exited Load/Save RF Kill Switch Status of rfkill0
    [email protected] loaded active exited Load/Save RF Kill Switch Status of rfkill1
    [email protected] loaded active exited Load/Save RF Kill Switch Status of rfkill2
    [email protected] loaded active exited Load/Save RF Kill Switch Status of rfkill3
    systemd-sysctl.service loaded active exited Apply Kernel Variables
    systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
    systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories
    systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
    systemd-udevd.service loaded active running udev Kernel Device Manager
    systemd-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown
    systemd-user-sessions.service loaded active exited Permit User Sessions
    systemd-vconsole-setup.service loaded active exited Setup Virtual Console
    [email protected] loaded active running User Manager for UID 1000
    LOAD = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB = The low-level unit activation state, values depend on unit type.
    27 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    [root@fenrir ~]# systemctl status netctl@wired\x2dstatic.service
    [email protected] - Networking for netctl profile wiredx2dstatic
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
    Active: inactive (dead)
    Docs: man:netctl.profile(5)
    [root@fenrir ~]# journalctl -x -n 26 --no-pager
    -- Logs begin at Fri 2014-01-10 12:13:41 CET, end at Tue 2014-06-17 16:18:47 CEST. --
    Jun 17 16:08:55 fenrir systemd[1]: Started User Manager for UID 1000.
    -- Subject: Unit [email protected] has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit [email protected] has finished starting up.
    -- The start-up result is done.
    Jun 17 16:08:55 fenrir slim[253]: /usr/bin/xauth: file /home/willard/.Xauthority does not exist
    Jun 17 16:08:55 fenrir slim[253]: setterm: $TERM is not defined.
    Jun 17 16:08:55 fenrir slim[253]: The XKEYBOARD keymap compiler (xkbcomp) reports:
    Jun 17 16:08:55 fenrir slim[253]: > Warning: Symbol map for key <RALT> redefined
    Jun 17 16:08:55 fenrir slim[253]: > Using last definition for conflicting fields
    Jun 17 16:08:55 fenrir slim[253]: > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    Jun 17 16:08:55 fenrir slim[253]: > Ignoring extra symbols
    Jun 17 16:08:55 fenrir slim[253]: Errors from xkbcomp are not fatal to the X server
    Jun 17 16:09:10 fenrir sudo[325]: willard : TTY=pts/0 ; PWD=/home/willard ; USER=root ; COMMAND=/usr/bin/su
    Jun 17 16:09:10 fenrir sudo[325]: pam_unix(sudo:session): session opened for user root by willard(uid=0)
    Jun 17 16:09:10 fenrir su[326]: (to root) willard on pts/0
    Jun 17 16:09:10 fenrir su[326]: pam_unix(su:session): session opened for user root by willard(uid=0)
    Jun 17 16:18:41 fenrir systemd[1]: Starting system-netctl.slice.
    -- Subject: Unit system-netctl.slice has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit system-netctl.slice has begun starting up.
    Jun 17 16:18:41 fenrir systemd[1]: Created slice system-netctl.slice.
    -- Subject: Unit system-netctl.slice has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit system-netctl.slice has finished starting up.
    -- The start-up result is done.
    Jun 17 16:18:41 fenrir systemd[1]: Starting Networking for netctl profile wired-static...
    -- Subject: Unit netctl@wired\x2dstatic.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit netctl@wired\x2dstatic.service has begun starting up.
    Jun 17 16:18:41 fenrir network[442]: Starting network profile 'wired-static'...
    Jun 17 16:18:41 fenrir kernel: atl1c 0000:01:00.0: irq 46 for MSI/MSI-X
    Jun 17 16:18:41 fenrir kernel: IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
    Jun 17 16:18:47 fenrir network[442]: No connection found on interface 'enp1s0' (timeout)
    Jun 17 16:18:47 fenrir network[442]: Failed to bring the network up for profile 'wired-static'
    Jun 17 16:18:47 fenrir systemd[1]: netctl@wired\x2dstatic.service: main process exited, code=exited, status=1/FAILURE
    Jun 17 16:18:47 fenrir systemd[1]: Failed to start Networking for netctl profile wired-static.
    -- Subject: Unit netctl@wired\x2dstatic.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit netctl@wired\x2dstatic.service has failed.
    -- The result is failed.
    Jun 17 16:18:47 fenrir systemd[1]: Unit netctl@wired\x2dstatic.service entered failed state.
    Jun 17 16:18:47 fenrir systemd[1]: Starting Network.
    -- Subject: Unit network.target has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit network.target has begun starting up.
    Jun 17 16:18:47 fenrir systemd[1]: Reached target Network.
    -- Subject: Unit network.target has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit network.target has finished starting up.
    -- The start-up result is done.
    Last edited by willardthor (2014-06-17 14:37:20)

    There is no link. Bring the link up manually and check status with
    ip link set up enp1s0
    ip link enp1s0
    If the link fails to come up (state other than "UP") it is likely a driver issue. If the link comes up (state UP) but status has "NO-CARRIER" it is likely a hardware issue, either one of the endpoints or the cable. First thing I would try in this case is a different cable.
    You can tell netctl to bring the interface up anyway with the option in /etc/netctl/wired-static
    SkipNoCarrier=yes
    However, the interface will not work until the link is fixed.

  • Netcfg/systemd not bringing up eth0 (static profile)

    I installed a fresh copy of Arch on a flash drive that will power my RAID server today. So far, it's almost perfect.
    The issue right now is that in netcfg fails to bring up a static eth0 profile at boot. I've got the netcfg.service enabled and if I do it from the command line, it'll come up without a hassle. Occassionally, it'll give me the "NOHZ: local_softirq_pending 08" error, but it still works. However, nine times out of ten, an error flashes by and the interface never comes up.
    [root@whitebox ~]# systemctl | grep net
    sys-devi...et-eth0.device loaded active plugged RTL8111/8168B PCI Express Gigabit Ethernet controller
    netcfg.service loaded failed failed Netcfg multi-profile daemon
    network.target loaded active active Network
    The unfortunate thing is that I don't have a /var/log/boot file. Also, because I booted with systemd, I can't use inittab to stop Arch from clearing the terminal before presenting the login prompt.
    So, I'm not sure where to go from here. Please give me something to post or read or something. I definitely need to get this to come up reliably at boot, as this'll be a headless unit.

    It failed again today:
    whitebox ~ # systemctl status netcfg.service
    netcfg.service - Netcfg multi-profile daemon
    Loaded: loaded (/usr/lib/systemd/system/netcfg.service; enabled)
    Active: failed (Result: exit-code) since Sun, 19 Aug 2012 12:54:43 -0500; 7min ago
    Process: 208 ExecStart=/usr/bin/netcfg-daemon start (code=exited, status=1/FAILURE)
    CGroup: name=systemd:/system/netcfg.service
    Aug 19 12:54:43 whitebox netcfg-daemon[208]: :: anglednet up Interface eth0 does not exist
    Aug 19 12:54:43 whitebox netcfg-daemon[208]: [fail]
    whitebox ~ #
    And yet...
    whitebox ~ # ls /sys/class/net/
    eth0 lo
    whitebox ~ #
    whitebox ~ # cat /etc/network.d/anglednet
    CONNECTION='ethernet'
    DESCRIPTION='Anglednet static IP for whitebox'
    INTERFACE='eth0'
    IP='static'
    ADDR='192.168.42.2'
    GATEWAY='192.168.42.42'
    DNS=('192.168.42.42')
    whitebox ~ #
    And, of course:
    whitebox ~ # netcfg anglednet
    :: anglednet up [ BUSY ]
    [ 343.246151] NOHZ: local_softirq_pending 08
    [ DONE ]
    whitebox ~ #
    I don't know what that NOHZ bit is about, but it doesn't seem to stand in the way. So, what I've gathered from all of this is that netcfg recognizes eth0 just fine, but somewhere between systemd's netcfg.service and netcfg-daemon, eth0 is invisible.
    Help?

  • SOLVED: Dell XPS 1530 wireless not configured properly , need help.

    Had another post about different questions but after playing around with this for a few days I think that my wifi is not configured properly. Every thing looks good on the hardware and driver end and shows up properly.
    This is my wifi card
    grep -i wireless
    0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
    ifconfig -a
    eth0      Link encap:Ethernet  HWaddr 00:15:C5:84:7A:7C 
              inet addr:162.178.12.101  Bcast:192.168.0.255  Mask:255.255.255.0
              inet6 addr: fe80::215:c5ff:fe84:7a7c/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:6225 errors:0 dropped:0 overruns:0 frame:0
              TX packets:6557 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:4309676 (4.1 Mb)  TX bytes:996746 (973.3 Kb)
              Interrupt:16
    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:6 errors:0 dropped:0 overruns:0 frame:0
              TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:380 (380.0 b)  TX bytes:380 (380.0 b)
    wlan0     Link encap:Ethernet  HWaddr 00:1C:BF:75:0A:1F 
              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)
    wmaster0  Link encap:UNSPEC  HWaddr 00-1C-BF-75-0A-1F-00-00-00-00-00-00-00-00-00-00 
              [NO FLAGS]  MTU:0  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)
    My rc.conf is asfollows.
    # /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="local"
    USEDIRECTISA="no"
    TIMEZONE="America/Toronto"
    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=()
    # 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="archtom"
    # 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 162.178.12.101 netmask 255.255.255.0 broadcast 192.168.0.255"
    INTERFACES=(eth0 wlan0)
    # 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 162.178.12.1"
    #ROUTES=(!gateway)
    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 network netfs crond alsa hal fam gdm)
    Another think is the card is there and recognized but the led light is not on so the card is not actually turning on and that can be an issue so can not scan for networks or even bring wlan0 up as I get this error.
    SIOCSIFFLAGS: No such file or directory
    Your help would be greatly appreciated as though I have used Ubuntu and Fedora for years everything worked out of the box so this is new to me. He he breakage I love Arch , learning so much.
    Last edited by TomWitko (2009-08-23 15:05:33)

    Umm k looking into this and fixing this now. Went by the wiki page for the dell xps 1530 and it stated I needed the 65 driver, just figured out I have the 45 card so need the 45 driver. Will update later when I get it fixed.
    K changed the driver and now can get wlan0 up ,, have to check out if everthing works now.
    Last edited by TomWitko (2009-08-23 14:58:09)

  • Network bridge problems linking wwan0 and eth0 [SOLVED]

    Hi There,
    I have just got working a 3G modem which appears as device wwan0. I am trying to link this interface to my wired ethernet eth0.
    wwan0 seems to work fine with network manager, getting a IP address via dhcp works just fine and I can use the interface.
    However, when I disable network manager and try to bring up the bridge with "netcfg up bridge" it times out, failing to get an lease with dhcp.
    My /etc/network.d/bridge file contains the following:
    INTERFACE="br0"
    CONNECTION="bridge"
    DESCRIPTION="Bridge wired and wireless connection"
    BRIDGE_INTERFACES="eth0 wwan0"
    IP="dhcp"
    #FWD_DELAY=10
    As per the wiki, I have tried using various values for FWD_DELAY (i.e 10 7 5,4,3,2,1,0) but nothing ..
    The relevant sections of /etc/rc.conf are:
    NETWORKS=(bridge)
    DAEMONS=( ... net-profiles !networkmanager ...)
    It seems that DHCP via networkmanager is the only way the interface gets an IP. I even tried "dhcpd br0" or "dhcpd wwan0" and they both time out.
    Anyone have any suggestions?
    Last edited by bmentink (2012-05-15 22:02:00)

    Hi,
    Ok I have this working now, here are the steps I used.
    1. Allowed NetworkManager to setup the 3G Interface wwan0 with DHCP ..
    2. Disabled my eth0 interface from Networkmanager by putting an entry in /etc/Networkmanager/Networkmanager.conf
    3. Manually configured eth0 with a static IP of 192.168.0.1
    4. did the "echo 1 > /proc/sys/net/ipv4/ip_forward" thing for IP forwarding
    5. did the following with iptables:
    iptables -t nat -A POSTROUTING -o wwan0 -j MASQUERADE
    rc.d save iptables
    rc.d start iptables
    6. Connected my wireless router "wan" port to eth0 and configured for 192.168.0.2 IP address and DNS servers dished up from the network  ..
    ( .. looked at the entries in /etc/resolve.conf on the PC I am sharing the internet )
    I can then connect to my wireless lan with my other computers..and on to the internet ... yahoo .. :-)
    The only issue I have with this setup is getting the 3G interface to connect automatically to the network .. I ticked the box in networkmanager, but it doesn't seem to work
    if I reboot the PC or take the usb T stick out and plug back in, I have to manually connect to the network with networkmanager. Does anyone know how to do this automatically ..
    [edit] seems this is a known bug ... you can only auto connect when the interface power is set to "on", but stupidly it defaults to "off"
    Thanks,
    B.
    Last edited by bmentink (2012-05-14 07:56:04)

  • [SOLVED] netcfg fails to add IPv6 gateway

    After updating the (~2-month backlog of) packages on an Arch Linux VPS, I can no longer get netcfg to bring up eth0 with an IPv6 gateway.  However, if I bring up eth0 manually, it works...
    [root@inception ~]# ifconfig
    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 metric 1
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10<host>
    loop txqueuelen 0 (Local Loopback)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    [root@inception ~]# lsmod
    Module Size Used by
    evdev 9370 0
    pcspkr 1819 0
    ext4 374587 1
    crc16 1359 1 ext4
    jbd2 71543 1 ext4
    mbcache 5977 1 ext4
    xen_netfront 17247 0
    xen_blkfront 12625 2
    xenbus_probe_frontend 3239 2 xen_blkfront,xen_netfront
    [root@inception ~]# rc.d start net-profiles
    :: eth0 up [BUSY] RTNETLIN
    K answers: No route to host
    > Adding gateway 2a00:7b80:3008::1 failed
    [FAIL]
    > No profile started.
    [root@inception ~]# ifconfig eth0 up
    [root@inception ~]# rc.d start net-profiles
    :: eth0 up [DONE]
    [root@inception ~]# cat /etc/network.d/eth0
    CONNECTION='ethernet'
    DESCRIPTION='Ethernet 0'
    INTERFACE='eth0'
    IP='static'
    ADDR='xx.xx.xxx.xxx'
    GATEWAY='77.95.224.1'
    IP6='static'
    ADDR6=('xxxx:xxxx:xxxx:x::xxxx:xxxx' 'xxxx:xxxx:xxxx:x::xxxx:xxxx' 'xxxx:xxxx:xxxx:x::xxx
    x:xxxx' 'xxxx:xxxx:xxxx:x::xxx:xxxx' 'xxxx:xxxx:xxxx:x::xxxx:xxxx')
    GATEWAY6='2a00:7b80:3008::1'
    DNS=('8.8.8.8' '8.8.4.4' '2001:4860:4860::8888' '2001:4860:4860::8844')
    [root@inception ~]# uname -a
    Linux inception 3.0.38-1-lts #1 SMP PREEMPT Fri Jul 20 09:22:28 CEST 2012 x86_64 GNU/Linu
    x
    I don't know if I borked something during the package upgrades -- there were those couple announced ones that required minor manual intervention.  Any ideas?
    Last edited by MindlessXD (2013-01-26 16:44:42)

    (I've changed the IP addresses.)
    # cat /etc/network.d/eth0
    INTERFACE="eth0"
    DESCRIPTION="static IP for eth0"
    CONNECTION="ethernet"
    IP="static"
    ADDR="204.51.26.215"
    GATEWAY="204.51.26.1"
    IP6="static"
    ADDR6=(2402:4400:2:16c1::1/64)
    GATEWAY6="2402:4400:2::2"
    # netcfg -v
    netcfg v2.8.3
    # NETCFG_DEBUG="yes" netcfg eth0
    DEBUG: Loading profile eth0
    DEBUG: Configuring interface eth0
    :: eth0 up DEBUG: status reported to profile_up as:
    DEBUG: Loading profile eth0
    DEBUG: Configuring interface eth0
    DEBUG: ethernet_up ifup
    DEBUG: ethernet_up ip addr add 204.51.26.215/24 brd + dev eth0
    DEBUG: ethernet_up ip route add default via 204.51.26.1 dev eth0
    DEBUG: ethernet_up ip -6 addr add 2402:4400:2:16c1::1/64 dev eth0
    DEBUG: ethernet_up ip -6 route replace default via 2402:4400:2::2 dev eth0
    DEBUG: ethernet_up ip -6 addr show dev eth0 tentative
    DEBUG: ethernet_up hostname galloway
    [done]
    # netcfg -v
    netcfg v2.8.8
    # NETCFG_DEBUG="yes" netcfg eth0
    DEBUG: Loading profile eth0
    DEBUG: Configuring interface eth0
    :: eth0 up DEBUG: status reported to profile_up as:
    DEBUG: Loading profile eth0
    DEBUG: Configuring interface eth0
    DEBUG: ethernet_up bring_interface up eth0
    DEBUG: ethernet_up ip addr add 204.51.26.215/24 brd + dev eth0
    DEBUG: ethernet_up ip route add default via 204.51.26.1 dev eth0
    DEBUG: ethernet_up ip -6 addr add 2402:4400:2:16c1::1/64 dev eth0
    DEBUG: ethernet_up ip -6 route replace default via 2402:4400:2::2 dev eth0
    RTNETLINK answers: No route to host
    Adding gateway 2402:4400:2::2 failed
    DEBUG: profile_up connect failed
    [fail]

  • [SOLVED] netcfg: unable to add gateway on boot when using ipv6

    I'm using netcfg to start two interfaces. The first, eth0, is configured with IPv6 in its profile, and for some reason does not start on boot but throws an error. (note: I've changed the real addresses to mask them.)
    :: eth0 up [BUSY]
    [ 4.622278] NET: Registered protocol family 10
    RTNETLINK answers: No route to host
    > Adding gateway 1234:5678:2::2 failed
    [FAIL]
    The strange thing is that, after boot, I can easily do a `/etc/rc.d/net-profiles restart` or `netcfg up eth0`, and eth0 works fine. Any suggestions? Here's my eth0 profile.
    CONNECTION='ethernet'
    INTERFACE='eth0'
    IP='static'
    ADDR='123.123.123.12'
    GATEWAY='123.123.123.1'
    IP6='static'
    ADDR6='1234:5678:2:9012::1/64'
    GATEWAY6='1234:5678:2::2'
    Last edited by anonova (2011-09-27 17:14:25)

    Have you already gone through these instructions:
    https://wiki.archlinux.org/index.php/IP … ic_Address

  • Netcfg - no connection, interface without devices connected

    I have two interfaces eth0, eth1
    eth0 (DHCP) - connect to router, provide internet
    eth1 (STATIC IP) - connect with print server in my printer
    - I expect interface should up without need to have powered on device connected to it
    Everything worked fine, when interfaces were configured with /etc/rc.conf.
    Now I configured network with netcfg and:
    eth0 - up and everything ok
    eth1 - no starts up, when no device is connected (powered off device connected) to this ethernet card
    log:
    # NETCFG_DEBUG="yes" netcfg eth1-static
    DEBUG: Loading profile eth1-static
    DEBUG: Configuring interface eth1
    :: eth1-static up [BUSY] DEBUG: status reported to profile_up as:
    DEBUG: Loading profile eth1-static
    DEBUG: Configuring interface eth1
    DEBUG: ethernet_iproute_up ifup
    > No connection
    DEBUG: profile_up connect failed
    but when printer is powered on, interface starts up:
    # netcfg eth1-static
    :: eth1-static up [DONE]
    network profile content
    # cat /etc/network.d/eth1-static
    CONNECTION='ethernet'
    DESCRIPTION='A basic static ethernet connection using iproute'
    INTERFACE='eth1'
    IP='static'
    ADDR='192.168.0.1'
    Am I missing some setting? Maybe I should disable/enable something in profile?
    Things to reproduce:
    1. two ethernet cards
    2. first connected network and second  connected to switched off device, or not connected
    3. configure 2 netcfg profiles (first - dhcp, second -static ip)
    4. the second interface will fail to start up
    Last edited by ostanislaw (2011-06-18 10:31:12)

    Now I configured second interface - eth1 the old way in /etc/rc.conf:
    eth1="eth1 192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255 mtu 1492"
    INTERFACES=(eth1)
    While eth0 is configured by netcfg profile.
    Both interfaces works. But my problem is not solved, because both interface should be configured in netcfg.
    I think netcfg check if network is available and doesn't start eth1 interface, while device configured the old way in /etc/rc.conf doesn't perform this check. There should be option to disable it in netcfg profile.
    Last edited by ostanislaw (2011-06-18 10:44:18)

  • Netcfg - wpa issue

    Hi all,
    few updates ago netcfg switched to 2.5.2, but now i'm in trouble; a previous post highlights the same
    problem: netcfg seems to be forced on WPA authentication even when i set SECURITY=none, but he
    resolves downgrading netcfg from rc2 to a stable release, now 2.5.2 is in core so downgrading couldn't
    be permitted ;-)
    DEBUG: Loading profile 3-wifi-home
    DEBUG: Configuring interface wlan0
    :: 3-wifi-home up [BUSY] DEBUG: status reported to profile_up as:
    DEBUG: Loading profile 3-wifi-home
    DEBUG: Configuring interface wlan0
    DEBUG: wireless_up stop_wpa wlan0
    DEBUG: wireless_up ifup
    DEBUG: wireless_up Configuration generated at /tmp/wpa.wlan0/wpa.conf
    DEBUG: wireless_up start_wpa wlan0 /tmp/wpa.wlan0/wpa.conf wext
    DEBUG: wireless_up wpa_check
    > WPA Authentication/Association Failed
    DEBUG: profile_up connect failed
    [FAIL]
    my profile:
    CONNECTION="wireless"
    DESCRIPTION="Static IP wlan0 [home]"
    INTERFACE="wlan0"
    SECURITY="none"
    SCAN="no"
    ESSID="ff0000-wifi"
    MODE="managed"
    CHANNEL="11"
    IP="static"
    IFOPTS="192.168.0.31 netmask 255.255.255.0 broadcast 192.168.0.255"
    GATEWAY="192.168.0.1"
    DNS=("192.168.0.1" "85.37.17.44")
    and finally the tool's version:
    Name : netcfg
    Version : 2.5.2-1
    URL : http://archlinux.org
    Licenses : BSD
    Groups : None
    Provides : None
    Depends On : wireless_tools coreutils wpa_supplicant>=0.6.8 net-tools
    dhcpcd>=4.0 iproute2
    Optional Deps : dialog: Required for menu based profile selector
    wpa_actiond: Required for automatic wireless connection with
    rc.d/net-auto-wireless
    ifplugd: Required for automatic wired connection with rc.d/net-auto-wired
    Required By : None
    Conflicts With : None
    Replaces : None
    Installed Size : 268.00 K
    Packager : James Rayner <[email protected]>
    Architecture : any
    Build Date : Thu 18 Feb 2010 10:14:45 AM CET
    Install Date : Thu 18 Feb 2010 03:57:23 PM CET
    Install Reason : Explicitly installed
    Install Script : No
    Description : Network configuration and profile scripts
    Any hints?
    Cheers,
    ff0000

    Okay, some more googling pinpointed the source of the intermittent network connectivity: I haven't been killing off the old wpa_supplicant processes. But, I'm still getting the same netcfg errors when I start clean with no dhcpcd's or wpa_supplicant's running.
    If I watch the processes that are running while netcfg tries to start, I see wpa_supplicant being called correctly (with just an extra -P /var/path/to/some/file.pid compared to what I'm running), but dhcpcd doesn't start at all. Does anone know what's going on between those two commands?

  • Issue with eth0 interface

    Have a rh9 system, with /etc/sysconfig/network-scripts/ifcfg-eth0 contents :
    DEVICE=eth0
    IPADDR=140....
    NETMASK=255.255.254.0
    BROADCAST=140...
    GATEWAY=140....
    BOOTPROTO=static
    ONBOOT=yes
    During system bootup, eth0 never comes up automatically. "service network status" shows eth0 in "configured devices" only, not in "currently active devices".
    "chkconfig --list network" shows :
    network 0:off 1:off 2:on 3:on 4:on 5:on 6:off
    After bootup, typing "service network reload" from command line activates eth0. Not sure what else could be stopping eth0 from coming up automatically upon reboot.
    Any suggestions ? Thanks.

    hi
    Try "dmesg|more" look for you dev(eth0 ) see if the is any errors anound it
    Gilles

  • [SOLVED] wlan0 error

    I've spent more time then I'm willing to say trying to get my WiFi to work on our internal network.
    $ ifconfig
    eth0 Link encap:Ethernet HWaddr E0:CB:4E:B9:07:D1
    inet addr:192.168.80.253 Bcast:0.0.0.0 Mask:255.255.255.0
    inet6 addr: fe80::e2cb:4eff:feb9:7d1/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1570054 errors:0 dropped:23 overruns:0 frame:0
    TX packets:1324161 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1024247817 (976.7 Mb) TX bytes:205585920 (196.0 Mb)
    Interrupt:41 Base address:0x8000
    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:1055 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1055 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:105498 (103.0 Kb) TX bytes:105498 (103.0 Kb)
    wlan0 Link encap:Ethernet HWaddr 00:02:6F:93:F7:D8
    inet addr:10.1.10.11 Bcast:10.1.10.255 Mask:255.255.255.0
    inet6 addr: fe80::202:6fff:fe93:f7d8/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1331532 errors:1 dropped:1 overruns:0 frame:0
    TX packets:28528 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:422361648 (402.7 Mb) TX bytes:1679791 (1.6 Mb)
    $ iwconfig
    lo no wireless extensions.
    eth0 no wireless extensions.
    wlan0 Ralink STA ESSID:"<hidden>" Nickname:"RT2870STA"
    Mode:Managed Frequency=2.412 GHz Access Point: 1C:AF:F7:73:7C:F7
    Bit Rate=54 Mb/s
    RTS thr:off Fragment thr:off
    Link Quality=100/100 Signal level:-33 dBm Noise level:-71 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0
    $ iwlist scan
    lo Interface doesn't support scanning.
    eth0 Interface doesn't support scanning.
    wlan0 Scan completed :
    Cell 01 - Address: 1C:AF:F7:73:7C:F7
    Protocol:802.11b/g/n
    ESSID:"<hidden>"
    Mode:Managed
    Channel:1
    Quality:100/100 Signal level:-35 dBm Noise level:-71 dBm
    Encryption key:on
    Bit Rates:144 Mb/s
    IE: WPA Version 1
    Group Cipher : TKIP
    Pairwise Ciphers (2) : CCMP TKIP
    Authentication Suites (1) : PSK
    IE: IEEE 802.11i/WPA2 Version 1
    Group Cipher : TKIP
    Pairwise Ciphers (2) : CCMP TKIP
    Authentication Suites (1) : PSK
    Any way to debug error indicated in ifconfig? Windows and OSX users in our office are able to successfully connect.
    Setup facts:
    I have set a static IP for eth0 in rc.conf, it shouldn't matter though.
    I am using NetworkManager with 2 dispatch scripts to bring up sshfs and smbnetfs.
    I have set immutable bit on resolv.conf because NM kept overriding it with crappy nameservers.
    I have tried many setting combinations in Network Setting window.
    Our network is partly managed by third party.
    Will update when I remember more...
    Thank you
    Last edited by mpz (2011-08-08 13:19:15)

    Thanks for your help fellas, I appreciate it.
    @karol
    Yes, wireless dongle is up and running and I can connect to the network, I get assigned an IP and I can ping my gateway but none of the domains resolve.
    @ewaller
    Which client are you referring to? I tried to use NetworkManager to setup my wireless connection without success. Please elaborate and I'll post what you need. IP comes from Comcast via DHCP, it's our outside line for redundancy.
    @tomk
    Yes, I need 2 lines though not simultaneously. Even when I disable eth0, wlan0 doesn't resolve domain names.
    Edit: Getting close
    I removed immutable bit from resolv.conf to see what DNS NM would set for this connection. With it set, Comcast resolves. I added back google nameservers (so that eth0 can resolve quickly) and now both connections work but comcast resolves slowely (its nameserver is last after 2 google nameserver in the order). Is there any way to assign DNS based on interface? I checked man resolve and didn't see any options. Thanks again!

  • [SOLVED-ISH] ipv6 dropping intermittently, fixed with netcfg -r

    So ipv6 connectivity drops randomly, without any interruption to ipv4.
    I'm not really sure what logs to look into to check what the real error is.
    However, a netcfg -r eth0 immediately after it drops out reconnects me to ipv6, and nobody else on the same network+host machine has the same issue. Therefore I'm assuming that this has something to do with my system. I'm running arch in a KVM.
    Any ideas? Right now I just have a script running on cron that checks if ipv6 connectivity is broken and does netcfg -r, but obviously this isn't a valid solution.
    This is what my profile looks like:
    CONNECTION='ethernet'
    DESCRIPTION='ipv6+ipv4 eth0'
    INTERFACE='eth0'
    IP=static
    ADDR=69.85.88.224
    NETMASK=24
    ROUTES=
    GATEWAY=69.85.88.1
    IP6=static
    ADDR6=(2606:df00:2::290c:6232/64 2606:df00:2::52c9:3080/64 2606:df00:2::a81:cb82/64 2606:df00:2::a1ac:9470/64 2606:df00:2::3ef6:a7e3/64)
    (the gateway specified in ipv4 is the same router for ipv6)
    Thanks.
    [EDIT] I just checked my irc logs and it looks like it drops every 30 minutes on the hour and half hour, but there's nothing in crontab.
    Last edited by kbar (2012-04-30 03:39:03)

    found the issue.
    https://bugs.archlinux.org/task/28887?s … &closedto=
    should fix it. meanwhile i manually changed the default route to add the ipv6 gateway.

Maybe you are looking for