Michael, I'm sorry for losing my temper with you the other day. The problems weren't yours, they were mine. I realized that although very little I am trying to do with the "Beast" works (contrast that with the fact that the Sony rarely ever fails to configure the way I want), I am enjoying the challange. And, as long as the Sony stays healthy I've got a connection to the www. Sorry, my bad. Jerry
Jerry Kreps wrote:
Michael, I'm sorry for losing my temper with you the other day. The problems weren't yours, they were mine. I realized that although very little I am trying to do with the "Beast" works (contrast that with the fact that the Sony rarely ever fails to configure the way I want), I am enjoying the challange. And, as long as the Sony stays healthy I've got a connection to the www.
You did not say if you now got the masq. going with my 5 lines.
On Wednesday 21 March 2001 14:20, Michael Hasenstein wrote:
Jerry Kreps wrote:
Michael, I'm sorry for losing my temper with you the other day. The problems weren't yours, they were mine. I realized that although very little I am trying to do with the "Beast" works (contrast that with the fact that the Sony rarely ever fails to configure the way I want), I am enjoying the challange. And, as long as the Sony stays healthy I've got a connection to the www.
You did not say if you now got the masq. going with my 5 lines.
Sadly, they didn't work. I reread the SuSE documentation on masqing and followed ti, too. IP_FORWARDING is active (/proc/sys/net/ipv4 shows a lot of masq files listed. The problem seems to be that the command /sbin/ipchains won't recognize any kind of protocols. /sbin/ipchains -n -L responds "Incompatible with this kernel", but ip_forwarding is active in the kernel, and /proc/sys/net/ipv4/ip_forward contains a 1. /sbin/ipchains -P forward DENY responds with "Protocol not available". I've recompiled the kernel, installed SuSEFireWall via yast2 and uninstalled it. I've set rcfirewal.conf manually and rebooted. The only thing I haven't done is downloaded a 'new" ? "fresh", 'different" ? copy if ipchains. Unfortunately, this Sony is too old to get along with the 2.4 kernel and modutils. The beast can telnet into the sony and can run the Sony's localhost webpage, and via versa, but the sony does not pass any packets back to teh beast. Running iptraf I can see the beast and the DNS server at my IP hooked up, but nothing is passed back to the beast. JLK
On Thu, Mar 22, 2001 at 10:27:37PM -0600, Jerry Kreps wrote:
On Wednesday 21 March 2001 14:20, Michael Hasenstein wrote:
Jerry Kreps wrote:
Michael, I'm sorry for losing my temper with you the other day. The problems weren't yours, they were mine. I realized that although very little I am trying to do with the "Beast" works (contrast that with the fact that the Sony rarely ever fails to configure the way I want), I am enjoying the challange. And, as long as the Sony stays healthy I've got a connection to the www.
You did not say if you now got the masq. going with my 5 lines.
Sadly, they didn't work. I reread the SuSE documentation on masqing and followed ti, too. IP_FORWARDING is active (/proc/sys/net/ipv4 shows a lot of masq files listed. The problem seems to be that the command /sbin/ipchains won't recognize any kind of protocols. /sbin/ipchains -n -L responds "Incompatible with this kernel", but ip_forwarding is active in the kernel, and /proc/sys/net/ipv4/ip_forward contains a 1. /sbin/ipchains -P forward DENY responds with "Protocol not available". I've recompiled the kernel, installed SuSEFireWall via yast2 and uninstalled it. I've set rcfirewal.conf manually and rebooted. The only thing I haven't done is downloaded a 'new" ? "fresh", 'different" ? copy if ipchains. Unfortunately, this Sony is too old to get along with the 2.4 kernel and modutils.
Did you include ipchains module into your 2.4 kernel?
The beast can telnet into the sony and can run the Sony's localhost webpage, and via versa, but the sony does not pass any packets back to teh beast. Running iptraf I can see the beast and the DNS server at my IP hooked up, but nothing is passed back to the beast. JLK
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Not running the 2.4 kernel. On Thursday 22 March 2001 22:49, Konstantin (Kastus) Shchuka wrote:
On Thu, Mar 22, 2001 at 10:27:37PM -0600, Jerry Kreps wrote:
On Wednesday 21 March 2001 14:20, Michael Hasenstein wrote:
Jerry Kreps wrote:
Michael, I'm sorry for losing my temper with you the other day. The problems weren't yours, they were mine. I realized that although very little I am trying to do with the "Beast" works (contrast that with the fact that the Sony rarely ever fails to configure the way I want), I am enjoying the challange. And, as long as the Sony stays healthy I've got a connection to the www.
You did not say if you now got the masq. going with my 5 lines.
Sadly, they didn't work. I reread the SuSE documentation on masqing and followed ti, too. IP_FORWARDING is active (/proc/sys/net/ipv4 shows a lot of masq files listed. The problem seems to be that the command /sbin/ipchains won't recognize any kind of protocols. /sbin/ipchains -n -L responds "Incompatible with this kernel", but ip_forwarding is active in the kernel, and /proc/sys/net/ipv4/ip_forward contains a 1. /sbin/ipchains -P forward DENY responds with "Protocol not available". I've recompiled the kernel, installed SuSEFireWall via yast2 and uninstalled it. I've set rcfirewal.conf manually and rebooted. The only thing I haven't done is downloaded a 'new" ? "fresh", 'different" ? copy if ipchains. Unfortunately, this Sony is too old to get along with the 2.4 kernel and modutils.
Did you include ipchains module into your 2.4 kernel?
The beast can telnet into the sony and can run the Sony's localhost webpage, and via versa, but the sony does not pass any packets back to teh beast. Running iptraf I can see the beast and the DNS server at my IP hooked up, but nothing is passed back to the beast. JLK
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Jerry Kreps wrote:
I reread the SuSE documentation on masqing and followed ti, too. IP_FORWARDING is active (/proc/sys/net/ipv4 shows a lot of masq files listed. The problem seems to be that the command /sbin/ipchains won't recognize any kind of protocols. /sbin/ipchains -n -L responds "Incompatible with this kernel",
Did you compile your own kernel? Could you re-install the ipchains package?
On Friday 23 March 2001 14:45, Michael Hasenstein wrote:
Jerry Kreps wrote:
I reread the SuSE documentation on masqing and followed ti, too. IP_FORWARDING is active (/proc/sys/net/ipv4 shows a lot of masq files listed. The problem seems to be that the command /sbin/ipchains won't recognize any kind of protocols. /sbin/ipchains -n -L responds "Incompatible with this kernel",
Did you compile your own kernel? Could you re-install the ipchains package?
Yes, I needed to in order to install my Zip100 and because I wanted my scsi drive compiled into the kernel on the Sony. Except for not recognizing ipchains stuff my Sony is a dream! I don't think I need to recompile the kernel but I am going to remove and reinstall a newer (?) copy of ipchains. Thanks, JLK
participants (3)
-
Jerry Kreps -
Konstantin (Kastus) Shchuka -
Michael Hasenstein