(old)Puppy Linux Discussion Forum

Project withdrawn. Internet sharing through software is a legacy concept that is now better handled through inexpensive hardware.

-----------------------------

Have you submitted this to Woof-CE?

how submit to Woof-CE

Go here:
https://github.com/puppylinux-woof-CE/woof-CE
Select "new pull request"
Supply the needed information. New code, file, suggestion, etc......

As I understand. If it is something that is accepted by the Woof-CE team members, it will be added to Woof-CE.
May also get more input, from others, and modified, before adding to Woof-CE. Depends on what it is.

Example pull request:
https://github.com/puppylinux-woof-CE/w ... issues/730

rcrsn51 wrote:This kernel module used to be a standard component of Puppy kernels but has disappeared from recent versions.

Hi @rcrsn51

This is probably a kernel config issue.....the relevant lines in DOTconfig seem to be:

CONFIG_NF_NAT_MASQUERADE_IPV4=m
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_NF_NAT_MASQUERADE_IPV6=m
CONFIG_IP6_NF_TARGET_MASQUERADE=m

and in 4.5.2-xenial these are all not set:
e.g. # CONFIG_NF_NAT_MASQUERADE_IPV4 is not set

When I next do a kernel build (4.6.1 most likely) I'll make these changes for IPV4.

@Bigpup - So this is not a woof-ce issue other than for the DOTconfigs included in kernel-kit configs_extra which haven't been updated for some time (but I suspect most kernel builders don't get their DOTconfig from there).

Cheers
peebee

The 32-bit pae kernel 4.6.1 with masquerade module enabled is available at:

http://smokey01.com/peebee/slackocurrent/kernel/

peebee wrote:(but I suspect most kernel builders don't get their DOTconfig from there).

I have asked this question before. If woof is meant to standardize Puppy and contributors are expected to work through woof, then why are kernel builders doing their own thing?

Surely a kernel is the MOST important thing to be standardized from one Puppy to the next.

rcrsn51 wrote:

peebee wrote:(but I suspect most kernel builders don't get their DOTconfig from there).

I have asked this question before. If woof is meant to standardize Puppy and contributors are expected to work through woof, then why are kernel builders doing their own thing?

Surely a kernel is the MOST important thing to be standardized from one Puppy to the next.

Think that needs to be raised in the Woof-CE thread or on the email list at GitHub.....

Guess it also depends on whether we're talking about an "official" Pup or an unofficial one: as per

http://puppylinux.com/

rcrsn51 wrote:Project withdrawn. Internet sharing through software is a legacy concept that is now better handled through inexpensive hardware.

-----------------------------

Aren't many people here though interested in legacy software/equipment?

I was search for a wireless hotspot pet that I though you made but can't find it