Throwback time

December 18th, 2020 1 comment

I was browsing the wayback machine and thought I’d post a screenshot of our page back in December 2004. Back when we all had more time for playing around with game servers and fun ūüôā


Categories: -si.ka- Tags:

WiFi SSIDs on different VLANs

January 27th, 2019 No comments

It’s been 10 years or so since I’ve posted anything meaningful to the network so I decided to it might be nice to start cross posting some of my technical or interesting topics from my personal blog here. Original.

I thought I’d do a quick write-up covering WiFi SSIDs on multiple VLANs, something that might be useful in a home setup, separating SSIDs better from one another. While I usually prefer the CLI, a lot of the devices mentioned here only (or mainly) use a web GUI for configuration management, so this posting will include a lot more screenshots than my usual postings. This posting won’t contain anything exciting for people who run and support networks professionally (mostly just a “so what options are available on SOHO hardware?”), and may even be overly simple and assume settings you wouldn’t do in a professional setup. But it is useful for homelab enthusiasts looking to build a more complex setup than “everything on the same VLAN/network” or trying to figure out “how do I use VLANs, give me an example”.

Ubiquiti and Netgear have some reasonable priced network gear that I’ve written about in the past¬†that behave decent in home networks. For out little setup today we will have a WiFi access point with multiple SSIDs, two switches, and a firewall/router. We will be focusing on the configuration of the WiFi Access Point (UniFi AP) , the two Netgear switches (GS105Ev2 / GS108Ev3) and the Ubiquiti Router (Edgerouter X).

Our goal is to have two SSIDs on the access point, one for the “normal” devices (VLAN 1), and one for separate devices (VLAN 178). Since the router to VLAN 178 is on a different switch than the access point we also need to trunk both VLANs across the network. Another way of looking at it, is that we are expanding Subnet/VLAN 178 into our network (but limiting it to the WiFi Access points). 178 doesn’t hold any special meaning, you can use any VLAN number you want, just chose 178 because the subnet in this test setup was

Here is a diagram of our test setup:

VLAN 1: The management and main client VLAN
VLAN 178: Subnet 178, 2nd WiFi network

Netgear 1

Port 1: Connection to Netgear 2
Port 5: Access Point

Netgear 2

Port 1: Connection to Netgear 1
Port 8: Edgerouter


eth0: Connection to Subnet 178
eth1: Connection to Netgear 2


Wireless Configuration

In the UniFi controller go to Settings->Wireless Networks either create a new network or edit an existing one. If you go into the advanced options area, you will find the VLAN setting for that SSID. Activating the option and setting a value means the access point will tag all packets from that SSID to the specified VLAN number.

In the network overview below we see that packets from one network are tagged with VLAN 178, and packets from the other network are untagged (the switch configuration will take care of deciding which VLAN untagged packets are part of).

Netgear Configuration

The Netgear devices only have a VLAN 1 defined by default, so the first step will be to add VLAN 178 to both of them. Enable Advanced 802.1q (VLAN->802.1Q->Advanced->VLAN Configuration), enter the VLAN ID 178 in the box and click on “Add” at the top.

Now let’s move on to the¬†VLAN Membership configuration. To switch settings, just click on the port and it will switch from tagged->untagged->none.

Netgear 1 device

For VLAN 1 we want port 1 to be (T)agged since it is the trunk to the next switch, and all other ports (U)ntagged since they will be dealing with untagged VLAN 1 traffic. The PVID will also be set to 1 for all ports.

For VLAN 178 we want port 1 to be (T)agged since it is the trunk to the next switch, port 5 (T)agged since it is the connection to the access point, and all other ports “none” since none of those ports are part of VLAN 178.



VLAN overview after changing all the settings:


For this scenario it is sane to leave the Port PVID configuration to PVID 1 on all ports. You could change a port to 178 if you are expecting untagged traffic on that port that needs to be in VLAN 178.

Netgear 2 device

Similar configuration as the first switch so I’ll skip the screenshots. Port 1 is the connection to the Netgear 1 device, port 8 is connected to the Edgerouter.

    • all ports PVID 1
    • VLAN 1 Tagged port 1 and 8, all other ports untagged
    • VLAN 178 Tagged port 1 and 8, all other ports none

Edgerouter Configuration:

Make sure the interface switch0 spans all ports you want to use VLANs on. Add the two VLANs 1 and 178. They should show up in the list as switch0.1 and switch0.178, and you can apply firewall rules to these interfaces to restrict traffic if you are doing any routing between the two networks.
We will want to tag everything from Subnet 178 as VLAN 178 on the interface connected to that network (eth0 in our setup), and allow VLAN 178 on the outgoing interface (eth1 in our setup). The Edgerouter doesn’t need us to specifically allow VLANs already set by the PVID, only additional VLANs need to be specified in the vid field.

Where to go from here?

You could put servers or virtual machines in their own subnet/VLAN and then use a firewall to restrict access between the different networks.

Adding more Access Points is straightforward, UniFi automatically applies the wireless configuration to all Access Points it manages, so all you need to do is take care of the switch port configuration.

Privacy Policy

May 22nd, 2018 No comments

Soon new laws will go into effect in the EU regarding data privacy. I assume anyone reading this has already noticed everyone updating their privacy policies. The German version of the laws exempt private websites, but the exact definition of what “private” means is a bit unclear.

To err on the side of caution we also updated our privacy policy, our impressum, and took the necessary steps behind the scenes to be complaint with the laws. The following links/forms are also in the policy itself, but for easier access:


Submit a request to rectify data:


Categories: Internet Tags:

Vodafone DSL and settings for LinkSys X3500 router

August 19th, 2017 No comments

Since I had to fiddle with the settings at the router here is what finally worked for me:

RFC 2516 PPPoE

Multiplexing: LLC
QoS Type: UBR
PCR: default (4000)
SCR: default (4000)
VPI: 1
VCI: 32
DSL Modulation: ADSL2+

Username: 1und1/
Password: [your password]

Note: This works for ADSL based connections. VDSL is a different topic.

Categories: -si.ka-, Internet Tags: , ,

Cisco 4410N: strange solution for ‘Found beacon stuck’ or ‘stuck beacon; resetting’

April 10th, 2014 No comments

We have three Cisco 4410n (WAP4410N-E V02 to be precise) access points delivering wireless lan in our offices. All of them serve the same SSID on different channels. This way we don’t need a roaming controller and have a cheap, simple setup. This worked quite well in the past months. But now and then two of the three boxes stop working for no apparent reason. They can’t be reached over the wired interface and they don’t accept any clients (though connected clients still seem to work).
Using a syslog daemon I found many many of the following two lines:
User.Info host3 Apr 10 17:28:25 host3 syslog: Found beacon stuck, down and up the VAP interface.
Local0.Info host3 Apr 10 17:28:22 host3 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
According to sources on the internet these messages are related to the problem.

All access points are alreay up-to-date regarding the firmware release ( Obviously Cisco doesn’t put any more efforts into a new firmware for this product.

I started experimenting with different settings. Some sources suggest increasing the beacon interval time. But this didn’t change anything. Then I compared the settings between the three boxes: all settings are the same besides the wifi channel. So I changed the channels and suddenly the error messages on the syslogd disappeared. As it turned out the errors start as soon as I configure an ap for wifi channel 9 or higher. I don’t understand how a different frequency makes a difference on things like dma and interrupts. So, lets see how things turn out in the next few days.

Categories: Information Technology Tags:

In the past, everything was better!

June 30th, 2013 No comments