Sponsored Content
Full Discussion: net card losing config
Top Forums UNIX for Dummies Questions & Answers net card losing config Post 302343825 by shwinky on Thursday 13th of August 2009 06:02:50 PM
Old 08-13-2009
net card losing config

hey all,
i have a computer with unix.... and i have an hme0 net card on it
i configured it to have an ip address in a local network with ifconfig
and i also went into inet folder to config it there....

my problem is every time i reboot my machine the config is lost and i have to config it again...

anyone knows what can cause this?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Losing IP config on reboot of Solaris 8

After a reboot my ifconfig -a has nothing but 0.0.0.0 have to reinput my IP and default route, what makes the info save? (1 Reply)
Discussion started by: jo calamine
1 Replies

2. UNIX Desktop Questions & Answers

Does Red Hat Fedora support Nvidia card 8800GTX and 260 card?

Does Red Hat Fedora support Nvidia card 8800GTX and 260 card? Does any Linux OS support Nvidia card? (1 Reply)
Discussion started by: sito
1 Replies

3. Shell Programming and Scripting

Net::SSLeay or Net::FTPSSL

Hello, I ran into an issue in one of my monitoring scripts. If I use the public ip address in my connection string everything works, but if I switch the connection string ip to 127.0.0.1 or the internal ip I get, " Connection refused at... (1 Reply)
Discussion started by: Styles
1 Replies

4. Solaris

net card coming up in down state

hey all, everytime i reset my computer my hme0 net card comes up with a down state, and i have to run ifconfig hme0 up command. help? (6 Replies)
Discussion started by: shwinky
6 Replies

5. Infrastructure Monitoring

net-snmp-config --create-snmpv3-user snmpengineID

Solaris 10 -- I created SNMPv3 users with net-snmp-config --create-snmpv3-user command. I am using HP Network Node Manager's SNMPv3 Smart Plugin to serve as the SNMP management server. Some SNMPv3 users were automatically created with the same snmpengineID. This causes NNM's brassagt proxy to... (0 Replies)
Discussion started by: rjsteele
0 Replies

6. Shell Programming and Scripting

parsing config file to create new config files

Hi, I want to use a config file as the base file and parse over the values of country and city parameters in the config file and generate separate config files as explained below. I will be using the config file as mentioned below: (config.txt) country:a,b city:1,2 type:b1... (1 Reply)
Discussion started by: clazzic
1 Replies

7. Solaris

Problem to detect a net card

People i install a solaris 9 in a sparc platform this is the 3 time that i install it on this machine, the problem now is that when i do a ifconfig -a i only see the loop conection and no the hme0, i don`t remember if during the installation i set the option not networked. Any ideas? how to... (6 Replies)
Discussion started by: enkei17
6 Replies

8. UNIX for Dummies Questions & Answers

How to use one net card of two

I have two server with 2 net cards each one: Server 1 A = 100 Mbs B = 1000Mbs (Gigabit) Server 2 A = 100 Mbs B = 1000Mbs (Gigabit) In A i ' am conected to the public network ( In both servers) and in B i make a point to point lan 1 gigabit of speed. Between the servers ... (1 Reply)
Discussion started by: enkei17
1 Replies

9. Shell Programming and Scripting

Shell script that will compare two config files and produce 2 outputs 1)actual config file 2)report

Hi I am new to shell scripting. There is a requirement to write a shell script to meet follwing needs.Prompt reply shall be highly appreciated. script that will compare two config files and produce 2 outputs - actual config file and a report indicating changes made. OS :Susi linux ver 10.3. ... (4 Replies)
Discussion started by: muraliinfy04
4 Replies

10. Red Hat

Apache virtual host config vs global config problem

Hi folks, I am trying to configure Apache webserver and also a virtual host inside this webserver. For Global server config: /var/www/html/index.html For virtual host config: /var/www/virtual/index.html Both client10 & www10 are pointing to 192.168.122.10 IP address. BUT, MY... (1 Reply)
Discussion started by: freebird8z
1 Replies
IN_GETIFA(9)						   BSD Kernel Developer's Manual					      IN_GETIFA(9)

NAME
in_getifa -- Look up the IPv4 source address best matching an IPv4 destination SYNOPSIS
options IPSELSRC #include <netinet/in_selsrc.h> struct ifaddr * in_getifa(struct ifaddr *ifa, const struct sockaddr *dst0); DESCRIPTION
in_getifa enforces the IPv4 source-address selection policy. Add the source-address selection policy mechanism to your kernel with options IPSELSRC. options IPSELSRC lets the operator set the policy for choosing the source address of any socket bound to the ``wildcard'' address, INADDR_ANY. Note that the policy is applied after the kernel makes its forwarding decision, thereby choosing the output interface; in other words, this mechanism does not affect whether or not NetBSD is a ``strong ES''. An operator affects the source-address selection using sysctl(8) and ifconfig(8). Operators set policies with sysctl(8). Some policies con- sider the ``preference number'' of an address. An operator may set preference numbers for each address with ifconfig(8). A source-address policy is a priority-ordered list of source-address ranking functions. A ranking function maps its arguments, (source address, source index, source preference, destination address), to integers. The source index is the position of source address in the interface address list; the index of the first address is 0. The source preference is the preference number the operator assigned to source address. The destination address is the socket peer / packet destination. Presently, there are four ranking functions to choose from: index ranks by source index; lower indices are ranked more highly. preference ranks by source preference; higher preference numbers are ranked more highly. common-prefix-len ranks each source address by the length of the longest prefix it has in common with destination address; longer common prefixes rank more highly. same-category determines the "categories" of source and destination address. A category is one of private, link-local, or other. If the categories exactly match, same-category assigns a rank of 2. Some sources are ranked 1 by category: a link-local source with a private destination, a private source with a link-local destination, and a private source with an other des- tination rank 1. All other sources rank 0. Categories are defined as follows. private RFC1918 networks, 192.168/16, 172.16/12, and 10/8 link-local 169.254/16, 224/24 other all other networks---i.e., not private, not link-local To apply a policy, the kernel applies all ranking functions in the policy to every source address, producing a vector of ranks for each source. The kernel sorts the sources in descending, lexicographical order by their rank-vector, and chooses the highest-ranking (first) source. The kernel breaks ties by choosing the source with the least source index. The operator may set a policy on individual interfaces. The operator may also set a global policy that applies to all interfaces whose pol- icy he does not set individually. Here is the sysctl tree for the policy at system startup: net.inet.ip.selectsrc.default = index net.inet.ip.interfaces.ath0.selectsrc = net.inet.ip.interfaces.sip0.selectsrc = net.inet.ip.interfaces.sip1.selectsrc = net.inet.ip.interfaces.lo0.selectsrc = net.inet.ip.interfaces.pflog0.selectsrc = The policy on every interface is the ``empty'' policy, so the default policy applies. The default policy, index, is the ``historical'' pol- icy in NetBSD. The operator may override the default policy on ath0, # sysctl -w net.inet.ip.interfaces.ath0.selectsrc=same-category,common-prefix-len,preference yielding this policy: net.inet.ip.selectsrc.default = index net.inet.ip.interfaces.ath0.selectsrc = same-category,common-prefix-len,preference The operator may set a new default, # sysctl -w net.inet.ip.selectsrc.debug=> same-category,common-prefix-len,preference # sysctl -w net.inet.ip.interfaces.ath0.selectsrc= yielding this policy: net.inet.ip.selectsrc.default = same-category,common-prefix-len,preference net.inet.ip.interfaces.ath0.selectsrc = In a number of applications, the policy above will usually pick suitable source addresses if ath0 is configured in this way: # ifconfig ath0 inet 64.198.255.1/24 # ifconfig ath0 inet 10.0.0.1/24 # ifconfig ath0 inet 169.254.1.1/24 # ifconfig ath0 inet 192.168.49.1/24 preference 5 # ifconfig ath0 inet 192.168.37.1/24 preference 9 A sysctl, net.inet.ip.selectsrc.debug, turns on and off debug messages concerned with source selection. You may set it to 0 (no messages) or 1. SEE ALSO
ifconfig(8), sysctl(8) STANDARDS
The family of IPv6 source-address selection policies defined by RFC3484 resembles the family of IPv4 policies that in_getifa enforces. AUTHORS
David Young <dyoung@NetBSD.org> BUGS
With options IPSELSRC, a new interface ioctl(2), SIOCSIFADDRPREF, was introduced. It ought to be documented in inet(4). Also, options(4) ought to cross-reference this manual page. This work should be used to set IPv6 source-address selection policies, especially the family of policies defined by RFC3484. BSD
February 22, 2007 BSD
All times are GMT -4. The time now is 09:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy