shareInternet-2.2.6.pet - Puppy as router - bugfix
shareInternet-2.2.1 available
Changes in shareInternet v2.2.1:
1) Share Internet no longer conflicts with the use of rc.firewall. It uses it's own iptables code based on one of the Linux based software firewalls.
If you run rc.firewall before running shareInternet, everything rc.firewall did will be ignored. Running rc.firewall while shareInternet is running may stop it working, and is not supported.
2) Upgraded the included dnsmasq to v2.51, compiled on pup-431.
gyro
Edit: withdrawn, please use shareInternet v2.2.3, see first post
1) Share Internet no longer conflicts with the use of rc.firewall. It uses it's own iptables code based on one of the Linux based software firewalls.
If you run rc.firewall before running shareInternet, everything rc.firewall did will be ignored. Running rc.firewall while shareInternet is running may stop it working, and is not supported.
2) Upgraded the included dnsmasq to v2.51, compiled on pup-431.
gyro
Edit: withdrawn, please use shareInternet v2.2.3, see first post
Last edited by gyro on Sat 12 Jun 2010, 01:43, edited 1 time in total.
i got other problem about this software...
every 3-6 hours, other computer got disconnect network from puppy (with this software ICS) then i manual turn off this software then second, turn off then on eth1 (ISP) (like 'ifconfig eth1 [up/down]') then i turn on this software...
then it will work...so is there automatic? im tired of repeat every disconnect...
ICS = Internet connection sharing
Thanks. I'll be waiting for reply...
every 3-6 hours, other computer got disconnect network from puppy (with this software ICS) then i manual turn off this software then second, turn off then on eth1 (ISP) (like 'ifconfig eth1 [up/down]') then i turn on this software...
then it will work...so is there automatic? im tired of repeat every disconnect...
ICS = Internet connection sharing
Thanks. I'll be waiting for reply...
no... i mean this software shareinternet running on puppy linux... im not running internet sharing on windows... windows box is client. only one puppy linux is sharing internet...
what i set up network? look at below:
[INTERNET (Motorola SB5100)]<--->[PUPPY LINUX with shareInternet]<--->[Linksys WIFI ROUTER]<--->[WINDOWS (1 PC with wired & 1 PC with Wireless & 3 Handheld wireless)]
but my internet keep always disconnect every 3-6 hours (maybe for new IP address. It's dynamic IP). so i tested with Xubuntu. its really working test 24 hours but i hate all ubuntu for my old computer. because it made my old computer so slow and overload memory and processor. only Puppy Linux can do with my old computer but problem is manual turn off then turn on eth1. that's why that will make conflict with 2 ethernet card after internet disconnect.
P.S. ICS = this software shareInternet... sorry for short word. hehehe...
thanks for responding...
what i set up network? look at below:
[INTERNET (Motorola SB5100)]<--->[PUPPY LINUX with shareInternet]<--->[Linksys WIFI ROUTER]<--->[WINDOWS (1 PC with wired & 1 PC with Wireless & 3 Handheld wireless)]
but my internet keep always disconnect every 3-6 hours (maybe for new IP address. It's dynamic IP). so i tested with Xubuntu. its really working test 24 hours but i hate all ubuntu for my old computer. because it made my old computer so slow and overload memory and processor. only Puppy Linux can do with my old computer but problem is manual turn off then turn on eth1. that's why that will make conflict with 2 ethernet card after internet disconnect.
P.S. ICS = this software shareInternet... sorry for short word. hehehe...
thanks for responding...
alienx2,
Thinking about this after my last response, I'm wondering if this is a dhcp problem, since it happens some time later.
(shareInternet only starts things going, and stops things. It doesn't actually run while traffic is flowing.)
That said, can we establish which link dies, when things fail:
Can the puppy machine still talk to the internet?
Can the puppy machine still talk to the Linksys router?
Other questions:
Is the ethernet port on the Puppy machine, that is connected to the Linksys router, defined statically?
Are you using the Linksys router as a router?
Is it running dhcp as a server?
(When I do something similar I plug the puppy machine into one of the client ports of the wireless router, and stop the dhcp server on the router. Effectively using the wireless router as an ethernet switch.)
gyro
Thinking about this after my last response, I'm wondering if this is a dhcp problem, since it happens some time later.
(shareInternet only starts things going, and stops things. It doesn't actually run while traffic is flowing.)
That said, can we establish which link dies, when things fail:
Can the puppy machine still talk to the internet?
Can the puppy machine still talk to the Linksys router?
Other questions:
Is the ethernet port on the Puppy machine, that is connected to the Linksys router, defined statically?
Are you using the Linksys router as a router?
Is it running dhcp as a server?
(When I do something similar I plug the puppy machine into one of the client ports of the wireless router, and stop the dhcp server on the router. Effectively using the wireless router as an ethernet switch.)
gyro
shareInternet-2.2.2.pet
I have attached the current version of shareInternet, 2.2.2.
The only change is a tweak to the iptables firewall rules.
gyro
Edit: withdrawn, please use v2.2.3 as per first post
The only change is a tweak to the iptables firewall rules.
gyro
Edit: withdrawn, please use v2.2.3 as per first post
Last edited by gyro on Sat 12 Jun 2010, 01:45, edited 1 time in total.
Its only one problem is talk to internet... Linksys is working connect to puppy linux (tested with Remote Desktop VNC, FTP)gyro wrote:alienx2,
Thinking about this after my last response, I'm wondering if this is a dhcp problem, since it happens some time later.
(shareInternet only starts things going, and stops things. It doesn't actually run while traffic is flowing.)
That said, can we establish which link dies, when things fail:
Can the puppy machine still talk to the internet?
Can the puppy machine still talk to the Linksys router?
yes. eth0 = static IP to linksys. then eth1 = auto DHCP to internet...Is the ethernet port on the Puppy machine, that is connected to the Linksys router, defined statically?
yes but gateway to puppy linux as router.Are you using the Linksys router as a router?
only internet have dhcp.Is it running dhcp as a server?
I think you are saying that all links stay up except the link between the Puppy box and the Internet.alienx2 wrote:Its only one problem is talk to internet... Linksys is working connect to puppy linux (tested with Remote Desktop VNC, FTP)
Just to be sure, when the problem occurs can the windows box "ping" the puppy box?
If the puppy box is not running as a router, does not run shareInternet, can it maintain the link to the Internet?
I would be surprised if this were the case.alienx2 wrote:only internet have dhcp.
If you run shareInternet, then it runs "dnsmasq" to provide a dhcp service downstream to the Linkysys router, and SOHO routers usually provide a dhcp service to their clients, in this case the windows box.
I would also suspect that the Linksys expects a dhcp service upstream on the puppy box.
gyro
windows box cant ping internet even also puppy linux (with shareinternet) cant ping internet. so manual turn off eth1 (internet) then turn on eth1.. both of them ping work.gyro wrote:I think you are saying that all links stay up except the link between the Puppy box and the Internet.alienx2 wrote:Its only one problem is talk to internet... Linksys is working connect to puppy linux (tested with Remote Desktop VNC, FTP)
Just to be sure, when the problem occurs can the windows box "ping" the puppy box?
If the puppy box is not running as a router, does not run shareInternet, can it maintain the link to the Internet?
because it sound like the problem is 2 network card conflict.
yes puppy box need shareInternet to be router
linksys is working connect with puppy box (with shareInternet)... because linksys gateway ip is Ip address of puppy box.gyro wrote:I would be surprised if this were the case.alienx2 wrote:only internet have dhcp.
If you run shareInternet, then it runs "dnsmasq" to provide a dhcp service downstream to the Linkysys router, and SOHO routers usually provide a dhcp service to their clients, in this case the windows box.
I would also suspect that the Linksys expects a dhcp service upstream on the puppy box.
in puppy box, eth0 is 192.168.1.101gyro wrote: What is the static IP address on eth0 of the puppy box?
windows box is 192.168.1.102gyro wrote: What is the IP address of the windows box?
192.168.1.xxx is linksys router
yes its always working.. but linksys got disconnect.. because my internet always disconnect every 3-6 hours... there is no automatic detect DHCP in linksys settings... About test straight up to internet (motorola) without router, Windows, ubuntu is working and automatic detect after internet disconnect...gyro wrote: A silly question, have you tried connecting the linksys directly to the ethernet port of the motorola?
alienx2,
I think you are saying:
if you connect the windows box directly to the motorola, it works fine.
If you connect the linksys router directly to the motorola, then the link to the internet drops after a few hours.
If you connect the puppy box to the motorola and the linksys to the puppy box, then the internet drops after a few hours.
One guess is that the motorola often gets a different IP address from dhcp every few hours. The windows box can follow this IP address change, but neither the linksys nor puppy with the current shareInternet can follow this IP change.
The current shareInternet is not correctly setup for such a dynamic situation. I will create a new version of shareInternet, v 2.2.3, in a couple of days, that is configured for such a situation. ( I need time to setup a test situation.)
When the problem occurs, does just a reboot of the puppy box fix it?
I'm surprised that the linksys is functioning as router, with eth0 of the puppy box being 192.168.1.101 and the windows box being 192.168.1.102. Normally I would expect these to be in different sub-nets, thus I would expect eth0 of the puppy box to be something like 192.168.2.101.
gyro
I think you are saying:
if you connect the windows box directly to the motorola, it works fine.
If you connect the linksys router directly to the motorola, then the link to the internet drops after a few hours.
If you connect the puppy box to the motorola and the linksys to the puppy box, then the internet drops after a few hours.
One guess is that the motorola often gets a different IP address from dhcp every few hours. The windows box can follow this IP address change, but neither the linksys nor puppy with the current shareInternet can follow this IP change.
The current shareInternet is not correctly setup for such a dynamic situation. I will create a new version of shareInternet, v 2.2.3, in a couple of days, that is configured for such a situation. ( I need time to setup a test situation.)
When the problem occurs, does just a reboot of the puppy box fix it?
I'm surprised that the linksys is functioning as router, with eth0 of the puppy box being 192.168.1.101 and the windows box being 192.168.1.102. Normally I would expect these to be in different sub-nets, thus I would expect eth0 of the puppy box to be something like 192.168.2.101.
gyro
still same problem... i think it was dhcpcd because there is no automatic dhcp everytime in PUPPY Linux. but i tried searched some forum who similar the problem to me...
i feeling the problem similar to http://www.murga-linux.com/puppy/viewto ... c43a41c303
but there solved the problem is take a look http://www.murga-linux.com/puppy/viewtopic.php?t=51424
i didnt test that script... that sound great tricky about repeating renew dhcp every 15 minutes.. i will test it next 6 hours from now...
i feeling the problem similar to http://www.murga-linux.com/puppy/viewto ... c43a41c303
but there solved the problem is take a look http://www.murga-linux.com/puppy/viewtopic.php?t=51424
i didnt test that script... that sound great tricky about repeating renew dhcp every 15 minutes.. i will test it next 6 hours from now...
alienx2,
Normally dhcpcd does automatically renew the IP address.
But it would appear that for some folk the dhcpcd in puppy fails to do this.
Again it's a guess, but one explanation would be if some ISP's often give a different IP address, instead of renewing the old one. And the dhcpcd in puppy can automatically handle the renewing of the old IP address, but not getting a completely new one.
If my guess is correct, then the suggested script should work around the problem. You should set it to run every 2 hours.
The new version of shareInternet has more chance of being capable of coping with a changing IP address.
One way to see if changing IP address is happening, is to see what is the IP address of eth1, when it's working, and then again after you've got it working again.
gyro
Normally dhcpcd does automatically renew the IP address.
But it would appear that for some folk the dhcpcd in puppy fails to do this.
Again it's a guess, but one explanation would be if some ISP's often give a different IP address, instead of renewing the old one. And the dhcpcd in puppy can automatically handle the renewing of the old IP address, but not getting a completely new one.
If my guess is correct, then the suggested script should work around the problem. You should set it to run every 2 hours.
The new version of shareInternet has more chance of being capable of coping with a changing IP address.
One way to see if changing IP address is happening, is to see what is the IP address of eth1, when it's working, and then again after you've got it working again.
gyro
shareInternet-2.2.4.pet
Bug:
If the default route had a non zero metric, shareInternet failed to properly detect the interface pertaining to the default route. This resulted in all interfaces being detected as "inside". Thus shareInternet did not work.
Fixed in shareInternet 2.2.4. (see first post for download)
Recommended upgrade for all users of shareInternet.
gyro
If the default route had a non zero metric, shareInternet failed to properly detect the interface pertaining to the default route. This resulted in all interfaces being detected as "inside". Thus shareInternet did not work.
Fixed in shareInternet 2.2.4. (see first post for download)
Recommended upgrade for all users of shareInternet.
gyro
Yes, its called "dhcpcd".alienx2 wrote:so is there automatic?
But the version of "dhcpcd" that's in the puppy you are using, doesn't seem to be working correctly in your situation.
I have compiled a newer version for puppy 431, see http://www.murga-linux.com/puppy/viewtopic.php?t=51424
gyro