03-03-2007
dladm show-link
to see all your physical interfaces
to get the other physical interface up, find out the interface name /w the cmd above and use ifconfig to bring it up.
9 More Discussions You Might Find Interesting
1. Solaris
Hi guys,
Hope somebody can help me on this. I have a Sun Sparc 20 workstation and it has a boot problem. During boot, an error message " ifconfig:socket: Bad File Number" come up and the workstation hang (cannot boot).
I did boot -s and checked using ifconfig -a command but i got the same... (0 Replies)
Discussion started by: kroegand
0 Replies
2. Solaris
Hi All,
I recently installed Solaris 9 on my Compaq Presario V2000 Series (V2069CL) laptop. Everything is working fine except that Solaris is not able to detect the Network Interface after boot.
While the system is booting, it shows that it has detected "Xircom Pocket Ethernet parallel port... (3 Replies)
Discussion started by: com2com
3 Replies
3. Solaris
Hi there,
I'm trying to configure an additional network interface on Solaris 8 (eri0). The interface has been activated, but all the frames are still routed to the current default interface (ce0) I've tried following command (with various syntaxes...) unsuccessfully so far:
# route add... (2 Replies)
Discussion started by: sreiniche
2 Replies
4. Solaris
Hi gurus
Could anybody tell me that what are the kernal parameter of network interface in solaris
Regards (3 Replies)
Discussion started by: girish.batra
3 Replies
5. HP-UX
Hello,
I'm writing to you because I encountered the following problem. My program displayes all network interfaces that are available in the system, but I would like to add a functionality in which a user can enter a destination address IP (ex. the IP address of the Google search engine) and will... (1 Reply)
Discussion started by: foxrafi
1 Replies
6. Solaris
Hi,
/sbin/ifconfig -a
when i login as guest user , output like below,
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
eri0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2
inet... (5 Replies)
Discussion started by: forumguest
5 Replies
7. Solaris
Hi,
I have installed Solaris 10 on VMware7, When i used ifconfig -a to check network interface, it has shown lo0 as loopback interface.
Please advise how to configure network interfaces using VMware. (1 Reply)
Discussion started by: ajhal04
1 Replies
8. Solaris
Dear All,
I have a solaris Server in which I have 4 network interfaces , out of which only one is used . So all the applications are using this interface .
The interface speed is 1000Mbps . I find no hardware issue or packets g being dropped.
But i find that no of Input and Output... (4 Replies)
Discussion started by: jegaraman
4 Replies
9. Solaris
Hi, I am new in Solaris 11. I can't even make the NIC work. Here is the issue:
Any help will be greatly appreciated. (6 Replies)
Discussion started by: aixlover
6 Replies
vni(7d) Devices vni(7d)
NAME
vni - STREAMS virtual network interface driver
DESCRIPTION
The vni pseudo device is a multi-threaded, loadable, clonable, STREAMS pseudo-device supporting the connectionless Data Link Provider
Interface dlpi(7P) Style 2. Note that DLPI is intended to interact with IP, meaning that DLPI access to applications is not supported. (For
example, snoop fails on the vni interface.)
The vni device is a software-only interface and does not send or receive data. The device provides a DLPI upper interface that identifies
itself to IP with a private media type. It can be configured via ifconfig(1M) and can have IP addresses assigned to it, making aliases pos-
sible.
The vni pseudo device is particularly useful in hosting an IP address when used in conjunction with the 'usesrc' ifconfig option (see
ifconfig(1M) for examples). The logical instances of the device can also be used to host addresses as an alternative to hosting them over
the loopback interface.
Multicast is not supported on this device. More specifically, the following options return an error when used with an address specified on
vni: IP_MULTICAST_IF, IP_ADD_MEMBERSHIP, IP_DROP_MEMBERSHIP, IPV6_MULTICAST_IF, IPV6_JOIN_GROUP, IPV6_LEAVE_GROUP. In addition, broadcast
is not supported.
Because there is no physical hardware configured below it, no traffic can be received through nor transmitted on a virtual interface. All
packet transmission and reception is accomplished with existing physical interfaces and tunnels. Because applications that deal with packet
transmission and reception (such as packet filters) cannot filter traffic on virtual interfaces, you cannot set up a packet filter on a
virtual interface. Instead, you should configure the policy rules to apply to the physical interfaces and tunnels, and if necessary, use
the virtual IP addresses themselves as part of the rule configuration. Also, note that the virtual interface cannot be part of an IP multi-
pathing (IPMP) group.
FILES
/dev/vni
64-bit ELF kernel driver
SEE ALSO
ifconfig(1M), in.mpathd(1M), ip(7P), ip6(7P)
SunOS 5.10 18 July 2004 vni(7d)