http://qa.mandrakesoft.com/show_bug.cgi?id=5893





------- Additional Comments From [EMAIL PROTECTED]  2003-24-09 08:55 -------
OK, I installed the new files. Now Shorewall is configured with eth0 and ppp+
wheras it used to be between eth0 and eth0. Still no route though.

In Drakconf, I first disabled the Firewall (to prevent the "existing firewall"
warning), then re-configured through Internet Connection Sharing wizard.

The client is assigned the address 192.168.1.251 but I am unable to ping
192.168.1.251 by the gateway machine. I get an error response and I see this in
the log...

Sep 24 07:44:34 desktop kernel: MASQUERADE: No route: Rusty's brain broke!
Sep 24 07:45:33 desktop kernel: Shorewall:all2all:REJECT:IN= OUT=eth0 
RC=192.168.1.1 DST=192.168.1.251 LEN=84 TOS=0

If I try to ping 192.168.1.1 from the client I get an error response see this in
the log...

Sep 24 07:46:30 desktop kernel: Shorewall:all2all:REJECT:IN=eth0 OUT=
MAC=00:02:e3:0a:55:55:00:0a:e6:4d:ea:0b:08:00 SRC=192.168.1.251 DST=192.168.1.1
LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=62985 SEQ=1
Sep 24 07:46:42 desktop kernel: MASQUERADE: No route: Rusty's brain broke!

I will attach the Shorewall status as reported via Webmin in case that provides
any clues.

Thanks.

-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date: 
description: 
On MDK 9.2RC2 I try to enable internet connection sharing but get no connection
via the client network.

I am using a Speedtouch USB modem as the connection I wish to share.

When I re-check Internet Connection Sharing, I am told it is set up but
currently disabled. I try to enable it but it never does. No error message. It
simply always stays in a disabled state.

I had a similar problem with MDK 9.1 and resolved it by using an IPtables script
instead.

Reply via email to