From: thefunnel on 10 Sep 2007 07:16 Hi, I have just upgraded the software on my Pix 525 from version 6 to 7. After a reboot I attempt to set an interface IP address for the next stage of the upgrade: For some reason the interface does not work! I get "No route to host" Any suggestions would be great: pixfirewall(config)# int e0 pixfirewall(config-if)# ip address 192.168.1.1 255.0.0.0 pixfirewall(config-if)# no shut pixfirewall# ping 192.168.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds: No route to host 192.168.1.1 Success rate is 0 percent (0/1) pixfirewall# Many thanks, Paul
From: Lutz Donnerhacke on 10 Sep 2007 07:25 * thefunnel(a)aol.com wrote: > pixfirewall(config)# int e0 > pixfirewall(config-if)# ip address 192.168.1.1 255.0.0.0 > pixfirewall(config-if)# no shut > > pixfirewall# ping 192.168.1.1 > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds: > No route to host 192.168.1.1 > > Success rate is 0 percent (0/1) You need to connect the interface to a working physical counterpart. Unless the interface is not "up/up", IP transport involving this interface will not happen.
From: thefunnel on 10 Sep 2007 07:53 > You need to connect the interface to a working physical counterpart. > Unless the interface is not "up/up", IP transport involving this interface > will not happen. The firewall is connected to a live switch port: The show int e0 command outputs: Interface Ethernet0 "", is up, line protocol is up But I still get "No route to host" even if I try to ping the address from the firewall itself. In fact - even a ping to 127.0.0.1 fails! pixfirewall# ping 127.0.0.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 127.0.0.1, timeout is 2 seconds: No route to host 127.0.0.1 Very strange!
From: thefunnel on 10 Sep 2007 07:56 Hi, The interface is up/up: Interface Ethernet0 "", is up, line protocol is up But I cant even ping 127.0.0.1 from the firewall? pixfirewall# ping 127.0.0.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 127.0.0.1, timeout is 2 seconds: No route to host 127.0.0.1
From: Lutz Donnerhacke on 10 Sep 2007 08:54
* thefunnel(a)aol.com wrote: > Interface Ethernet0 "", is up, line protocol is up Fine. > But I still get "No route to host" even if I try to ping the address > from the firewall itself. Turn on logging. > In fact - even a ping to 127.0.0.1 fails! Of course. The PIX does no know about 127.0.0.1. |