Again, my congratulations! This is not the normal procedure, but at least here 
we get something: a functional link through rum1.

I did an extra unplumb of rge0, which was still there.

# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 
index 1
        inet 127.0.0.1 netmask ff000000 
rge0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500 
index 2
        inet 192.168.116.61 netmask ffffff00 broadcast 192.168.116.255
        ether 0:e0:4d:30:2d:68 
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 
index 1
        inet6 ::1/128 
# ifconfig rge0 unplumb
# 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 
# rem_drv rum
#  add_drv -i '"usb148f,2573"' rum
devfsadm: driver failed to attach: rum
Warning: Driver (rum) successfully added to system but failed to attach
# rem_drv rum
# [plugging rum device]
bash: [plugging: command not found
#  add_drv -i '"usb148f,2573"' rum
# modinfo | grep rum
286 fffffffff81e4000   6750 294   1  rum (rum driver v1.1)
# ifconfig rum1 plumb
# dladm scan-wifi rum1
LINK       ESSID               BSSID/IBSSID      SEC    STRENGTH   MODE   SPEED
rum1       wlan                0:13:10:7c:aa:f1  wpa    excellent  g      54Mb
#  dladm connect-wlan -e wlan -k psk rum1
# dladm show-wifi
LINK       STATUS            ESSID               SEC    STRENGTH   MODE   SPEED
rum1       connected         wlan                wpa    excellent  g      36Mb
# ifconfig rum1 dhcp
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 
index 1
        inet 127.0.0.1 netmask ff000000 
rum1: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500 
index 3
        inet 192.168.116.198 netmask ffffff00 broadcast 192.168.116.255
        ether 0:21:27:c0:a8:9b 
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 
index 1
        inet6 ::1/128 
# netstat -rn
Routing Table: IPv4
  Destination           Gateway           Flags  Ref     Use     Interface 
-------------------- -------------------- ----- ----- ---------- --------- 
default              192.168.116.200      UG        1          0 rum1      
192.168.116.0        192.168.116.198      U         1          0 rum1      
127.0.0.1            127.0.0.1            UH        3        131 lo0       
Routing Table: IPv6
  Destination/Mask            Gateway                   Flags Ref   Use    If   
--------------------------- --------------------------- ----- --- ------- ----- 
::1                         ::1                         UH      1      21 lo0   
# ping 192.168.116.100
192.168.116.100 is alive
# dig www.opensolaris.org
[...]
;; QUESTION SECTION:
;www.opensolaris.org.           IN      A

;; ANSWER SECTION:
www.opensolaris.org.    900     IN      CNAME   opensolaris.org.
opensolaris.org.        900     IN      A       72.5.123.5
[...]

# cat /etc/motd
Sun Microsystems Inc.   SunOS 5.11      snv_105 November 2008

/var/adm/messages is a tad long. I include it as attachment, and still cut out 
the thousands of identical lines following suit, of 

solu unix: [ID 954099 kern.info] NOTICE: IRQ20 is being shared by drivers with 
different interrupt levels.
solu This may result in reduced system performance.


I personally understand much too little to make out, why and where it would 
interfere with rge0 - if it was there.

Uwe
-- 
This message posted from opensolaris.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: messages_rum1
Type: application/octet-stream
Size: 28015 bytes
Desc: not available
URL: 
<http://mail.opensolaris.org/pipermail/laptop-discuss/attachments/20090115/88e0d92c/attachment.obj>

Reply via email to