Bug #1419
open
nwam defaults multiple interfaces?
0%
Description
Hi, not sure this is a bug or a <<feature>>... Finally able to install first 148 text to an AMILO Pa1510 using default nwam
then image-updated to dev-il to get oi_151.
I notice the following:
richard@amilo:~# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
rtls0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2
inet 192.168.0.20 netmask ffffff00 broadcast 192.168.0.255
ether 0:3:d:62:71:67
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
inet6 ::1/128
rtls0: flags=20002004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2
inet6 fe80::203:dff:fe62:7167/10
ether 0:3:d:62:71:67
rtls0:1: flags=20002000840<RUNNING,MULTICAST,IPv6> mtu 1500 index 2
inet6 ::/10
I'm curious why the interface rtls0:1
Files
Updated by Richard PALO almost 12 years ago
- File amilo.messages.txt amilo.messages.txt added
thought I'd reboot with a clean messages file to add.
I noticed in the meantime that ipadm thinks differently:
richard@amilo:~$ ipadm show-addr ADDROBJ TYPE STATE ADDR lo0/v4 static ok 127.0.0.1/8 rtls0/_b dhcp ok 192.168.0.20/24 lo0/v6 static ok ::1/128 rtls0/_a addrconf ok fe80::203:dff:fe62:7167/10
Updated by Richard PALO almost 12 years ago
Strange, yet a new interface...
richard@amilo:~$ ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
rtls0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2
inet 192.168.0.20 netmask ffffff00 broadcast 192.168.0.255
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
inet6 ::1/128
rtls0: flags=20002004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2
inet6 fe80::203:dff:fe62:7167/10
rtls0:1: flags=20002000840<RUNNING,MULTICAST,IPv6> mtu 1500 index 2
inet6 ::/10
rtls0:2: flags=20002000840<RUNNING,MULTICAST,IPv6> mtu 1500 index 2
inet6 ::/0
richard@amilo:~$ ipadm show-addr
ADDROBJ TYPE STATE ADDR
lo0/v4 static ok 127.0.0.1/8
rtls0/_c dhcp ok 192.168.0.20/24
lo0/v6 static ok ::1/128
rtls0/_a addrconf ok fe80::203:dff:fe62:7167/10
the only difference in system is I'm trying to test a logitech usb webcam does seem to work better in this release than in 148 but is still rather slow... perhaps related?
These messages in /var/adm/messages are strange:
Aug 30 08:03:49 amilo mac: [ID 469746 kern.info] NOTICE: rtls0 registered Aug 30 08:03:49 amilo mii: [ID 427086 kern.info] rtls0: Using 100BASE-X Ethernet PHY at 1: Realtek Internal RTL8139 Aug 30 08:03:49 amilo nwamd[94]: [ID 659247 daemon.error] 1: nwamd_plumb_unplumb_interface: unplumb IPv4 failed for rtls0: Operation failed Aug 30 08:03:49 amilo nwamd[94]: [ID 921391 daemon.error] 1: nwamd_plumb_unplumb_interface: unplumb IPv6 failed for rtls0: Operation failed Aug 30 08:03:49 amilo nwamd[94]: [ID 659247 daemon.error] 1: nwamd_plumb_unplumb_interface: unplumb IPv4 failed for rtls0: Operation failed Aug 30 08:03:49 amilo nwamd[94]: [ID 921391 daemon.error] 1: nwamd_plumb_unplumb_interface: unplumb IPv6 failed for rtls0: Operation failed Aug 30 08:03:50 amilo nwamd[94]: [ID 659247 daemon.error] 1: nwamd_plumb_unplumb_interface: unplumb IPv4 failed for rtls0: Operation failed Aug 30 08:03:50 amilo nwamd[94]: [ID 921391 daemon.error] 1: nwamd_plumb_unplumb_interface: unplumb IPv6 failed for rtls0: Operation failed Aug 30 08:03:50 amilo nwamd[94]: [ID 561378 daemon.error] 1: add_ip_address: ipadm_create_addr failed on rtls0: Addrconf already in progress Aug 30 08:03:50 amilo nwamd[94]: [ID 782290 daemon.error] 11: start_dhcp: ipadm_create_addr on rtls0 returned: Could not communicate with dhcpagent, retrying in 10 sec . . . Aug 30 08:04:00 amilo nwamd[94]: [ID 532455 daemon.error] 11: start_dhcp: ipadm_create_addr failed for rtls0: Invalid argument provided
Updated by Ken Mays over 11 years ago
- Due date set to 2011-09-14
- Category set to OS/Net (Kernel and Userland)
- Status changed from New to Closed
- Assignee set to Ken Mays
- Target version set to oi_151_stable
- Estimated time set to 8.00 h
A feature. Shows IPv4/IPv6 setup on your Realtek NIC.
Updated by Richard PALO over 11 years ago
Ken Mays wrote:
A feature. Shows IPv4/IPv6 setup on your Realtek NIC.
You say feature, but do not explain why after reboot the extra interfaces are not always persistent.
If it is a feature, then it sure is buggy!
Updated by Richard PALO over 11 years ago
- Status changed from Closed to Feedback
Once again, you say feature (and even close the report !), but you do not justify the reason extra interface(s) (like rtls0:1:) is/are created in a stock installation, not to mention that upon reboot it/they does/do not always remain...
What are these messages for:
Sep 12 18:11:06 amilo mac: [ID 469746 kern.info] NOTICE: rtls0 registered Sep 12 18:11:07 amilo mii: [ID 427086 kern.info] rtls0: Using 100BASE-X Ethernet PHY at 1: Realtek Internal RTL8139 Sep 12 18:11:07 amilo nwamd[110]: [ID 495969 daemon.error] 1: nwamd_plumb_unplumb_interface: unplumb IPv4 failed for rtls0: Echec de l'opération Sep 12 18:11:07 amilo nwamd[110]: [ID 751104 daemon.error] 1: nwamd_plumb_unplumb_interface: unplumb IPv6 failed for rtls0: Echec de l'opération Sep 12 18:11:07 amilo nwamd[110]: [ID 495969 daemon.error] 1: nwamd_plumb_unplumb_interface: unplumb IPv4 failed for rtls0: Echec de l'opération Sep 12 18:11:07 amilo nwamd[110]: [ID 751104 daemon.error] 1: nwamd_plumb_unplumb_interface: unplumb IPv6 failed for rtls0: Echec de l'opération Sep 12 18:11:07 amilo nwamd[110]: [ID 495969 daemon.error] 1: nwamd_plumb_unplumb_interface: unplumb IPv4 failed for rtls0: Echec de l'opération Sep 12 18:11:07 amilo nwamd[110]: [ID 751104 daemon.error] 1: nwamd_plumb_unplumb_interface: unplumb IPv6 failed for rtls0: Echec de l'opération Sep 12 18:11:07 amilo nwamd[110]: [ID 561378 daemon.error] 1: add_ip_address: ipadm_create_addr failed on rtls0: Addrconf already in progress
BTW, the system encouraged me to upgrade to 151.1 which I did.
Sep 12 18:10:58 amilo genunix: [ID 665917 kern.notice] ^MOpenIndiana Build oi_151a 64-bit (illumos a4e1558c0599) Sep 12 18:10:58 amilo genunix: [ID 107366 kern.notice] SunOS Release 5.11 - Copyright 1983-2010 Oracle and/or its affiliates. Sep 12 18:10:58 amilo genunix: [ID 864463 kern.notice] All rights reserved. Use is subject to license terms.
Updated by Ken Mays over 11 years ago
- Due date deleted (
2011-09-14) - Assignee changed from Ken Mays to Ken Mays
- Priority changed from Normal to Low
- Estimated time changed from 8.00 h to 1.00 h
- Difficulty changed from Medium to Bite-size
- Tags changed from needs-triage to nwam
Richard - you can ask over in the nwan-discuss at OpenSolaris.org. I consider a bug if you were not getting accurate information or proper functionality from the driver or tools. If you are looking for more detailed info on nwam, then you can check with the nwam developers.
Updated by Ken Mays over 11 years ago
- Due date set to 2011-09-16
- Status changed from Feedback to Closed
- % Done changed from 0 to 100
Some implemented NICs have features like this or the NIC is attached to other interfaces on the motherboard causing the info. Nothing major and depend on how the NIC is implemented or enabled features it has. Think of it like when you run psrinfo and see virtual processing cores versus a physical chip. The info you get back is what the driver is interpreting from the NIC (which is accurate (I have a similar setup!!)).
Updated by Albert Lee over 11 years ago
- Project changed from OpenIndiana Distribution to illumos gate
- Category deleted (
OS/Net (Kernel and Userland)) - Target version deleted (
oi_151_stable)
Updated by Albert Lee over 11 years ago
- Category set to cmd - userland programs
- Status changed from Closed to New
- Assignee deleted (
Ken Mays) - % Done changed from 100 to 0
This is obviously not resolved.