I recently bought a new Linksys RV082 router because my old Netgear firewall broke down, but with the Linksys admin interface I struggled to find how I could open up port forwarding for a specific IP address. Port forwarding opens the port for everyone on the Internet, and firewall access rules do not specify which LAN address the traffic should be routed to. The trick is to combine these two.
In this example we will open up the SSH port (tcp/22) for remote access for a specific Internet IP. First, you have to create the service, give it a name and enter tcp/22 as the port number used. Remember, creating a port forwarding entry will open the port to everyone, so let’s create a firewall accessrule next to block this first. Create an accessrule to deny everything on this port for any on the WAN interface. Next, we need to open this traffic for our single IP. Create an accessrule to allow this single IP on this port on the WAN interface, make sure that the allow-rule has higher priority than the deny-rule. Final step is to create a port forwarding entry, and specify that this port should be forwarded to a LAN IP. We created the port fowarding last so that the port is not wide open until we created the accessrules. Now everything should be like we wanted, port 22 is only open for a single Internet IP and is forwarded to a LAN IP.
To sum up, this is what we need to make sure only 2126.96.36.199 can use port 22 on LAN server 192.168.1.10 from the Internet.
Accessrule Priority 1, Allow SSH , WAN1, Source: 2188.8.131.52, Destination: Any
Accessrule Priority 2, Deny SSH , WAN1, Source: Any, Destination: Any
Port forwarding, TCP/22~22 -> 192.168.1.10
Me and a friend of mine decided to make a roadtrip to Nurburgring in Germany, a world (in)famous racetrack and do a couple of laps with our own cars, my Dodge Charger and his Golf GTI. This post is about the 5200 km roadtrip and the Nordschleife experience.
Recently my Netgear fvx538 firewall has been acting up, ending with pretty much total failure on the LAN side. It started with random WAN interface restarts, but now the LAN ports are hanging/locking up. Even with cables pulled out the port LEDs still are lit. The device then needs to be rebooted, and might work for a few minutes before it happens again. I searched the net for answers but only found people with the same problem, and no solution. I tried reverting to an older firmware, factory reset, disabling DHCP and dyndns service, but no luck. Seems like the Netgear is done for, too bad, it was doing good for several years.
I have now ordered a new Cisco firewall, hoping it has better quality. It should arrive in a day or two.
The summer tyres are now on! Also I have washed the car thorough so it’s all shiny, but there will probably be some rain soon enough to change that. Here is a new picture, with the new rear wing spoiler on too.
For this years pimping of my car I’ve decided to go for a wing spoiler. I ordered it from the states a few weeks ago, all painted and ready to be mounted, much cheaper than getting it from a dealer here in Sweden, atleast half the price (even with paint and shipping). Next step is just to get the summer tyres on, within a few weeks probably, and get cruising :). I will also probably spend some money on polishing this year again. Winter, salt and sand really put some annoying scratches on the body. Anyway, here is a picture of the new wing spoiler on my ride, enjoy…
Since there is still some slowness on the blog from time to time after database server change, the webserver will now also change. The change comes to effect when DNS is updated, which could take a day or two, but there will be no downtime as the site is still running on the old server for several days more.
Recently the blog and main website has been pretty slow, unreachable sometimes, due to overloaded database server. The site is now using a different server and should be much faster loading pages.