Hi, >assuming that the server sits inside the firewall and the client PC is >outside, you just have to open the udp port 69 for the client pc. since you >are not blocking any outbound ports (as is the normal case), you should not >have any probs. >But you might also want to consider the following: - >a) what after tftp? >b) you might have to allow dhcp requests inside your firewall (which is a big >>NO-NO) >c) All other protocols like XDCMP etc
I don't want to access server outside my LAN. And yes I've opened DHCP (or BOOTP) for my LAN. I also opened sunrpc port, NFS, XDMCP, mountd, statd ports also. I want to boot my thin client. So reason 4 setting up firewall is to define tightly (or tightly bound) what actually I needed. My thin clients are booting fine with firewall except I've to open all UDP ports (for TFTP). What I was looking for is some TFTP server which allows me to restricts its ports range so I can tightly define that I only wants this port range to be open. Anyways thanx for your advice, Ashish Shukla alias Wah Java !! Wah Java !! -- Ashish Shukla "Wah Java !!" Supercomputers are for people too rich and too stupid to design efficient algorithms -- Steven Skiena, Department of Computer Science, SUNY Stony Brook _________________________________________________________ Sent from Mail2Forum at http://www.lug-delhi.org/forums/ Read this topic online here: http://lug-delhi.org/forums/viewtopic.php?p=3114#3114 _______________________________________________ ilugd mailinglist -- [email protected] http://frodo.hserus.net/mailman/listinfo/ilugd Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/[email protected]/
