Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I experiencing a small problem with my network setup: Setup


In this network, I can ping from 192.168.3.0 to 192.168.2.0 and reverse, but it does not work with TCP connections. The handshake fails (no ack).

Below is a Wireshark capture and my config:
wireshark
icmp redirects to 192.168.3.2.

config router 192.168.2.1:
route 192.168.3.0/24 dev eth-right via 192.168.2.2  

config router 192.168.3.1:
route 192.168.2.0/24 dev eth-left via 192.168.3.2

config router 192.168.2/3.2:
route 192.168.2.0/24 dev eth-left proto kernel  scope link  src 192.168.2.2
route 192.168.3.0/24 dev eth-right proto kernel  scope link  src 192.168.3.2
tcp_timestamps = 0 / 1 no effect
tcp_window_scaling = 0 / 1 no effect
ip_forward = 1
iptables:
    *filter
    :INPUT ACCEPT [558387:1126476966]
    :FORWARD ACCEPT [7256:5227071]
    :OUTPUT ACCEPT [366250:1071395133]
    -A INPUT -p udp -m udp --sport 67:68 --dport 67:68 -j DROP
    COMMIT
share|improve this question

migrated from stackoverflow.com Oct 28 '11 at 14:05

This question came from our site for professional and enthusiast programmers.

    
192.168.2.1 and 192.168.3.1 are default gateways (via dhcp) in its subnets. –  mo01 Oct 28 '11 at 14:12
    
and i can open 192.168.2.1's webpage –  mo01 Oct 28 '11 at 14:33

1 Answer 1

up vote 0 down vote accepted

route 192.168.2.0/24 dev eth-left proto kernel scope link src 192.168.2.2 route 192.168.3.0/24 dev eth-right proto kernel scope link src 192.168.3.2

the src-attribute is the problem, it should look like this:

route 192.168.2.0/24 dev eth-left proto kernel scope link route 192.168.3.0/24 dev eth-right proto kernel scope link

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.