10-21-2003
.............
thanks to Perderabo ....
by the way, i had also set up an eri0 no changes, because -->....
just for info and forum searchs
the answere:
I contacted a friend of mine who's working at sun as an SE, he told me that the tpye "ce" is an additional driver for cards witch supports VLAN like vge, hme and ce itselfs. the "low budget" variants like eri or ge cannot create additional VLAN interfaces, so the only alternativ approach is to create "dummy" interfaces (eri0:1).. not an really good alternativ solution ;-(
thx a lot
greetings Preßy
10 More Discussions You Might Find Interesting
1. IP Networking
Hi all,
so server: FreeBSD 7.0 release,
interfaces on it DLINK DGE-528T with support of vlans :))
so first interface looks to LAN second to ISP.
I created vlan1 with id 1 and gave to it ip address and plug it in
tagged port of swith for vlan 1. so client from vlan1 reaches the server.
it... (2 Replies)
Discussion started by: samar
2 Replies
2. Solaris
I 've a T5220 running solaris 10u6 with Ldoms 1.1. following is o/p of my dladm
e1000g0 type: non-vlan mtu: 1500 device: e1000g0
e1000g1 type: non-vlan mtu: 1500 device: e1000g1
e1000g531001 type: vlan 531 mtu: 1500 device: e1000g1
e1000g2 ... (0 Replies)
Discussion started by: fugitive
0 Replies
3. AIX
I have a aix 5.3, two network adapter, configure as a etherchannel, how can I know the vlan id by command? (4 Replies)
Discussion started by: rainbow_bean
4 Replies
4. Programming
Hi all
My application is a monitoring application that monitors the incoming udp packet when ever required. When ever a particular source ip and port and dest ip and port is provided the filter will be framed based them. For eg,
char filterExpr;
filterExpr = "udp and src host 192.168.16.100... (0 Replies)
Discussion started by: anusha_pixel
0 Replies
5. IP Networking
Hello. I want to Communicate 2 VLAN with router like this solution:
http://8pic.ir/images/83m0ouih8mmm9s1sfl56.jpg
For this purpose I'm configuring 2 Linux system as a switch and connect 4 host to them. Then a router is added to scenario.
The configuration of the switches is:
On DUT1(Linux):... (1 Reply)
Discussion started by: zsn
1 Replies
6. Solaris
Hi,
Is it possible to VLAN tag with a ce interface on Solaris 9? Link speed is gb.
ce:0:ce0:link_speed 1000
I have a ce0 interface I would need to have access to another VLAN as well as the one it's currently on.
What commands would I need to run?
Thanks.;) (2 Replies)
Discussion started by: sparcman
2 Replies
7. Red Hat
We have two hosts in same vlan with same route rules.
One of them is not able to connect to an outside IP while in another I get "failed: Connection timed out" while testing the connectivity through netcat.
I have tried mtr /traceroute and it gives me the same results.
Is there a netcat... (1 Reply)
Discussion started by: jacki
1 Replies
8. Solaris
Have 2 nics on physical system
net0 phys 1500 up --
net1 phys 1500 up --
1. I want to create a link aggregation with LACP enabled with above 2 nics
2. Create port-group(Like we create on ESXi) with VLAN-ID 2141
3. And assign this... (0 Replies)
Discussion started by: Shirishlnx
0 Replies
9. AIX
Hi Guys,
Our lpars is currently running on 2 different vlans (20, 30). Now we have a requirement that vlan 30 needs to be change to vlan 31 at the same subnet. I'm not sure on what is the best approach for this or what change is involve on the AIX side.
This is our setup.
Network switch -... (5 Replies)
Discussion started by: kaelu26
5 Replies
10. Solaris
Hi Folks,
I am currently moving systems to a new environment, with some changes to the network requirements on the systems.
One of these changes is moving from just standard IPMP to using IPMP on top of a VLAN, I have used VLAN tagging befor without issue - however not with IPMP.
What I... (2 Replies)
Discussion started by: gull04
2 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