Sponsored Content
Special Forums IP Networking network segment use vlan, linux vconfig and AT-GS950 Post 302252118 by penyu on Tuesday 28th of October 2008 09:30:32 PM
Old 10-28-2008
Question network segment use vlan, linux vconfig and AT-GS950

Dear all,

I have a Allied Telesyn AT-GS950 16 port switch.
All hosts&router have rtl8139 NICs.
OS : Slackware linux 12.1.
I use a switch with vlan technique to separate my network to some segment.

here my plan:

router eth0 ---> switch port 1
switch port 5 <--- eth0 host A
switch port 6 <--- eth0 host B

in eth0 of router, I make two vlan :
Code:
# modprobe 8021q
# ifconfig eth0 0.0.0.0 up
# vconfig add eth0 5
# ifconfig eth0.5 172.16.5.1 netmask 255.255.255.0 up
# vconfig add eth0 6
# ifconfig eth0.5 172.16.6.1 netmask 255.255.255.0 up

host A :
Code:
# ifconfig eth0 172.16.5.2 netmask 255.255.255.0 up

host B :
Code:
# ifconfig eth0 172.16.6.2 netmask 255.255.255.0 up

Arrange vlan configuration in switch :
Code:
VLAN_ID    VLAN_NAME     VLAN_MEMBER
1        Default VLAN   Untag:1; Tag:-; Not_member:2-16
5        vlan5              Untag:5; Tag:1; Not_member:2-4,6-16
6        vlan6              Untag:6; Tag:1; Not_member:2-5,7-16

ping result to both host A and host B from router gave same result : Destination Host Unreachable
ping command :
Code:
# ping 172.16.5.2 -I vlan5
# ping 172.16.6.2 -I vlan6

Please help, there's maybe I have wrong concept about vlan configuration?
Thank you very much.


Regards,
Denny
 

10 More Discussions You Might Find Interesting

1. Solaris

VLAN on SF280

hi, i tried to configure an VLAN interface on my SF280 based on the documentation on docs.sun.com # ifconfig eri1000 plumb up Oct 21 13:41:26 cmsmaster ip: ip_rput_dlpi(eri1000): DL_ERROR_ACK for DL_ATTACH_REQ(11), errno 8, unix 0 ifconfig: SIOCSLIFNAME for ip: eri1000: no such interface... (2 Replies)
Discussion started by: pressy
2 Replies

2. IP Networking

Network Access on Different Segment

I do have 2 different segment network which different platform on each segment. E.g. 20 segment, Windows OS can talk to Unix OS and 21 segment practice same rule. Further more, Windows OS from 20 segment can talk to 21 segment other OS but only the UNIX OS in 20 segment fail to talk to 21 segment.... (3 Replies)
Discussion started by: HASM
3 Replies

3. IP Networking

what is wrong with VLAN???

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

4. AIX

how to know the vlan id?

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

5. Programming

Data segment or Text segment

