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
VLAN(4) BSD Kernel Interfaces Manual VLAN(4)
NAME
vlan -- IEEE 802.1Q Virtual LAN network device
SYNOPSIS
pseudo-device vlan
DESCRIPTION
The vlan interface provides support for IEEE 802.1Q Virtual Local Area Networks (VLAN). This supports the trunking of more than one network
on a single network interface. This is particularly useful on routers or on hosts which must be connected to many different networks through
a single physical interface.
To use a vlan interface, the administrator must first create the interface and then specify the VID (VLAN identifier, the first 12 bits from
a 16-bit integer which distinguishes each VLAN from any others) and physical interface associated with the VLAN. This can be done by using
the ifconfig(8) create, vlan, and vlanif subcommands from a shell command line or script. From within a C program, use the ioctl(2) system
call with the SIOCSIFCREATE and SIOCSIFVLAN arguments.
To be compatible with other IEEE 802.1Q devices, the vlan interface supports a 1500 byte MTU, which means that the parent interface will have
to handle packets that are 4 bytes larger than the original Ethernet standard. Drivers supporting this increased MTU are:
- drivers using the DP8390 core (such as ec(4), ne(4), we(4), and possibly others)
- bge(4)
- bnx(4)
- ea(4)
- eb(4)
- epic(4)
- etherip(4)
- ex(4)
- fxp(4)
- gem(4)
- hme(4)
- le(4)
- sip(4)
- ste(4)
- stge(4)
- ti(4)
- tl(4)
- tlp(4)
- vge(4)
- vr(4)
- wm(4)
- xi(4)
vlan can be used with devices not supporting the IEEE 802.1Q MTU, but then the MTU of the vlan interface will be 4 bytes too small and will
not interoperate properly with other IEEE 802.1Q devices, unless the MTU of the other hosts on the VLAN are also lowered to match.
EXAMPLES
The following will create interface vlan0 with VID six, on the Ethernet interface tlp0:
ifconfig vlan0 create
ifconfig vlan0 vlan 6 vlanif tlp0
After this set up, IP addresses (and/or other protocols) can be assigned to the vlan0 interface. All other hosts on the Ethernet connected
to tlp0 which configure a VLAN and use VID six will see all traffic transmitted through vlan0.
The same VLAN can be created at system startup time by placing the following in /etc/ifconfig.vlan0:
create
vlan 6 vlanif tlp0
SEE ALSO
ifconfig(8)
HISTORY
The vlan device first appeared in NetBSD 1.5.1, and was derived from a VLAN implementation that appeared in FreeBSD and OpenBSD.
BUGS
The vlan interfaces do not currently inherit changes made to the physical interfaces' MTU.
BSD
December 16, 2010 BSD