11-11-2006
Network Startup Problems
I recently installed slackware 11 and have been very happy with it until I found out that some gnome related apps can cause gnome's network manager to alter the rc.init1 script by adding 3 lines to the script containing only the command, eth_up. This causes the script not to run properly and not intialize eth0. I took these back out of the script and still could not get eth0 intialized. I replaced the rc.inet1 with the original rc.inet1 that slack 11 installs and now the rc.inet1 script runs and returns no errors, however, ifconfig still shows no eth0, and network applications return error 101:no connection to network. Have I missed a step somewhere? Please help!
9 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hello guys , i have a big big problem.
At the company that i work for there are like 4 pcs that are sending and recieving a lot of packets to the point that the network is down.
we think that it might be a virus, we run all the antivirus that you could posible think of and nothing so far.
... (2 Replies)
Discussion started by: josramon
2 Replies
2. SuSE
Hullo everyone,
I have recently installed SUSE 9.1 and attached it to my Network router (Actiontec 54Mbps Wireless DSL Gateway) but can't connect to the internet. It comes up with the following error message:
An error occurred while loading "http://www.yahoo.com":Timeout on server - connection... (2 Replies)
Discussion started by: sybella1
2 Replies
3. AIX
Hi,
I have a LPAR running AIX 5.3 with multiple Etherchannels running (e.g. ent10-ent14 etc).
The person who configured up the interfaces set more that one interface through minimal config and startup under smitty->tcpip
When I try and clear out the IP address for one of the additional... (1 Reply)
Discussion started by: backslash
1 Replies
4. Solaris
Hey. i have a SPARCstation 5 running solaris 8 and CDE,
i know this hardware is really old but its the only Solaris machine i can afford at this time, (Student) but im having a hard time getting it on the internet, im using a cable modem, andt DHCP IPv4, but i can`t get a connection, i have heard... (0 Replies)
Discussion started by: mads-nielsen
0 Replies
5. Shell Programming and Scripting
i have two lines in my rc.local file that are
wget -O/<path>/<file>.zip url://domain.com
unzip -o /<path>/<file>.zip
the wget works fine, but the unzip won't work. when i copy/pase the unzip line to the prompt it works fine. i thought that maybe the unzip was running before the wget... (0 Replies)
Discussion started by: easysnowboards
0 Replies
6. Solaris
recently I've setup a Solaris 10 box & am having network disruption, e.g. disconnects, interrupted pings, etc) when I
connect to it from another machine, how should I troubleshoot this !
The machine is a x86 box with 3 NICs (Differnet providors). The Current NIC is a Intel Gigabit, which is... (4 Replies)
Discussion started by: stevie_velvet
4 Replies
7. SCO
SCO unix 5.0.5 - Suddently network lost & has to be reboot. I try to stop TCP & start TCP. but no connection. Any idea about that.
thanks (8 Replies)
Discussion started by: ajantha
8 Replies
8. UNIX for Advanced & Expert Users
i need help, i will always accord mine if my scope allows me, help me in this one..
am running vmware 7.0 in winserver 2008 on a cq61-425el, my network driver is installed correctly. and my vmware network drivers have added as well (in the device manager section).
During installation i wasnt... (0 Replies)
Discussion started by: baitz
0 Replies
9. Shell Programming and Scripting
Hi,
I work on several Sun servers running Solaris (SunOS 5.10). All of these are Application Servers with a propietary software running on it.
It happens that some times (not regularly/deterministic and not so often, i.e. twice a month circa) we register what I think are network problems.
I say... (4 Replies)
Discussion started by: Evan
4 Replies
LEARN ABOUT SUSE
ifsysctl
IFSYSCTL(5) Network configuration IFSYSCTL(5)
NAME
ifsysctl[-<interface name>] - per network interface sysctl settings
SYNOPSIS
/etc/sysconfig/network/ifsysctl
/etc/sysconfig/network/ifsysctl-<interface name>
DESCRIPTION
These files are intended to contain sysctl settings, that should be applied when a network interface is created. This are usually interface
specific settings, like:
net.ipv6.conf.eth0.use_tempaddr = 1
or
net.ipv4.conf.eth0.rp_filter = 0
The settings are applied by the /etc/sysconfig/network/scripts/ifup-sysctl script executed via /etc/udev/rules.d/77-network.rules rule (see
udev(7)), after the creation and after the rename of the interface name to its persistent name (when applicable), but before the ifup
<interface name> -o hotplug may be executed to configure the interface.
The settings are not applied by default when the NetworkManager is active (NETWORKMANAGER=yes), except when the IFSYSCTL_NETWORKMANAGER=yes
variable is set in the /etc/sysconfig/network/config file.
Settings from the ifsysctl- file are applied every time an interface has been created.
Settings from the ifsysctl-interface name file are applied when the interface with the corresponding interface name has been created.
SYNTAX
The sysctl(8) utility is required to apply the settings. It supports two separator characters for sysctl keywords: a "." in default format
and a "/" in the alternate format. Therefore the syntax is basically same to the /etc/sysctl.conf file.
Interface names may contain a ".". In the default sysctl format using a "." as separator, that is any "." in the interface name of the key-
word, has to be replaced with a "/". In the alternate sysctl format with "/" as separator, normal interface names can be used.
Optionally, the ifsysctl files may contain also the $INTERFACE and the $SYSCTL_IF variables, that are automatically replaced with the cur-
rent interface name usable in the alternate format and with the sysctl-quoted interface name for the default format, before the settings
are passed to the sysctl utility.
Note also, that settings with variables in the ifsysctl (without the -<interface name> suffix), will be applied for every interface!
Further, files with variables are not compatible to the /etc/sysctl.conf file.
EXAMPLES
Settings for "eth0" and "eth0.1" interfaces
# using "." as separator:
net.ipv6.conf.eth0.use_tempaddr = 1
net.ipv6.conf.eth0/1.use_tempaddr = 1
# using "/" as separator:
net/ipv6/conf/eth0/use_tempaddr = 1
net/ipv6/conf/eth0.0/use_tempaddr = 1
Settings with variables:
# using "." as separator:
net.ipv6.conf.$SYSCTL_IF.use_tempaddr = 1
# using "/" as separator:
net/ipv6/conf/$INTERFACE/use_tempaddr = 1
To test your ifsysctl-eth0 or ifsysctl file, use:
/etc/sysconfig/network/scripts/ifup-sysctl eth0 -o debug
BUGS
Please report bugs at <https://bugzilla.novell.com/>
AUTHOR
Marius Tomaschewski <mt@suse.de>
SEE ALSO
ifup(8) ifcfg(5) sysctl(8)
sysconfig December 2009 IFSYSCTL(5)