similar to: multiple vlan in dom0 and domu

Andrew and Dennis are spot on. Their conclusions about your server being connected to an access port and not a trunk port would be my conclusion as well. On Sat, Jan 24, 2015 at 9:11 AM, Dennis Jacobfeuerborn < dennisml at conversis.de> wrote: > Hi Boris, > what I'd like to know is the actual VLAN configuration of the switch > port (link-type and tagged and untagged VLANs).

Do you need the whole configuration? On the switch end, we have the relevant VLAN (VLAN 48) with the assigned IP address of 192.168.48.101 and the range of ports (Gi1/0/1 - Gi1/0/8) assigned to that VLAN. Seems - and acts - like a legitimate setup and works fine, except for this particular instance. Thanks. Boris. On Fri, Jan 23, 2015 at 8:54 PM, Dennis Jacobfeuerborn < dennisml at

I''m playing around with VLAN''s and I have a VLAN capable (layer 2) smart switch. I see a steady stream of martians in the logfile if I have the routefilter option set on the loc zone interfaces in /etc/shorewall/interfaces. I have two interfaces in the loc zone, eth1 and vlan2 respectively. vlan2 is an 802.1q trunk going towards the switch. Is this the expected behavior in

Thank you everyone. OK, the mystery deepens, I guess. The machine does need to support several VLAN's, it is currently on a trunkport (8021q encapsulated), it made it into the ARP table - which I specifically tested for by physically unplugging the table, clearing the ARP table and plugging it back in. The ARP table currently looks like this: hq#show arp Protocol Address Age (min)

Hi -- The environment we have is as follows, Domain controller: samba 3.0.14a running Solaris 9/X86 Authentication: openldap 2.2.14 Clients: Windows XP with SP2 The issue I met: If both clients and Samba server are on the same physical switch (also same subnet), the clients can join the domain and users can log into their domain accounts without any problem. However, if the clients

Hi, The attached patches enables the bridge to filter and forward packets according to their IEEE 802.1q headers. The goals behind this change include : - Enable running STP on 802.1q tagged networks. STP packets must be untagged. It isn't obvious how else to enable STP with the current bridge and vlan code. - Add native support for an untagged vlan. Currently an untagged vlan can

<I apologize if this arrives twice... I sent it first from an non-subscribed address, don't know if that'll get to the list or not --JJ> Hi folks, I have an implementation question regarding bridging on a linux box between a catalyst trunk port and a cisco 26something w/802.1q subinterfaces. So right now, there's no vlan trunking going on on the link my bridging firewall sits

Hello. I''m trying to use vlan in domU, but have something strange: I created bridge on eth0. This interface was configured as trunk with vlan 300, 301. I use this bridge in my domU, and I can see tagged packets when run tcpdump in domU. Also I created interface on domU to work with vlan 300. On this interface I see untagged packets in vlan300. And everything looks fine. But when

I''m trying to implement simple untagged vlans on our switch and have misconfigured something.. ISP gw is on the default vlan1 (untagged) Router eth1 is setup on the switch with default vlan1 and member of vlan4. eth0 is default vlan4 which connects to the clients that are all default members of vlan4 eth0 is x.x.x.86/28 This is what clients are connecting to as their gw.. (no

On 25 January 2015 at 15:12, Boris Epstein <borepstein at gmail.com> wrote: > OK... but why does it need to be a trunk port? > Because a trunk port will "trunk" the vlan. A VLAN is basically a 4 byte "tag" that gets injected into the packet header when the packet enters the VLAN network. When we trunk a VLAN we say to the switch "pass packets on VLAN x but

I've searched around but haven't found a definitive answer yet, is it possible to kickstart from a tagged VLAN? I found this bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=431915 But I can't find out how far the vlan support goes. I haven't found anything about it in any kickstart docs. I have two tagged vlans: Vlan 100 - server subnet Vlan 101 - backup subnet From

Hi, all. I see that the Polycom SoundPoint IP 330 supports VLAN... but I don't quite see how that works. Do you point a non-VLAN'd segment at it (akin to when you uplink a VLAN_enabled switch), and have the phone implement the VLAN? Or...? *puzzled* Thanks much, -Ken

Hello to everybody, Sorry if my english isn?t very good. I need pass 802.1q through a VPN between two offices. I have mounted a WRT54GL, with OpenWRT firmware, conected to a switch trunk port in both offices. In the switch of the first office I have created five tagged VLANs and I need pass these VLAN to the second offices where it has created it too. Can I do this with Tinc in HUB/Switch

Just curious, if I have my Polycom IP 550 phone VLAN tag 30, will the packets I send from my PC(on the PC port of the phone) have the same VLAN tag? THe PC is sending untagged packets. This e-mail, facsimile, or letter and any files or attachments transmitted with it contains information that is confidential and privileged. This information is intended only for the use of the individual(s) and

Hi. I''ve installed our 1st Virtualized server using Xen. I''ve managed to create & populate a VM that''s going to be used as our office mail server. Everything seems to work ok -- I can send/receive email to/from the ''real world''. I''ve read a bunch at the Xen wiki about routing, and bridging, and security. Wow! Lots of stuff to digest

Hi, I encountered a problem when creating a VLAN interface according to the Red_Hat_Enterprise_Linux-7-Networking_Guide. I configuered the parent interface ifcfg-eno1 as follows: DEVICE=eno1 TYPE=Ethernet BOOTPROTO=none ONBOOT=yes And I created a new file named ifcfg-eno1.5, the content is: DEVICE=eno1.5 BOOTPROTO=none ONBOOT=yes IPADDR=192.168.81.3 PREFIX=24

hi everyone, I'm trying to get vlans tagged in libvirt as my switch's end (yes traffic will be leaving the host and into network switches) allows only tagged vlans. But with network as such: ...   <portgroup name='vlan-55'>     <vlan trunk='yes'>       <tag id='55'/>     </vlan>   </portgroup> </network> and guest as:    

Hello all, I have a machine running Centos 6.6 connected to a port on a Cisco Catalyst 3750 series switch. That port is part of VLAN 48. I have VLAN 48 on the CentOS machine too. The IP network on VLAN 48 is 192.168.48.0/255.255.255.0. The address on the CentOS side is 192.168.48.101, the address on the Linux end ought to be 192.168.48.100. When I only bring up eth0.48 VLAN device with the

we would like setup VLAN on CENTOS 5.X and 4.x. Only VLAN will active, but primary LAN NOT active. E.g "eth0" inactive, but "eth0.2" active. I have been tried several ways, but never successful. Any ideal? ______________________________________________________________________________________________________ ?????????Yahoo!??????2.0?????????????

Changes since v9: * series re-ordering so make functionality more distinct. Basic vlan filtering is patches 1-4. Support for PVID/untagged vlans is patches 5 and 6. VLAN support for FDB/MDB is patches 7-11. Patch 12 is still additional egress policy. * Slight simplification to code that extracts the VID from skb. Since we now depend on the vlan module, at the time of input skb_tci is