06-29-2006 05:37 AM - edited 03-09-2019 03:26 PM
When the firewall boots, I get a message about conflicting statics. Despite the message everything seems to work as expected.
Maybe I'm blind but I just don't see it:
static (inside,outside) tcp interface 3389 192.168.0.250 3389 netmask 255.255.255.255
static (dmz,outside) tcp interface 7475 10.0.0.2 10000 netmask 255.255.255.255
static (dmz,outside) tcp interface ftp 10.0.0.2 ssh netmask 255.255.255.255
static (inside,outside) tcp interface 7456 192.168.0.10 ftp netmask 255.255.255.255
static (inside,outside) tcp interface www 192.168.0.225 www netmask 255.255.255.255
static (inside,dmz) 192.168.0.0 192.168.0.0 netmask 255.255.255.0
Can you help me figure it out?
Thanks!
06-29-2006 06:41 AM
nope, looks alright to me.
06-29-2006 06:52 AM
Can you paste the error message as it appears during bootup please.
06-29-2006 07:20 AM
Unfortunately, I only got to see a part of the message on the console and I didn't have logging enabled during last boot. What I could see said "conflicting static" and it gave the config line number.
Could it have something to do with these NAT commands?
nat (inside) 0 access-list nonat
nat (inside) 1 192.168.0.0 255.255.255.0
nat (dmz) 1 10.0.0.0 255.255.255.0
06-29-2006 06:34 PM
In and of themselves, there is nothing wrong with those statements. Why don't you use hypterterm and record your session? That way you can capture the exact error message.
06-30-2006 10:52 AM
I'll do that the next time the firewall reboots - it probably won't happen for a few months though (unless there is a problem).
07-13-2006 05:54 AM
I just discovered a great command "show startup errors" - DUH?!
Here's the exact message:
WARNING: conflicting statics in startup configuration
*** Output from config line 88, "static (dmz,outside) tcp..."
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide