How to recover from a firewall rule that blocks or forwards port 8282



Document ID: 98070315

 

Posted Date: 2002-03-06

 

Last Updated: 2001-11-15

 

Distribution: View Public Website

 

Issue
You accidentally entered 1500 instead of 15000 when you were mapping a range of ports (15000 to 15353) to a specific computer on the public network.
Procedure
  1. From a client machine connected to the SG10, Click Start/Run... and type "telnet 192.168.1.1" and click OK.
  2. A Telnet window should launch and display this prompt:
    Red Hat Linux release 6.1 (Cartman)
    Kernel 2.2.12-20 on an i686
    login:
    Type "telnetuser" and press Enter.
  3. Type the password used for the first configured user account. If no user account were created yet, type "toshiba". Press Enter.
    NOTE: While typing the above username or password, if the user types a mistake, the Backspace key will not function as backspace; the Delete key acts as a backspace.

    NOTE: The above password is the same password as the applianceadmin account. Reset that password using any Level 3 account if this password is not known. (applianceadmin, telnetuser, and root account passwords are always kept in sync.)
  4. A successful login will display a command line prompt like this:
    [telnetuser@myserver.loc telnetuser]$
  5. Type "su -" and press Enter.
  6. At the "Password:" prompt enter the same password as used above.
  7. You now have root access and a prompt like this:
    [root@myserver.loc /root]#
  8. Type "cd /etc/rc.d/init.d" and press Enter.
  9. Type "TERM=vt100" and press Enter.
    Do not type any spaces for this. And it is case-sensitive (as is everything in Linux). Type "set" and press Enter to confirm that TERM now equals vt100, if you like.
  10. Type "cp ./firewall.custom ./firewall.custom.old" and press Enter.
    You can later copy this file back again to restore the old settings.
  11. Type "vi ./firewall.custom" and press Enter.
    You're now editing this source file. If anything goes wrong or you suspect that something might have been done wrong while inside the vi editor, press ESC and type ":q!" and press Enter. This will quit the vi editor without saving changes.
  12. Put the cursor on the line that starts the custom rule.
    Each custom rule starts with a commented line. Commented lines start with the # character. The next thing on this line is the Rule Name given by the customer on the Administration Web Site’s Add Rule page. There are many other parameters on this line as well, depending on the type of rule the customer setup.
  13. Press “dd” to delete this line.
  14. Continue to press “dd” to delete every line until the next commented line or the end of the file, which ever comes first.
    Do NOT delete the next commented line, if any.
    The total number of deleted lines will be about eight, but this varies by a few lines depending on the type of rule that was created.
  15. Type ":wq" and press Enter. This will save changes and quit the vi editor.
  16. Type “./firewall restart” and press Enter.
    This command will stop and restart the firewall without the firewall rule that we just deleted.
  17. Type "exit" and press Enter. Type "exit" and press Enter, again.
  18. Click OK when you get a "Connection to host lost." message box.
  19. Click the "X" in the upper-right to close the telnet window.
  20. Restart the Magnia SG10 appliance server.
    This is optional and should not be necessary, but it helps verify the changes are correct.
  21. Restart any Windows 95 or Windows 98 clients.
    Sometimes Windows Explorer on these operating systems has problems if it’s looking at a share that was restarted.

COMMENTS:
The assumption here is that telnet access is still available. If telnet is not available, the next suggestion would be to boot from a second SG10 hard disk, telnet into that one, and mount the problematic hard disk. Once mounted, the firewall.custom file on the mounted drive can be edited as described above. The fixed disk can then be booted from and port 8282 should be accessible again.

Export Control and EULA
Use of any software made available for download from this system constitutes your acceptance of the Export Control Terms and the terms in the Dynabook end-user license agreement both of which you can view before downloading any such software.