iptables and portmapper

English Network/Internet
#1

Hello, I have a problem here. After the system boot, or when i type #rcnetwork restart i get:

iptables-batch v1.4.4: unknown protocol ‘portmapper’ specified

Can yhou help me? Why am I getting this and how to solve this?
Thank you in advance.

#2

portmap has been replaced by rpcbind
service rpcbind start

#3

Thank you. However the problem is still not solved, so maybe i will describe it more:

After #rcnetwork restart i get those lines:

Starting Firewall Initialization (phase 2 of 2) SuSEfirewall2: Warning: no default firewall zone defined, assuming ‘ext’
SuSEfirewall2: batch committing…
iptables-batch v1.4.4: unknown protocol ‘portmapper’ specified
Try ‘iptables-batch -h’ or ‘iptables-batch --help’ for more information
SuSEfirewall2: Error: iptables-batch failed, re-running using iptables
iptables v1.4.4: unknown protocol ‘portmapper’ specified
Try ‘iptables -h’ or ‘iptables --help’ for more information

and so on with ip6tables-batch and ip6tables
It happens also when i run
service rpcbind start

I need portmap to get dhcp server working.

#4

payek wrote:

> I need portmap to get dhcp server working.
>

Why do you think so?

–
Per Jessen, Zürich (17.4°C)
http://en.opensuse.org/User:pjessen

#5

This is what I’m getting from OS12.1 share is in fstab…
Tried to mount nfs share from terminal; mount /shares/docs

Starting rpc.statd … portmapper not running failed
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use ‘-o nolock’ to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
MYPC:/ # rpcbind start
rpcbind: another rpcbind is already running. Aborting

Is there a solution to fix this issue ?

Thanks

#6

On 2012-11-19 21:06, MavGuardian wrote:
>
> This is what I’m getting from OS12.1 share is in fstab…
> Tried to mount nfs share from terminal; mount /shares/docs
>
> Starting rpc.statd … portmapper not running
> failed

In previous versions it meant that you had to start service “rcnfs” before.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))

#7

Doesn’t this mean portmapper is running ?

rpcinfo -p

program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper

Thanks for reply

#8

Am I wrong in thinking that you apply code you know from some other distro? Why not use Yast to setup NFS. On openSUSE that’s the way to do things.

#9

I’ve setup all of it in YaST,
I just usually mount the shares via terminal,

I used YaST to open NFS client ports,
I used YaST to setup NFS client service,

I did place my nfs shares in fstab, like so,
10.0.0.33:/nfs/Documents /shares/documents nfs noauto,rw,user 0 0

Is that wrong I thought all Linux work the same way on these basic configs ?
the server has not changed, and these always worked until I changed to OpenSUSE,

Thanks

#10

On 2012-11-19 22:26, MavGuardian wrote:
>
> Doesn’t this mean portmapper is running ?

I wouldn’t know.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))

#11

On 2012-11-19 23:26, MavGuardian wrote:

> Is that wrong I thought all Linux work the same way on these basic
> configs ?
> the server has not changed, and these always worked until I changed to
> OpenSUSE,

nfs has problems in openSUSE 12.2, probably related to how systemd
starts things. You might try systemv.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))

#12

If only I knew how you meant that !

I have an established nfs server I can’t get this new install of OpenSUSE 12.1 to connect to,
1 - firewall ports are open,
and since this PC connected perfectly before I changed OS to OS12.1,
I’m assuming it’s this PC,

so what am I forgetting on this client to make it connect ?

Thanks

#13

On 2012-11-20 07:56, MavGuardian wrote:

> so what am I forgetting on this client to make it connect ?

Dunno. I’m not at home where I can do tests, I only have this laptop
available.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))

#14

On 2012-11-20 07:56, MavGuardian wrote:
>
> If only I knew how you meant that !

When booting, there is a keypress to choose systemd or systemv. Try.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))

#15

Nope, not in 12.2 (GRUB2). One could install sysvinit-init, It requires deinstallation of sysvinit-systemd, after install the “old” init will be used.

#16

On 2012-11-20 15:06, Knurpht wrote:
>
> robin_listas;2505174 Wrote:
>> On 2012-11-20 07:56, MavGuardian wrote:
>>>
>>> If only I knew how you meant that !
>>
>> When booting, there is a keypress to choose systemd or systemv. Try.

> Nope, not in 12.2 (GRUB2). One could install sysvinit-init, It requires
> deinstallation of sysvinit-systemd, after install the “old” init will be
> used.

Ah. I have only tried 12.2 in vmware and with grub1, they keypress is
clearly there.

However, no need to change packages: there is a change to the kernel
line that has the same effect. You can have two entries in grub to
choose systemd or systemv. But I don’t remember what exactly you have to
change, I’m not at home.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))

#17

can be done by adding

 init=/sbin/init

to the kernel boot-options line

One would have to make one entry with the added boot option, and a copy of it without

#18

The solution is to write a systemd service that will wait for rpcbind before starting nfs. A brutal hack is to introduce a 5 seconds delay in after local (sleep 5). That’s what I do on openSUSE, Fedora and ArchLinux. I’ve posted this hack a couple times. Search the forum and you’ll find it.

According to my experience, 4 seconds delay is too short. Who did say that systemd is faster?

I wouldn’t boot in sysvinit just because of this.

#19

Notice that to connect to 12.1 NFS servers, the totally anti-systemd function I called “runafter” works for me. See this post: http://forums.opensuse.org/english/other-forums/development/programming-scripting/469832-running-commands-depend-process-being-started-after-local.html. On 12.2 machines however, my after.local script looks like this:


#!/bin/sh
**timeout=5**
fileserver=spock

printf "\033;34;1mRunning after.local "

exec > /var/log/afterlocal.log 2>&1

date +"after.local executed on %c"

# run a command after a given process  
function runafter {
proc=$1
shift
 -x $proc ] || return 1
while ( ! /sbin/checkproc $proc ) ; do
        printf "Waiting for %s
" $proc
        sleep $timeout
done
$* 
}

LMOUNT=/usr/local/bat/lmount4

**sleep $timeout
**
# mounting fileserver
test -x $LMOUNT && runafter /sbin/rpcbind "$LMOUNT -m $fileserver"

You have to create and enable an after.local systemd service in order to use the after.local script in systemd. How to is explained in the forum.

#20

On 2012-11-20 17:06, Knurpht wrote:
> One would have to make one entry with the added boot option, and a copy
> of it without

Right, that’s the one, thanks.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))