Opened 5 years ago

Closed 5 years ago

Last modified 3 years ago

#469 closed (fixed)

Remove firewall log in GUI (micro)

Reported by: soulstace Owned by: somebody
Keywords: firewall logs micro Cc:

Description

Since micro does not have the capability to log firewall messages, it might be wise to remove these options from the web interface (like you have removed other things from the web interface in micro versions).

Many dd-wrt users keep asking why logging doesn't work...

I think you will agree, functions that are not supported in micro should not appear in the GUI for micro.

Removing it might save enough space for something else, such as Tab Completion in BusyBox?, or the Networking tab in web interface.

Thanks for reading,

~ss

Attachments (3)

security_firewall_log.Png​ (11.8 KB) - added by soulstace 5 years ago.
this doesn't work in micro
https1.png​ (10.4 KB) - added by soulstace 5 years ago.
HTTPS should not be in micro
firewall.png​ (24.0 KB) - added by soulstace 5 years ago.
Firewall page render issue

Download all attachments as: .zip

Change History (14)

Changed 5 years ago by soulstace

this doesn't work in micro

comment:1 Changed 5 years ago by soulstace

  • Resolution set to invalid
  • Status changed from new to closed

Ok I feel silly. I think micro includes same web code as all other versions, yes?

In this case it would probably require even more space to disable logs than just leaving them enabled..

Or can you guys actually include smaller versions of webpages in micro version to save space?

~ss

comment:2 Changed 5 years ago by BrainSlayer

it uses the same webcode. right. but removing it will not create any more space for tab completion etc. there are more important features than the very limited console

comment:3 Changed 5 years ago by soulstace

Good point, I agree! Thanks for the info. :)

comment:4 Changed 5 years ago by soulstace

  • Resolution invalid deleted
  • Status changed from closed to reopened

Eko, I noticed you hide logging in micro. But doesn't that code for logging still get built into micro?

Or am I just misunderstanding how it works?

In other words.. Couldn't you save more space in micro (and other firmwares) by only including web code which they actually support?

Just an idea I had.

Thanks,

~ss

comment:5 Changed 5 years ago by soulstace

  • Resolution set to fixed
  • Status changed from reopened to closed

in [9312]

comment:6 Changed 5 years ago by soulstace

  • Resolution fixed deleted
  • Status changed from closed to reopened

Sorry, closed too early. Firewall page has problems in 9300.

Also, micro should not include HTTPS option.

I will look further into why Firewall page doesn't render correctly. Must be due to this ticket changes.

Screenshots coming.

Changed 5 years ago by soulstace

HTTPS should not be in micro

Changed 5 years ago by soulstace

Firewall page render issue

comment:7 Changed 5 years ago by soulstace

Sorry, typo. I meant build 9330 Eko

DD-WRT v24 RC-7 (03/19/08) micro - build 9330M Eko

comment:8 Changed 5 years ago by soulstace

IE7 says

Line 52 Char 18 Error: 'document.firewall.log_enable.1' is null or not an object Code: 0 URL: ​http://192.168.1.1/Firewall.asp

comment:9 Changed 5 years ago by soulstace

  • priority changed from minor to major
  • type changed from task to defect

comment:10 Changed 5 years ago by eko

  • Resolution set to fixed
  • Status changed from reopened to closed

Fixed in r9332

comment:11 Changed 3 years ago by anonymous

  • milestone v24 final deleted

Milestone v24 final deleted

Note: See TracTickets for help on using tickets.