How to disable a thomson firewall

Sp00n · 8 Oct 2008 at 16:33

I've tried disabling via the web interface and also via telnet but the stupid POS is still blocking ports.

Does anyone know any magic tricks on how to stop it?

I have to add in port forwards manually within the web interface jsut to get RDP/VNC working so I can get on to the servers remotely, thats after the 2 different ways of disabling.

FrenchTart · 8 Oct 2008 at 16:42

It's normal to have to forward ports like that unless you've got a dmz set up.

Sp00n · 8 Oct 2008 at 16:44

Even if its non-nat and the firewall behind the thomson has its own public ip?

FrenchTart · 8 Oct 2008 at 16:50

Sp00n said:
Even if its non-nat and the firewall behind the thomson has its own public ip?

Perhaps not. I may have misunderstood your OP.

Sp00n · 8 Oct 2008 at 16:56

It would seem i dont fully remember my own setup.

As it stands, the bebox has the public ip, the hardware firewall sits on the 192.168.1.x range.

I suppose the only way i could do it maybe would be to create a range of 0 - 55555 or something and just forward everything that way but it just seems stupid as I am assuming its NAT enabled (dont actually have the option).

I realise now why it doesnt work, i guess its the companies own fault for not buying a proper router.

Please excuse my stupidity, its been a long old day.

/edit so I've created an application group with 0 - 55555 on the ports but the bugger still won't telnet through to the port i need :mad:

FrenchTart · 8 Oct 2008 at 17:32

Have you disabled the routers telnet? Assuming you're using the standard port.

The router has several applications running on its own ports that you need to disable when you want to run your own app behind the NAT (e.g. FTP).

#Chri5# · 8 Oct 2008 at 21:05

Which Thomson?

There's a CLI based command to properly disable the firewall. I've got some Thomson/Speedtouches documentated at work for when we've used with SonicWalls and hence don't want any firewalling on the router.