Normally, the NWAM service properly configures your network connection. This procedure shows how to configure the connection manually if, for example, you want to configure static IP addresses for your network interface. The procedure applies whether you are manually configuring wired network settings or wireless network settings.
You can manually configure network settings in one of two ways:
- By using the OpenSolaris GUI
- By issuing commands in a terminal window
The following are steps that you perform when using the OpenSolaris GUI.
- From the Desktop menu, choose System > Administration > Network.
The prompt to choose to configure automatically or manually appears. - Choose the appropriate option to configure the network manually.
The NWAM service is disabled and the Network settings window appears. - In the Connections tab of the Network settings window, do one of the following, depending on the kind of interface that you want to configure:
- If you are manually configuring the wired network settings, select the wired interface, then click Properties.
- If you are manually configuring the wireless network settings, select the wireless interface, then click Properties.
A separate Interface properties window appears, as shown in the following figure.
- In the Interface properties window, select whether you want to configure a static IP address or DHCP.
- To activate this interface connection every time the system boots, select Activate on boot.
- If you are configuring static IP addresses, provide the IP address, Subnet mask, and Gateway address on the appropriate fields, and then click OK.
- To provide the host name, select the General tab and supply the requested information.
- To configure DNS, select the DNS tab and supply the requested information.
- To add hosts, click the Hosts tab and supply the requested information.
- Click OK.
- (For wireless network configurations only) Connect to the wireless network of your choice.
See How to Connect to a Wireless Network at Startup.
The following example shows how to manually configure network settings by issuing commands in a terminal window. The commands start a privileged shell, stop the NWAM service, and configure a static IP address for the selected wired or wireless interface. This example uses a wired interface. In addition, parameters are defined in configuration files to create a persistent configuration.
The example assumes that the host name is sys001. You would type the following commands in a terminal window.
user@opensolaris:-$ pfexec bash
#
# svcadm enable network/physical:default
# svcadm disable network/physical:nwam
#
# dladm show-phys
LINK MEDIA STATE SPEED DUPLEX DEVICE
e1000g0 Ethernet up 1000 full e1000g0
e1000g1 Ethernet down 1000 full e1000g1
ath0 Wifi up 1000 full ath0
#
# ifconfig e1000g0 plumb 192.168.10.10/24 up
# ifconfig e1000g0
e1000g0: flags=201100843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 6
inet 192.168.10.10 netmask ffffff00 broadcast 192.168.10.255
ether 2:8:20:b2:f1:76
#
# echo sys001 > /etc/hostname.e1000g0
# vi /etc/hosts
...
192.168.10.10 sys001 loghost
#
If you are configuring a wireless network setting, you would perform the following additional steps.
# dladm scan-wifi LINK ESSID BSSID/IBSSID SEC STRENGTH MODE SPEED ath0 net1 00:0e:38:49:01:d0 none good g 54Mb ath0 net2 00:0e:38:49:02:f0 none very weak g 54Mb ath0 net3 00:0d:ed:a5:47:e0 none very good g 54Mb # # dladm connect-wifi -e net3 # dladm show-wifi LINK STATUS ESSID SEC STRENGTH MODE SPEED ath0 connected net3 none very good g 54Mb
Perform other network configurations as needed.
For example, if a router exists, add the router's IP address to the /etc/defaultrouter file. If you are using a naming service, copy that naming service's configuration file. For example, copy /etc/nsswitch.dns to /etc/nsswitch.conf.
For more information:
Comments (6)
Mar 07, 2009
stephen_b says:
Kathy, please, help with this: I need to intercept nwam and reverse the ether....Kathy,
please, help with this:
I need to intercept nwam and reverse the ether. i do it manually, but it should be possible to put this in a config file somewhere.
ifconfig nge0 ether 0:19:21:db:3c:5
ifconfig nge0 dhcp start
nge was supposed to be fixed as Sun knew about this problem, but I installed osol 11 and the same issue is still there.
thank you
stephen
Mar 09, 2009
kathy.slattery says:
Stephen, I'll ask Raoul to look into this. He is the writer assigned to these p...Stephen,
I'll ask Raoul to look into this. He is the writer assigned to these pages.
Thanks for the update.
-Kathy
Mar 09, 2009
raoulrc says:
Yes. I made inquiries with an nwam engineer about this. I'll put the information...Yes. I made inquiries with an nwam engineer about this. I'll put the information in as soon as he reviews the proper steps to do this.
Raoul
Mar 20, 2009
raoulrc says:
Stephen, Per an engineer, "... turn off the physical:nwam service and use the...Stephen,
Per an engineer,
"... turn off the physical:nwam service and use the regular physical:default service to manage interfaces; you can then set up special configuration in /etc/hostname.nge0."
It seems to me that this issue arises from a broken nge driver. If yes, then the information might be better placed in the release notes, since the workaround is only temporary until the driver is fixed. Do you think so? Reply to me directly, and then we can work together on the wording of the note to describe the issue accurately: raoul.carag@sun.com
Thanks!
Raoul
Mar 23, 2009
tek-ops says:
Here are two examples: Static IP: $ cat /etc/hostname.e1000g1 192.168.175.1 net...Here are two examples:
Static IP:
$ cat /etc/hostname.e1000g1
192.168.175.1 netmask 255.255.255.0 broadcast + up
Notes:
DHCP:
$ cat /etc/hostname.e1000g0
$ cat /etc/dhcp.e1000g0
Note:
[empty files mean accepting default values]
Mar 23, 2009
raoulrc says:
Thanks much for this feedback. Indeed, the information here is applicable to the...Thanks much for this feedback. Indeed, the information here is applicable to the nge0 interface, whose problems were primarily due to a broken driver.
The nge driver should be fixed in the later Nevada builds so it is no longer necessary to do this workaround in the next OpenSolaris release. The drivers-discuss@opensolaris.org alias should also be able to point where to get the fixed driver if this is available.
Raoul