Hi, Whether the following piece of code is placed in the read-only memory of code (text) segment or data segment? char *a = "Hello"; I am getting two different answers while searching in google :( that's why the confusion is (7 Replies)
Discussion started by: royalibrahim
7 Replies

6. IP Networking

Implement inter vlan routing with Linux

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

7. Solaris

Solaris 9 VLAN tagging with ce interface

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

8. Red Hat

Network issue in same vlan

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

9. Solaris

Solaris non-global zone network vlan

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

10. Solaris

IPMP over VLAN questions.

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
VDEQ(1) 						      General Commands Manual							   VDEQ(1)

NAME
vdeq - Virtual Distributed Ethernet wrapper for QEMU/KVM virtual machines SYNOPSIS
vdeq qemu [ --mod octalmode ] QEMU_OPTIONS -net vde[,vlan=n][,sock=socketpath][,port=n] QEMU_OPTIONS vdeq kvm [ --mod octalmode ] KVM_OPTIONS -net vde[,vlan=n][,sock=socketpath][,port=n] KVM_OPTIONS vde{qemu_name} [ --mod octalmode ] QEMU_OPTIONS -net vde[,vlan=n][,sock=socketpath][,port=n] QEMU_OPTIONS OLD SYNOPSIS
vdeq qemu [ --mod octalmode ] [ -sock socketpath [ ,socketpath [ ,... ] ] ] [ qemu_args ] vde{qemu_name} [ -sock socketpath [ ,socketpath [ ,... ] ] ] [ qemu_args ] DESCRIPTION
vdeq is a wrapper to start a QEMU/KVM virtual machine connected to a VDE network. It uses the qemu/kvm -tun-fd parameter to set up the connection with a vde_switch. The command vdeq qemu -b c -hda=sampledisk starts a qemu machine which boots from the sampledisk image and has a ne2000 ethernet interface connected to the standard vde_switch. The command vdeq kvm -b c -hda=sampledisk starts a kvm machine which boots from the sampledisk image and has a ne2000 ethernet interface connected to the standard vde_switch. It is also possible to create symbolic links to the vdeq executable to have a simpler command. If the link has a name that begins with vde the remaining part of the name is taken as the qemu command. For example if vdeq is linked to vdeqemu: vdeqemu -b c -hda=sampledisk starts qemu as above. If vdeq is linked to vdekvm: vdekvm -b c -hda=sampledisk starts kvm with the same parameters. The new syntax is consistent with the new Qemu 0.8.0 network parameters. Using vdeq is possible to specify a vde interface in the same way as user,tap or socket interfaces. The sock= parameter can be used to use a specific socket. Please note that what qemu names as vlan is not related to the 802.1q VLAN managed by the vde_switch. port= can be used to specify the port of the switch, otherwise the first allo- catable port is assigned. The following command run a qemu VM with two ethernet interface connected to the standard switch and to the switch with local socket "/tmp/my.ctl", port 10, respectively vde qemu -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10 vdeqemu -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10 The following command run a kvm VM with two ethernet interface connected to the standard switch and to the switch with local socket "/tmp/my.ctl", port 10, respectively vde kvm -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10 vdekvm -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10 The old syntax can be used with Qemu 0.8.0 but all the vde interfaces are assigned to vlan 0. vdeq qemu -sock /tmp/vde.ctl,/tmp/my.ctl -b c -hda=sampledisk vdeqemu -sock /tmp/vde.ctl,/tmp/my.ctl -b c -hda=sampledisk both start qemu with one ethernet interface connected both to the standard switch and to the switch with local socket "/tmp/my.ctl". OPTIONS
--mod octalmode, specify the mode for comm socket. -sock socketpath, specify the UNIX socket to be used by local programs for joining the VDE. The default value is "/tmp/vde.ctl" It is also possible to indicate several socketpath (comma separated, no blanks): in this case several interfaces are defined. The first socketpath is connected to the first ne2k interface and so on. -h, -help, --help print a Usage help. NOTE
Qemu has changed its syntax for networking (cvs Nov.15 2005). As a temporary solution use vdeoq and vdeoqemu instead of vdeq and vdeqemu if you are running a qemu with the old syntax. By default qemu uses the same MAC address for every virtual machine, so if you plan to use several instances of qemu be sure to explicitly set a different MAC address for each virtual machine. While generating your address beware to not use broadcast/multicast reserved MACs, ethernet rules say: the multicast bit is the low-order bit of the first byte, which is "the first bit on the wire". For example 34:12:de:ad:be:ef is an unicast address, 35:12:de:ad:be:ef is a multicast address (see ETHERNET MULTICAST ADDRESSES section in http://www.iana.org/assignments/ethernet-numbers for more informations). NOTICE
Virtual Distributed Ethernet is not related in any way with www.vde.com ("Verband der Elektrotechnik, Elektronik und Informationstechnik" i.e. the German "Association for Electrical, Electronic & Information Technologies"). SEE ALSO
vde_switch(1), vde_plug(1), vde_plug2tap(1), dpipe(1). AUTHOR
VDE is a project by Renzo Davoli <renzo@cs.unibo.it> Virtual Distributed Ethernet December 6, 2006 VDEQ(1)
All times are GMT -4. The time now is 10:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy