Skip to main content
Hi,



Please excuse me for posting in EN on a NL forum, any NL replies are welcome though.



I've recently moved from Telenet to Belgacom and I'm having a bit of a problem getting port forwarding working correctly.



The ports that need forwarding are outside of the range of blocked ports.



I have a B-Box 2 (F@st3464) modem.



I have set the Firewall settings on the modem to Minimum.



I have tried adding the necessary details to Advanced -> LAN servers.



I have also tried adding my server to the Firewall -> DMZ Host.



Currently I have the setup running without LAN servers and just DMZ Host.



This worked for a number of hours (ports showed as open and services where remotely accessible) but eventually stopped working. The Security Log showed the following:



"

















Outbound Traffic Blocked - NAT out failed


"



Nearly 50 of those entries per second indicating my server IP.



According this THIS post, a reboot or restart is required to temporarily fix the problem.



My question is this: Is there a way to get port forwarding working without having to reboot/restart the modem daily?



What other options do I have to try and resolve this matter?



Any help will be greatly appreciated.

I've seen and experienced my fair share of port forwarding problems on the bbox. A lot of them were "human errors", commonly caused by misconfiguration of the bbox and/or the client device/application. Unfortunately, many of the problems were also the result of the bbox simply not doing what it's supposed to do, despite a correct configuration.

You seem to know what you're talking about, so I'm going to assume that you disabled DHCP and assigned a static local IP address to your server (and doublechecked that you forwarded the ports to that same address... I know it sounds rediculous, but you'd be surprised).



Ruling out any configuration errors, my advice would be to simply get rid of the poor routing functionality of the bbox and to buy yourself a decent router. Disable WAN PPPoE (and wireless LAN) on the bbox, connect the aforementioned router to the bbox and make it establish the PPPoE connection. The bbox is now purely acting as a VDSL modem and your own router does what it does best.

Hi Wouter,



Thanks for the reply.



Indeed I did assign a static IP to the server and the forwarding (or LAN servers) where set up to that static address. As I mentioned the problem isn't really getting it working, but rather keeping it working. Which definitely leads to me believe it is more than just a configuration problem.



As for the suggestion to use the BBox2 as a modem and put a router behind it, I'm starting to think that will be the most suitable solution.



I have a spare Linksys E1000 that I can use for this purpose.



I do have one question regarding such a setup though: Are there any considerations to take into account with Belgacom TV?



If I disable WAN PPPoE and set the Underlying Connection to LAN Bridge on the BBox2 (and then use E1000 to create the connection), will I still be able to use Belgacom TV? Should it be running from the BBox2 or the E1000?

BelgacomTV will still run from the bbox2 (on another VLAN), so no problems there.

Thanks for the confirmation on that. I look forward to giving this a try later today. Your assistance is appreciated :)

I've managed to put the BBox2 in bridge mode and have the E1000 make the connection via PPPoE.



Configuring the Port Forwarding via the E1000 now gives me the required functionality.



Considering the BBox2 is in bridge mode, I'm assuming it won't start blocking things after a number of hours of operation again. Time will tell.

The pleasure's all mine. I hope the bbox won't start acting up again, although I'm pretty confident that this setup will work.



Reageer


Forumvoorwaarden