Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jtrout]

To start, I'm on the Beta firmware (1.11 MS_Beta B39).

First major beef: VPN pass thru is not working correctly. I have a PPTP VPN server set up behind the DIR-655 at 192.168.101.2. I have port 1723 protocol 6 (TCP) and protocol 47 (GRE) forwarded to 192.168.101.2 via the Port Forwarding page. The Internet Sessions screen shows the GRE attempt coming in from my test box outside the DIR-655, but nothing shows up in the router log. In the end, the event viewer on 192.168.101.2 and the client connecting outside the router show the same error, 806, basically saying that GRE packets are being blocked somewhere. I've tried unchecking PPTP in the ALG configuration - it makes no difference whatsoever. Any ideas?

Second: Something is broken between scheduling and Port Forwarding. I set up a schedule that should only have forwarded very specific BitTorrent ports to a machine in our house between 5 PM and 8 AM, M-Th. I suspect it doesn't know what to do with the start time being before the end time, because after 5 PM nothing changes, and the Internet Sessions pages continues to show active sessions with the machine I forward to and those port which, in theory, should no longer be forwarded. Which brings me to my second gripe about schedules - they MUST be more robust. I need to say "allow this traffic EXCEPT during 8am - 5pm, when I'm working from home." I can't possibly be the only person with this need, but there's no elegant way to do that. I did try setting up an Allow All port forwarding rule for all the time, and then a Deny All rule for the 8-5 hours M-F, but that did nothing as well. I think the scheduling stuff is completely broken, myself - or at least Port Forwarding does not seem to respect the schedules. Any thoughts on this one?

Thanks, I know that was kind of a long one. In general, I love this router. I have no other issues with it (thank God), and its uptime is insane. But these two have had me pulling my hair out on a multitude of occasions.

~JT

[jtrout]

Ok, so it looks like both machines outside my network that I was using to test are behind Cisco gear that blocks GRE packets. Just tried it again on a whim from my office, and the VPN portion works fine.

I am still curious about schedules though - they really don't seem to work right for me...

~JT

[blainem]

When setting up schedules, they may not work correctly when running past 12 midnight.  I had a tech support case on this about 6 months ago.  I had to have one schedule running up to midnight and another running from midnight until morning to get it to work properly.  I use schedules slightly differently that you are, but it is now working fine for me.

Cheers

[jtrout]

Ok, that's what I figured. It's such a pain that they can't include an inverse - like Allow Except During...  That way I could just say 8-5, M-Th, and be done with it. Instead I have to jump through all these hoops like setting up two schedules and duplicating rules to apply to each schedule. Hey, there's another one - why can we only apply one schedule to a rule? There must be a better way

[rotorboy]

Hi jtrout;

I too am having difficulty connecting to my PPTP VPN server in my office. There is no other firewall/router in the way, and it seems like the initial VPN setup exchange from client to server via port 1723 goes ok, but it appears the 655 is NOT forwarding protocol 47 GRE packets that actually engages traffic through the tunnel.

You had mentioned you were able to set forwarding of that PROTOCOL (not port) in the port forwarding page, but I have not been able to determine where to do that. could you tell me how you set that?

thanks

-avi