Jorge: have you set the network properly? Are you using 192.168.x.x net. The network parameter must be wrote in ../ifcfg-eth0 and ../ifcfg-eth1 file (because I suspect that you have two nics). The route command shows some aspect of your network configuration.
Julián --- Jorge Bastos <[EMAIL PROTECTED]> wrote: > Hum I got some news on this, > > I don't know why my system started to give me this > information: > > Kernel IP routing table > Destination Gateway Genmask > Flags Metric Ref Use Iface > 192.168.1.0 * 255.255.255.0 U > 0 0 0 eth0 > 192.168.0.0 * 255.255.255.0 U > 0 0 0 eth1 > default localhost 0.0.0.0 UG > 0 0 0 eth1 > > Kernel IP routing table > Destination Gateway Genmask > Flags Metric Ref Use Iface > 192.168.1.0 0.0.0.0 255.255.255.0 U > 0 0 0 eth0 > 192.168.0.0 0.0.0.0 255.255.255.0 U > 0 0 0 eth1 > 0.0.0.0 192.168.0.254 0.0.0.0 UG > 0 0 0 eth1 > > > The fact is that the hosts file is correct: > > cisne:~# cat /etc/hosts > 127.0.0.1 localhost > > I only have this there > > I know this is not squid related but if you guys can > give me a hand. > I have no idea why is it resolving 192.168.0.254 to > localhost. > > > > > > > -----Original Message----- > > From: Jorge Bastos [mailto:[EMAIL PROTECTED] > > Sent: sábado, 5 de Abril de 2008 21:23 > > To: 'Henrik Nordstrom' > > Cc: 'Amos Jeffries'; squid-users@squid-cache.org > > Subject: RE: [squid-users] client ip's > > > > This already worked with some of the 3.0 versions. > > Gonna try to play with my iptables rules and let > you guys know. > > > > > > > > > > > -----Original Message----- > > > From: Henrik Nordstrom > [mailto:[EMAIL PROTECTED] > > > Sent: sábado, 5 de Abril de 2008 19:38 > > > To: Jorge Bastos > > > Cc: 'Amos Jeffries'; squid-users@squid-cache.org > > > Subject: RE: [squid-users] client ip's > > > > > > lr 2008-04-05 klockan 14:24 +0100 skrev Jorge > Bastos: > > > > > > > I updated to last STABLE-4 on debian, but this > still happens this > > > way. > > > > What can I do more? > > > > > > Good question. > > > > > > One thing you can try is to downgrade to > Squid-2.6. If that shows the > > > same symptoms the problem is not within Squid > but most likely in your > > > firewall ruleset or something else relevant to > how the connections > > end > > > up at your Squid. > > > > > > Regards > > > Henrik > > > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
