Print

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

[joejack]

All,

can't seem to get the firewall working correctly on this router. I tried creating a default deny rule and it doesn't seem to work.

I even tried blocking/denying this rule to test:
source: LAN
startip 10.0.0.2
endip 10.0.0.254

dest: WAN
startip 1.1.1.1
endip  223.255.255.255 (was the highest ip address i can assign; if i try 224.0.0.0, it says dest ending ip address not valid)

port: all
start 1
end 65535

tested with an email application that uses port 993 and traffic is still flowing through!

i tried blocking 443 as a second rule to test and the same result. check some ssl/tls sites (google) and was still able to pull it up under https.

seems like only the first rule is valid and the rest are ignored.

[FurryNutz]

Link>Welcome!

• What Hardware version is your router? Look at sticker under the router case.
• Link>What Firmware version is currently loaded? Found on the routers web page under status.
• What region are you located?
• Are you wired or wireless connected to the router?

Internet Service Provider and Modem Configurations

• What ISP Service do you have? Cable or DSL?
• What ISP Modem Mfr. and model # do you have?

What are you trying to block?
Valid numbers could be 0.0.0.1
255.255.255.254
0 thru 65535

[FurryNutz]

Any status on this? 

All,

can't seem to get the firewall working correctly on this router. I tried creating a default deny rule and it doesn't seem to work.

I even tried blocking/denying this rule to test:
source: LAN
startip 10.0.0.2
endip 10.0.0.254

dest: WAN
startip 1.1.1.1
endip  223.255.255.255 (was the highest ip address i can assign; if i try 224.0.0.0, it says dest ending ip address not valid)

port: all
start 1
end 65535

tested with an email application that uses port 993 and traffic is still flowing through!

i tried blocking 443 as a second rule to test and the same result. check some ssl/tls sites (google) and was still able to pull it up under https.

seems like only the first rule is valid and the rest are ignored.