/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting!
/* ALSO: Don't quote this header. It makes you look lame :-) */
I did try with other client machines with the same results (both linux and win
clients). It does seem strange that both telnet and ftp stopped working at the
same time masq did. Is there a way to scope out what packets are doing
internally instead of just on the interface? I'm using ethereal at the moment,
but I can't tell what happens to the packets between eth1 and eth0 - from my
perspective they just seem to get dropped when I try to ping the outside
world, yet I can ping eth0 just fine from the internal net.
Michael Best wrote:
> On 29 Jul 2001, Trent Brown wrote:
>
> > I tried ipchains --flush and then from the command line issued just
> > /sbin/ipchains -A forward -i eth0 -s 192.168.2.0/24 -j MASQ
> > with the same results. Snooping on eth0 still shows no packets being
> forwarded,
> > though they arrive fine on eth1. Something very wacky is going on here.
>
> You said that you cannot telnet from an internal machine to your server
> machine. Since that is completely unrelated to MASQ, it appears that the
> problem may be in the network card. Can you ping another internal machine
> from your server?
>
> -- Michael Best
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/ --
THIS INCLUDES UNSUBSCRIBING!
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.
