Hello,

Im under debian Sage, and I have some problem with network
I have 2 network card on the server
- eth0 connected to internet via inet adr:193.xx.yy.160 Bcast:193.xx.yy.255 Masque:255.255.255.0
- eth1 connected to local via inet adr:193.xx.yy.161 Bcast:193.xx.yy.255 Masque:255.255.255.0


The other computer on localnetwork inet adr:193.xx.yy.163 Bcast:193.xx.yy.255 Masque:255.255.255.0
Wth gateway ip: 193.xx.yy.161


Take look a little drawing :

INTERNET <--------> [eth0(193.xx.yy.160) | eth1(193.xx.yy.161] <--------> [eth0(193.xx.yy.163)]


BUT ! When I try to ping 193.xx.yy.161 on the computer(192.xx.yy.163). And when I try to pîng 193.xx.yy.163 on the server(192.xx.yy.161) I have No reply !!
Anybody have some idea ?


(PS: I don't want to put the localnetwork on private ip)

Try a packet filter like ethereal and see if there are ICMP messages being sent while you are ping'ing or not.
Maybe some security measure is blocking the ICMP messages.

Have you also checked all network interfaces (are they up, properly connected, using right kind of cables)?

All work without problem with private ip like 192.168.1.*
With ethereal on the server, I receive nothing on the eth1 !

Iptable is clear, and no other firewall.


(Excuse my poor english )

You did use -I to specify the network interface (eth1) to use when ping'ing from the server to the client right?

Have you also tried other forms of communication like nmap? It can do a lot more than just send ICMP Echo Requests (ping's).

It sounds like your client is not configured properly for networking. When you change the IP address, what settings did you modify exactly?

I edit /etc/network/interfaces
and reload the interfaces with /etc/init.d/networking

Are you sure this isn't a routing problem? eth0 being your first interface and having the same address family as your internal network, I think the kernel tries to route your packets to eth0, that is, to the internet, because it takes the interfaces in order: eth0, eth1. Maybe you should execute in a shell (as root) a line like this:

ip route add 193.xx.yy.163 dev eth1

on the server( 193.xx.yy.16{0,1} )
I think it should work this way ..

serv160:/# ip route add 193.xx.yy.163 dev eth1
bash: ip: command not found

Try it without "ip" in front.

You should have the iproute2 package installed, though. I'm assuming you have at least the 'route' utility. I think it would go this way:

route add 193.xx.yy.163 dev eth1

from a root shell. Hope helps..

serv160:/# route add 193.xx.yy.163 dev eth1
serv160:/# ping 193.xx.yy.163
PING 193.xx.yy.163 (193.17.73.163) 56(84) bytes of data.
64 bytes from 193.xx.yy.163: icmp_seq=1 ttl=64 time=0.036 ms
64 bytes from 193.xx.yy.163: icmp_seq=2 ttl=64 time=0.065 ms

Thanks a lot all !