Jump to content

Another connection sharing query


Horty
 Share

Recommended Posts

Hi all.

 

I have a small peer to peer network consisting of one XP box and one MDK 10 OE box. Both systems are configured with static ip addresses and could see each other no problems.

 

 

Until tonight that is. I decided it was time to play around with connection sharing, and tried enabling it with the supplied MCC wizard. The result being that connection sharing didn't work (I'll sort that out later), and I can no longer see the other computer or its shares.

 

I've tried disabling connection sharing through the wizard, but to no effect. I also disabled squid, also to no avail.

 

No luck with ping either.

 

My network is a simple crossover cable connection, while my internet connection is dial up.

 

What can I do to get my shares back?

 

Thanks.

 

ipconfig as follows :

 

eth0 Link encap:Ethernet HWaddr 00:00:21:E0:64:FD

inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0

inet6 addr: fe80::200:21ff:fee0:64fd/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:1981 errors:0 dropped:0 overruns:0 frame:0

TX packets:2350 errors:2063 dropped:0 overruns:0 carrier:4124

collisions:35060 txqueuelen:1000

RX bytes:289330 (282.5 Kb) TX bytes:523385 (511.1 Kb)

Interrupt:11 Base address:0xe800

 

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:2475 errors:0 dropped:0 overruns:0 frame:0

TX packets:2475 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:195813 (191.2 Kb) TX bytes:195813 (191.2 Kb)

 

ppp0 Link encap:Point-to-Point Protocol

inet addr:203.214.106.205 P-t-P:203.89.203.11 Mask:255.255.255.255

UP POINTOPOINT RUNNING NOARP MULTICAST MTU:576 Metric:1

RX packets:1723 errors:0 dropped:0 overruns:0 frame:0

TX packets:1339 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:3

RX bytes:679392 (663.4 Kb) TX bytes:141313 (138.0 Kb)

 

[moved from Software by spinynorman]

Link to comment
Share on other sites

Thanks for the reply, streeter.

 

I (briefly) turned off the firewall, and was able to browse each computer again, so I assume that the redirection to squid rule which was added to the firewall was the culprit.

 

I had a look in /etc/shorewall/rules and found the redirection to squid, which I disabled. Is there anything else I have to disable?

Link to comment
Share on other sites

You need the masquerading rule.

 

Have a look at my 'work in progress' ICS_with_modem repair howto page - I am writing it for exactly your situation...

 

I don't use shorewall, so can't comment on the reappearance of rules - use iptables rules in /etc/rc.d/rc.local to disable them for now - this file is read after everything else when you boot up. See the howto.

 

Chris

Link to comment
Share on other sites

Thanks for the link, streeter. I'll definately use it. For the moment, though, I'm going to sort out what has happened to the Shorewall rules, policies, etc. If Shorewall is supposed to simplify iptables, I'd hate to configure iptables itself! :wall:

 

Might get firestarter.

 

Horty

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...