Search results for query: *

If every host inside the network has an address on the 192.168.x.x network, then there is no need for the secondary address (205.158.x.x) on the inside interface. That is precisely what network address translation does for you... a packet comes in bound for your mail server (let's pretend it's...

The config above would certainly correspond with what I was suggesting... Serial0 does have the 64.x.x.x address and your ISP will have a 64.x.x.x address on the same subnet on one of their router interfaces. The default route is to Serial0, so anything your router can't handle gets pushed out...

Thanks vvoip, but I think you misunderstood.

Pretty tough to say without actually seeing the router config... everything I typed above is speculation, but I can tell you this... If you are using 192.168.131.1 as the gateway when setting up TCP/IP on your workstations, then the inside address of your router is 192.168.131.1. If your...

Sure... We use all 10.x.x.x addresses on our internal network. The address on E0 is 10.2.0.x Our ISP has allocted a small block of globally routable ip addresses on the 209.191.213.x network. I have statements in the router that translate (either statically or dynamically) my internal 10.x...

192.186.31.1 is your internal network 205.158.200.x could be a range of addresses your internal addresses are translated to. 64.x.x.x could be the address your isp uses on that interface to route traffic to you.

OK... allow me to rephrase... Any "Open Source" software?

Is anyone here using anything to analyze ip accounting data from their Cisco routers? I recall trying something once upon a time that did a nice job of collecting the show ip accounting output and gathering it into nice tables... I've lost it in the shuffle. Any recommendations appreciated.

After checking the log a bit further and shutting off HostnameLookups I do see that the ip address of the client is getting logged properly, but my initial problem continues and I still wonder if it is something with my Apache config. I am running a cgi (not of my creation) that has the...

Whoops! I was looking at the Apache forum when I posted and assumed... well... my apologies.

OSX server running Apache 1.3 ... I first noticed the problem when running a cgi that was set to return the client ip address. I kept getting the address of the server returned no matter which client I connected from. I took a look at the access_log today and see that every log entry begins...

OSX server running Apache 1.3 ... I first noticed the problem when running a cgi that was set to return the client ip address. I kept getting the address of the server returned no matter which client I connected from. I took a look at the access_log today and see that every log entry begins...

No... not working. The variable is typed correctly in the script (RETURN_ADDR was just a typo here). REMOTE_ADDR returns the address of the server. Even the ssi directive in a little java script designed to display the client ip address: <!--#echo var="REMOTE_ADDR"--> returns the server ip...

You lost me Paul.

Duh... my bad. REMOTE_ADDR

Nope... just a server. One NIC, one ip address. The server sits at 10.2.0.19, I'm connecting from a workstation on the same network at 10.2.0.255. Using RETURN_ADDR Perl writes 10.2.0.19 to the log file. I'm beginning to wonder if this isn't an apache thing?

I'm just starting to dig into some Perl scripting and have run across the following issue with a script: Using the environment variable REMOTE_ADDR is returning the address of the server, not the client. I'm running this on an OS X server running Apache 1.2.27 and the host is a virtual host...