New rc.conf file ?

skanky · 2011-06-09 08:38:39

Ah thanks. I'm using netcfg so it must be something specific to how that's set up as my settings look the same except I also have NETWORKS set (as can be seen above).
I'll keep looking.

igndenok · 2011-06-09 08:47:35

Got some problem with network connection (can't connect internet), I use static IP no netcfg.
Need to configure broadcast address on /etc/rc.d/network

/usr/sbin/ip addr add $address/$netmask broadcast $broadcast dev $interface || return 1

And to /etc/rc.conf

broadcast=192.168.1.255

to make my problem go away. Hope this help some people

Varg · 2011-06-09 09:03:00

skanky wrote:

Ah thanks. I'm using netcfg so it must be something specific to how that's set up as my settings look the same except I also have NETWORKS set (as can be seen above).
I'll keep looking.

No problems here with netcfg. I even left the interface part blank. Tested with filling in eth0 and even wlan0 but that gave no problems either.
I also have networks configured ( only one though ) but I use net-profiles in my daemons array and not net-auto-wired/wireless.

skanky · 2011-06-09 09:34:15

Varg wrote:

skanky wrote:
Ah thanks. I'm using netcfg so it must be something specific to how that's set up as my settings look the same except I also have NETWORKS set (as can be seen above).
I'll keep looking.
No problems here with netcfg. I even left the interface part blank. Tested with filling in eth0 and even wlan0 but that gave no problems either.
I also have networks configured ( only one though ) but I use net-profiles in my daemons array and not net-auto-wired/wireless.

Thanks for the information. I have just tried rebooting with the interface not set, in case that was the issue, but no change.

whitetimer · 2011-06-09 11:03:25

Varg wrote:

skanky wrote:
Ah thanks. I'm using netcfg so it must be something specific to how that's set up as my settings look the same except I also have NETWORKS set (as can be seen above).
I'll keep looking.
No problems here with netcfg. I even left the interface part blank. Tested with filling in eth0 and even wlan0 but that gave no problems either.
I also have networks configured ( only one though ) but I use net-profiles in my daemons array and not net-auto-wired/wireless.

@ Varg
I use netcfg and i'm still having problems with my wireless network starting at boot. It works great when i manually start it. Can you post your network settings in rc.conf so i can see how you have yours ... Cheers

Varg · 2011-06-09 12:18:38

whitetimer wrote:

@ Varg
I use netcfg and i'm still having problems with my wireless network starting at boot. It works great when i manually start it. Can you post your network settings in rc.conf so i can see how you have yours ... Cheers

Sure

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

# 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)
#   - gateway: default route (ignored for DHCP)
# 
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=
address=
netmask=
gateway=

# 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=(home)

# -----------------------------------------------------------------------
# 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=(!hwclock syslog-ng dbus !network @acpid @iptables !wicd @net-profiles @crond @alsa @ntpd @cups @vnstat)

As you can see nothing special actually. I backed up my old rc.conf, copy rc.conf.pacnew to rc.conf and put all my modules and daemons in it, setting hostname, etc,...

Speek · 2011-06-09 12:32:46

Why are the new variable names lowercase?

MadCatMk2 · 2011-06-09 12:35:36

Speek wrote:

Why are the new variable names lowercase?

lowercase > uppercase

martinoff · 2011-06-09 12:36:33

everything working ok for me with the new file (i use wicd )

#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=eth0
address=
netmask=255.255.255.0
gateway=my.router.getaway

whitetimer · 2011-06-09 14:35:17

Varg wrote:

whitetimer wrote:

@ Varg
I use netcfg and i'm still having problems with my wireless network starting at boot. It works great when i manually start it. Can you post your network settings in rc.conf so i can see how you have yours ... Cheers

Sure

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

# 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)
#   - gateway: default route (ignored for DHCP)
# 
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=
address=
netmask=
gateway=

# 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=(home)

# -----------------------------------------------------------------------
# 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=(!hwclock syslog-ng dbus !network @acpid @iptables !wicd @net-profiles @crond @alsa @ntpd @cups @vnstat)

As you can see nothing special actually. I backed up my old rc.conf, copy rc.conf.pacnew to rc.conf and put all my modules and daemons in it, setting hostname, etc,...

Thanks Varg, thats similar to mine ... Just annoying that most of the time i have to manually start my netcfg connection ... heigh ho, at least it works )

ConnorBehan · 2011-06-09 19:43:11

Inxsible wrote:

Hmmm I seem to be the lucky one then ?

Me too. I did not have to change anything to keep using net-profiles. Nor did I see a warning message saying that I would have to. Just the one about blacklisting modules.

Inxsible · 2011-06-09 19:47:47

Baah !!

And here I was...thinking that I was special

I have now updated my rc.conf to the newer one. You best be doing that too Connor.

skanky · 2011-06-09 21:00:28

Not sure if this is related, but my system clock is an hour ahead when I boot. I start nntp when I connect and that fixes it, so it may always have been like that but the automatic connection meant that it was fixed before logging on. Anyway, has anyone got it working with net-auto-wired and/or net-auto-wireless?

karol · 2011-06-09 21:02:51

skanky wrote:

Not sure if this is related, but my system clock is an hour ahead when I boot. I start nntp when I connect and that fixes it, so it may always have been like that but the automatic connection meant that it was fixed before logging on.

Start a thread and post some info about your settings, especially timezone and hwclock.

skanky · 2011-06-09 21:13:11

karol wrote:

skanky wrote:
Not sure if this is related, but my system clock is an hour ahead when I boot. I start nntp when I connect and that fixes it, so it may always have been like that but the automatic connection meant that it was fixed before logging on.
Start a thread and post some info about your settings, especially timezone and hwclock.

Yeah sorry, I was thinking about doing that - I just mention it here as it is controlled by an rc.conf setting and *may* be connected. I'll do that when I've fixed the network issue.

Last edited by skanky (2011-06-09 21:20:40)

lilsirecho · 2011-06-09 22:39:57

There used to be quotes on the entries for the network data. Are these not necessary any more?

Arashi · 2011-06-10 02:20:37

Ok, so for those of us who DO need more than one WIRED interface, what do we do?

(Yes, I promise, there are those of us out there who DO use more than one nic...)

Left scratching my head here on this one, as far as I can tell, there's no easy way to configure more than one nic.

(Yes, I get that the 'old' method works)

thestinger · 2011-06-10 02:22:02

Arashi wrote:

Ok, so for those of us who DO need more than one WIRED interface, what do we do?
(Yes, I promise, there are those of us out there who DO use more than one nic...)
Left scratching my head here on this one, as far as I can tell, there's no easy way to configure more than one nic.
(Yes, I get that the 'old' method works)

Use netcfg for anything more advanced than 1 interface.

ConnorBehan · 2011-06-10 19:15:31

If you're sure of how to do it, maybe help this person out.

Varg · 2011-06-11 20:55:50

For the people using net-auto-wireless:

I just tried out net-auto-wireless as it might be usefull in the future instead of netcfg and it works fine with multiple networks configured.
The wiki says that you need to put the variable

...
WIRELESS_INTERFACE="wlan0"
...

In your rc.conf.

I tested it without setting that variable and then there was no auto connecting but I could connect manually. I'm guessing that some of you forgot to migrate that setting in rc.conf.

skanky · 2011-06-11 21:33:03

Varg wrote:

For the people using net-auto-wireless:
I just tried out net-auto-wireless as it might be usefull in the future instead of netcfg and it works fine with multiple networks configured.
The wiki says that you need to put the variable
...
WIRELESS_INTERFACE="wlan0"
...
In your rc.conf.
I tested it without setting that variable and then there was no auto connecting but I could connect manually. I'm guessing that some of you forgot to migrate that setting in rc.conf.

Thank you so much, you're a star.
I can't work out how I didn't see that in the wiki entry - or why it wasn't in the rc.conf. Also if it's not new I must have accidentally removed it.
One of those horrible can't see for seeing what you want to see errors.

krnekhelesh · 2011-06-11 22:49:11

skanky wrote:

jasonwryan wrote:
Just updated my laptop (EeePC 901 + wicd): moved blacklist modules into /etc/modprobe.d/blacklist.conf and changed over to the new network settings in /etc/rc.conf. I already had net-tools installed, so rebooted, held my breath and BAM!
+ Shaved at least 20% off my boot time
+ Network came up straight away
+ PROFIT!
Thanks to the devs for the smooth transition
Can you show your new network section from rc.config, please?
I still have to manually start both wired & wireless with netcfg.

I also use netcfg for managing my wireless networks and here is part of my rc.conf file,

NETWORKS=(home work)
DAEMONS=(hwclock preload dbus bluetooth @net-profiles netfs crond gdm)

Basically, I load the net-profiles automatically during boot and it checks which wireless network is present and connects to it automatically.

Arch Linux

#26 2011-06-09 08:38:39

Re: New rc.conf file ?

#27 2011-06-09 08:47:35

Re: New rc.conf file ?

#28 2011-06-09 09:03:00

Re: New rc.conf file ?

#29 2011-06-09 09:34:15

Re: New rc.conf file ?

#30 2011-06-09 11:03:25

Re: New rc.conf file ?

#31 2011-06-09 12:18:38

Re: New rc.conf file ?

#32 2011-06-09 12:32:46

Re: New rc.conf file ?

#33 2011-06-09 12:35:36

Re: New rc.conf file ?

#34 2011-06-09 12:36:33

Re: New rc.conf file ?

#35 2011-06-09 14:35:17

Re: New rc.conf file ?

#36 2011-06-09 19:43:11

Re: New rc.conf file ?

#37 2011-06-09 19:47:47

Re: New rc.conf file ?

#38 2011-06-09 21:00:28

Re: New rc.conf file ?

#39 2011-06-09 21:02:51

Re: New rc.conf file ?

#40 2011-06-09 21:13:11

Re: New rc.conf file ?

#41 2011-06-09 22:39:57

Re: New rc.conf file ?

#42 2011-06-10 02:20:37

Re: New rc.conf file ?

#43 2011-06-10 02:22:02

Re: New rc.conf file ?

#44 2011-06-10 19:15:31

Re: New rc.conf file ?

#45 2011-06-11 20:55:50

Re: New rc.conf file ?

#46 2011-06-11 21:33:03

Re: New rc.conf file ?

#47 2011-06-11 22:49:11

Re: New rc.conf file ?

Board footer