Tag Info

Hot answers tagged

4

In a typical setup with a datacenter provided switch, all your servers plus (maybe) their router will be on your private VLAN. If this is the case you should be ok. All of the datacenter's switches can see the traffic, but their other customers can't. Many setups provide a private LAN as well as an internet connection. Make sure you are transfering on ...


4

That is correct behaviour: the interface bond0.11is a VLAN-aware interface, so the only traffic that you should see on it is traffic for the VLAN of which it is a member (11), after those frames have been selected and the VLAN tags removed. If you dump bond0 you should see all the traffic that hits that physical interface, with tags intact.


4

A vlan is pretty much the same as having a separate network with separate cables and switches. So you can use any valid IP addresses you would use on a regular LAN. You can't use addresses you don't control, but can use any of the ones set aside for private usage like 10.0.0.0/8. It is best to avoid reusing the same subnets for different VLANs. Its not ...


2

Ethernet VLANs do nothing more than "partition" switches such that they act like multiple switches, with separate broadcast domains for each VLAN. (That is, broadcast traffic from one VLAN doesn't appear in another.) If you're planning on doing port-based VLANs (that is, port X will be a member of VLAN 2, port Y will be a member of VLAN 3, etc) and you're ...


2

Yes it's possible to do using an ARP spoofing attack. Or if the switch was configured for port mirroring. Services provided by companies like Amazon avoid that by placing each customer's server inside it's own VLANed environment (or something custom). To get outside the VLAN requires a router (in Amazon's case provided by an elastic IP). The net result ...


2

The vSwitch should have no special configuration. Your port groups should contain all of the actual VLAN tags. On the switch side, is VLAN 1 actually defined anywhere? See my example from: vSwitch configuration with 12 uplinks There's nothing untagged at the vSwitch level because it makes more sense to associate port groups with a VLAN once you start ...


1

Use literally ANYTHING that's Internet based. Use Skype, Yahoo, Jabber, IRC, Google, . Also, your Lync Server paired with an EDGE server allows clients to connect from externally. You can also federate your Lync with Skype or Yahoo or Jabber.


1

The Wireshark documentation on VLAN is quite clear on this. To check for both VLAN-encapsulated and non-VLAN-encapsulated packets with that IPv4 address, try host x.x.x.x or (vlan and host x.x.x.x) The manpage gives me -f <capture filter> So I think this should work: tshark -f vlan -i eth0 -V >somefile


1

Do the Trunk ports needs to be tagged or untagged on both switches? Tagged. Ports connected to devices that aren't VLAN-aware need to be untagged. Typically this would be your user-facing ports.


1

The easy solution would be to create tagged interfaces, build a bridge on each and plug the VMs into the bridges. With IOMMU you will probably be better off in terms of latency, but tagging on IOMMU is easier done inside the VM. Just make sure the switch port is set to trunk. As for load on the host, I've seen hosts with hundreds of tagged interfaces with ...


1

You cannot use IOMMU in this use case. IOMMU provides direct access to a complete physical PCI-e card for a VM. In your case, since you want each VM to be on a different VLAN, you cannot provide the whole network interface via IOMMU, since it would also move all VLANs to that VM. So, the only solution to achieve your goal is the one @dyasny wrote above, ...


1

Ahh by now I probably spent more work-hours on it than what this switch cost. It is a Zyxel GS1510-24. I found an interesting forum post about it: "It appears that it only supports dynamic (tagged) if another switch sends it a GVRP message telling it to create a dynamic VLAN. VLAN 1 is static with no way to change it and if you use the web interface to ...


1

Basically not. It is possible through using ARP Spoofing attack (when hacked server tells switch "I am Server2's ip") Sniffing on a switch (it may be hacked or configured with Port Mirroring (when traffic from Server1 to Server2 mirrors to Server3) If they are not in the same network segment, sniffing is possible on gateway Just use SSL with predefined ...


1

1. "I'm new to vlans, but I'm thinking to set one up" - If this is a production environment and you're setting up a VLAN just for the heck of it then stop. Never do anything without having clearly defined needs and outcomes. 2. "I'm wondering if I can assign the vlan any network address I want" - Why would you want to do that? Wouldn't it make more sense to ...


1

Not all switches support private VLAN's. I don't believe the 2524 provides full private VLAN support. Some of the later firmware versions did introduce port isolation, but there are some significant limitations when using port isolation like: Port Isolation is intended only for networks that do not use VLAN tagging. (The switch must be in the default VLAN ...



Only top voted, non community-wiki answers of a minimum length are eligible