Andrew Myers wrote: >Unfortunately I'm still experiencing the same problems even when I do that. > >Here's the series of commands I executed before it actually connected. > >bash-3.00# ifconfig -a >lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu >8232 index 1 > inet 127.0.0.1 netmask ff000000 >lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu >8252 index 1 > inet6 ::1/128 > ># ifconfig iwi0 plumb ># wificonfig -i iwi0 connect homenet >#ifconfig iwi0 dhcp > >At this point i still could not connect to websites through firefox. > >So then I tried this: > >#svcadm enable physical:nwam > >Almost immediately a dialog popped up saying "Brought interface iwi0 >up, got address 192.168.2.120" and from then on everything was okay. > >Is there anything else that nwam does which I might be missing out on? > > That is the case. When you use wificonfig manually connect to the internet, you need to set your dns server ip to /etc/resolv.conf, otherwise, even you get the ip address from dhcp, you can't connect to internet through firefox.
nwam does all this for you automatically. -- Quaker >On 27/07/07, Quaker Fang <Quaker.Fang at sun.com> wrote: > > >>Hi Andrew, >> >>After you reboot your system, before use wificonfig, please make sure >>iwi is plumbed. >># ifconfig iwi0 plumb >> >>Since if you enable the nwam, it will plumb the interface for you >>automatically. >> >>-- >>Quaker >> >>
