[nylug-talk] bad routing or general bad design?

Kiryl Hakhovich administrator at bsolution.net
Thu Jan 11 17:24:48 EST 2007


Hey fellas, i have this problem for a few days, however due to my 
limited *deep* knowledge  of  TCP/IP  i can't find a solution :)

OFT: I was trying to get Ipsec/linux + windows clients = too much effort 
and impossible to get users configure their PC's as needed.

So i went pptp road....

I have linux firewall box in the office that serve as default gateway 
for all machines inside. Now i have build another linux box that is 
running pptpd (one end looking to the internet, another to the lan). 
Windows clients can happily connect to the pptpd box and get ip address.
LAN: 192.168.0.0
PPTP  Users: 192.168.1.0

Linux box that acting as default gateway has a routing rule to route all 
192.168.1.0 over to the linux pptpd box.

When client connected, he can happily ping all servers on the LAN, 
however when he tries to access available server (for example http 
browser) on the LAN - time out happens. But once i ping the client from 
that server he is trying to access - all traffic magically starts 
flowing and user can get to it via browser.

Since pings going fine (udp) why other traffic (tcp) does not fly unless 
i ping client from the server first?


Thank you.


-- 

Sincerely,

Kiryl Hakhovich




More information about the nylug-talk mailing list