2019-04-01 19:35:24

by Jeffrin Thalakkottoor

[permalink] [raw]
Subject: about selftests/netfilter test related issue

hello
i think the script nft_nat.sh is assuming devices eth0 and eth1
which may not be the case always. my suggestion is why not give the needed
network devices as arguments to the script. iam showing related
command line sessions below and error related file is attached.
---------------------------x-------------x----------------------------
$ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN mode DEFAULT group default qlen 1000
link/ether 70:5a:0f:b9:d8:5c brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state
UP mode DORMANT group default qlen 1000
link/ether 68:14:01:07:36:1f brd ff:ff:ff:ff:ff:ff
$
------------------------x-----------x---------------------------------------
$sudo ./nft_nat.sh 2> error-related.txt
ERROR: ping failed
SKIP: Could not add add ip6 dnat hook
ERROR: canot ping ns1 from ns2
ERROR: cannot ping ns1 from ns2 with active ip masquerading
ERROR: cannot ping ns1 from ns2 via ipv6
ERROR: cannot ping ns1 from ns2
ERROR: cannot ping ns1 from ns2 with active ip redirect
ERROR: cannnot ping ns1 from ns2 via ipv6
ERROR: cannot ping ns1 from ns2 with active ip6 redirect
-------------------------x---------------------------x------------------------------------

a file is attached which shows the contents of error-related.txt

/Jeffrin
--
software engineer
rajagiri school of engineering and technology


Attachments:
error-related.txt (8.04 kB)

2019-04-01 19:47:26

by Florian Westphal

[permalink] [raw]
Subject: Re: about selftests/netfilter test related issue

Jeffrin Thalakkottoor <[email protected]> wrote:
> i think the script nft_nat.sh is assuming devices eth0 and eth1

No it does not.
These are arbitrary names given to veth devices.

> Error: Unknown device type.

No Veth device support in kernel?

2019-04-01 20:02:24

by Jeffrin Thalakkottoor

[permalink] [raw]
Subject: Re: about selftests/netfilter test related issue

anyway thanks for the reply. let me look on what you said and learn

On Tue, Apr 2, 2019 at 1:15 AM Florian Westphal <[email protected]> wrote:
>
> Jeffrin Thalakkottoor <[email protected]> wrote:
> > i think the script nft_nat.sh is assuming devices eth0 and eth1
>
> No it does not.
> These are arbitrary names given to veth devices.
>
> > Error: Unknown device type.
>
> No Veth device support in kernel?



--
software engineer
rajagiri school of engineering and technology

2019-04-01 20:18:31

by Florian Westphal

[permalink] [raw]
Subject: Re: about selftests/netfilter test related issue

Jeffrin Thalakkottoor <[email protected]> wrote:
> Error: Unknown device type.

Feel free to send a patch that makes it display a more reasonable
exit+error here.

2019-04-01 20:48:04

by Jeffrin Thalakkottoor

[permalink] [raw]
Subject: Re: about selftests/netfilter test related issue

let me also work on that too. anyway thanks

On Tue, Apr 2, 2019 at 1:46 AM Florian Westphal <[email protected]> wrote:
>
> Jeffrin Thalakkottoor <[email protected]> wrote:
> > Error: Unknown device type.
>
> Feel free to send a patch that makes it display a more reasonable
> exit+error here.



--
software engineer
rajagiri school of engineering and technology