Profile pic

SpongeB0B, spongeb0b@programming.dev

Instance: programming.dev
Joined: a year ago
Posts: 19
Comments: 10

RSS feed

Posts and Comments by SpongeB0B, spongeb0b@programming.dev


Thanks everyone,

I figured out also the missing ./ but meanwhile I got already 4 reply ! \

Thanks so much !


Ideally running the .py python foobar.py will be ideal, otherwise an .appimage

I think I will have to build it my self (the .appimage ) :)


I like light system
and moreover I like the simplicity of .appimage

Unlike some systems such as Snap and Flatpak, AppImages work with very little support from the base distribution.

To run the app, an user simply needs to run this file — there’s no intermediate installation step.

source: https://www.booleanworld.com/creating-linux-apps-run-anywhere-appimage/


Thanks @fratermus@lemmy.sdf.org
But graph-easy is text to graph.
and I'm looking to draw ! so draw to ~graph(ASCII)
but it's a nice program too.


I'm not, I'm on MX Linux with SysVinit.


Thanks @Strit@lemmy.linuxuserspace.show ,
"Packaging" is not mandatory when creating a software, like it's was written It could run as .py trough python executable. but here it seem not

Otherwise I'm ok with .appimage format/packing.



SOLVED

The following works !

I guess one of my others rules was blocking

table ip Tip {
        chain prerouting {
                type nat hook prerouting priority -100; policy accept;
                ip daddr 192.168.y.2 log prefix "forwarded " dnat to 192.168.y.3
        }
        chain postrouting {
                type nat hook postrouting priority 100; policy accept;
                masquerade
        }
        chain INPUT {
                type filter hook input priority filter; policy accept;
        }
        chain FORWARD {
                type filter hook forward priority filter; policy accept;
        }
        chain OUTPUT {
                type filter hook output priority filter; policy accept;
        }
}

Hi, Thank to all of you.

I made a test environment with the following.
- Machine A: 192.168.Y.1
- Machine B: 192.168.Y.2
- Machine C: 192.168.Y.3

The goal is to send a ping A to B, B forward to C

So ping -4c 1 192.168.y.2 from A, should ping B fw C

I've set the following rule in /etc/nftables.conf

table ip Tip {
        chain prerouting {
                type nat hook prerouting priority dstnat; policy accept;
                iif "eth0" ip protocol icmp dnat to 192.168.y.3
        }
        chain postrouting {
                type nat hook postrouting priority 100; policy accept;
                ip saddr 192.168.y.3 masquerade
        }
}

but is not working :'(

I see B receive the package

preroute: IN=eth0 OUT= MAC=▒▒ SRC=192.168.y.1 DST=192.168.y.2 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=21398 DF PROTO=ICMP TYPE=8 CODE=0 ID=17950 SEQ=1

but it seem C receive nothing..

Any ideas ?


RSS feed

Posts by SpongeB0B, spongeb0b@programming.dev

Comments by SpongeB0B, spongeb0b@programming.dev


Thanks everyone,

I figured out also the missing ./ but meanwhile I got already 4 reply ! \

Thanks so much !


Ideally running the .py python foobar.py will be ideal, otherwise an .appimage

I think I will have to build it my self (the .appimage ) :)


I like light system
and moreover I like the simplicity of .appimage

Unlike some systems such as Snap and Flatpak, AppImages work with very little support from the base distribution.

To run the app, an user simply needs to run this file — there’s no intermediate installation step.

source: https://www.booleanworld.com/creating-linux-apps-run-anywhere-appimage/


Thanks @fratermus@lemmy.sdf.org
But graph-easy is text to graph.
and I'm looking to draw ! so draw to ~graph(ASCII)
but it's a nice program too.


I'm not, I'm on MX Linux with SysVinit.


Thanks @Strit@lemmy.linuxuserspace.show ,
"Packaging" is not mandatory when creating a software, like it's was written It could run as .py trough python executable. but here it seem not

Otherwise I'm ok with .appimage format/packing.



SOLVED

The following works !

I guess one of my others rules was blocking

table ip Tip {
        chain prerouting {
                type nat hook prerouting priority -100; policy accept;
                ip daddr 192.168.y.2 log prefix "forwarded " dnat to 192.168.y.3
        }
        chain postrouting {
                type nat hook postrouting priority 100; policy accept;
                masquerade
        }
        chain INPUT {
                type filter hook input priority filter; policy accept;
        }
        chain FORWARD {
                type filter hook forward priority filter; policy accept;
        }
        chain OUTPUT {
                type filter hook output priority filter; policy accept;
        }
}

Hi, Thank to all of you.

I made a test environment with the following.
- Machine A: 192.168.Y.1
- Machine B: 192.168.Y.2
- Machine C: 192.168.Y.3

The goal is to send a ping A to B, B forward to C

So ping -4c 1 192.168.y.2 from A, should ping B fw C

I've set the following rule in /etc/nftables.conf

table ip Tip {
        chain prerouting {
                type nat hook prerouting priority dstnat; policy accept;
                iif "eth0" ip protocol icmp dnat to 192.168.y.3
        }
        chain postrouting {
                type nat hook postrouting priority 100; policy accept;
                ip saddr 192.168.y.3 masquerade
        }
}

but is not working :'(

I see B receive the package

preroute: IN=eth0 OUT= MAC=▒▒ SRC=192.168.y.1 DST=192.168.y.2 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=21398 DF PROTO=ICMP TYPE=8 CODE=0 ID=17950 SEQ=1

but it seem C receive nothing..

Any ideas ?