Topic: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments - page 85. (Read 775279 times)

The output ports seems to be non-7075, maybe try using sport 7075 instead?

/sbin/iptables -t filter -A OUTPUT -p udp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p udp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A OUTPUT -p tcp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p tcp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A OUTPUT -p udp --sport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p udp --sport 7075 -j ACCEPT
/sbin/iptables -t filter -A OUTPUT -p tcp --sport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p tcp --sport 7075 -j ACCEPT

This is fact when price of any legit project are falling people don't touch it. We will see lot of people shouting moon and showing interest in buying when the price will start to increase again. If project is real and development is going on through thick and thick situations means buying time is at low. Nano works smoothly who has used it knows well.

Well the most clever ones will always get involved prior every hype. The projects works well and everyone will realize that

Yes, it is part of a larger firewall script where I close "everything" then re-open one by one each port I need (I have others software running on this server). Here is the beginning of the script:

Then I open the ports I need according to https://github.com/nanocurrency/raiblocks/wiki/Network-usage


The -t filter comes from the way the script starts and does works well will all other programs, I have been using this script for years. I suspect this is related to the UDP nature of the protocol but I have no idea.

Anyone out there has an iptable working script on Ubuntu ?

I also have in my logs:

This is fact when price of any legit project are falling people don't touch it. We will see lot of people shouting moon and showing interest in buying when the price will start to increase again. If project is real and development is going on through thick and thick situations means buying time is at low. Nano works smoothly who has used it knows well.

Honestly it's the firs time that I've encountered this guy, lol never really thought he'll be so butt hurt about what I said hahahaha I guess I hit a nerve well just like what the popular saying says the truth hurts lmao anyway thank you for teaching me about the ignore list mate, I've been on here for almost a year now but it's the first time that I used this feature. I also just check his post history and you're right he is indeed a joke, looking at his posts it really seems like he just created his account to talk bad about Nano well too bad for him, he can never put a great project down. I don't want to sound too full of myself but I was right he's just another newbie spreading FUD lol.

Been trying to use the NANO Wallet on Windows.

It's the worst Crypto wallet I ever used.

Chaotic.

I was interested into NANO but this clearly isn't good enough for adoption.

Plus, NANO rebranding was a mistake. "NANO" on Google gives millions of other results and XRB Raiblocks still gives way more intel than NANO.
Fail...

It has been a little bit over a week since version 11 of the Nano Node was released. Currently, around 45% of the network has been upgraded and is running the latest version.

We’ve been monitoring its rollout and working diligently with those reporting issues to diagnose, understand, test and patch bugs that were found. Our team would like to thank all users who have reported any issues they have faced to us, this engagement helps immensely to refine the Nano protocol.

Version 11 – patches and learnings

In version 11.2, found at https://github.com/nanocurrency/raiblocks/releases/tag/V11.2, we have fixed an issue where a cached value was being ignored and when recalculated would cause the node to crash.

Also, work generation was moved outside of database transactions, which could cause large database sizes if work generation was very slow or there were a lot of wallet operations.

Universal Blocks were not the cause of any of these nor was their future rollout via canary block affected.

Exchange questions

Exchanges running nodes are a unique situation due to the scale at which they operate. Our team is available 24/7 to answer any technical questions exchanges may have and to offer full support in resolving any issues they are facing. When a problem arises and it is brought to our attention, our team dedicates full resources to solve the issue as quickly as possible.

Two things to keep in mind:

1) Due to the nature of some questions or issues that arise that are internal to the exchanges’ business or sensitive in their nature, we do not feel it is appropriate to comment on the issues they are facing and we feel it is best to let exchanges to provide updates as they see fit.

2) Many coins that are forks of bitcoin or are ERC-20 tokens have a standard API and integration that exchanges are very familiar with. Because Nano is not a derivative project, our node and API are unique and may experience issues that other coins’ nodes do not.

As a final note, our team would like to extend our thanks to the Binance team for their professionalism, time and dedication in resolving the wallet issues we recently faced. Our team was able to diagnose their problem and get a fix in place, resulting in minimal downtime.

Now is another problem with Nano (XRB) deposit on Kucoin. I deposited over 36 hours ago and the coins are still on pending. How long can take until they fix their XRB wallet?

Are you directing packets to a table called filter? Any other rules you have got in place?

Maybe try this instead:

#!/bin/sh

# Empty rules
/sbin/iptables -t filter -F

# Empty personnal rule
/sbin/iptables -t filter -X

# Forbid everything
/sbin/iptables -t filter -P INPUT DROP
/sbin/iptables -t filter -P FORWARD DROP
/sbin/iptables -t filter -P OUTPUT DROP

# Preserve established connexion
/sbin/iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
/sbin/iptables -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT

# Allow loopback
/sbin/iptables -t filter -A INPUT -i lo -j ACCEPT
/sbin/iptables -t filter -A OUTPUT -o lo -j ACCEPT 

#nano In/Out
/sbin/iptables -t filter -A OUTPUT -p udp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p udp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A OUTPUT -p tcp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p tcp --dport 7075 -j ACCEPT

[2018-04-04 12:14:39.686591]: Error broadcasting confirm_ack to [::ffff:138.68.183.123]:1964: Operation not permitted
[2018-04-04 12:14:39.687108]: Error broadcasting confirm_ack to [::ffff:51.255.200.174]:6063: Operation not permitted
[2018-04-04 12:14:39.687115]: Error broadcasting confirm_ack to [::ffff:5.189.128.113]:12000: Operation not permitted
[2018-04-04 12:14:39.687160]: Error broadcasting confirm_ack to [::ffff:186.155.30.146]:52921: Operation not permitted
[2018-04-04 12:14:39.687176]: Error broadcasting confirm_ack to [::ffff:167.99.254.89]:1024: Operation not permitted
[2018-04-04 12:14:39.687257]: Error broadcasting confirm_ack to [::ffff:186.155.30.146]:62212: Operation not permitted

Hi there,

Newby question, please. I have installed a headless node on an Ubuntu 16.04
At node start I have 4 errors strings:
"sendto: Operation not permitted
sendto: Operation not permitted
sendto: Operation not permitted
sendto: Operation not permitted"

I have opened UDP port for peering in the firewall with no result:
#nano In/Out
/sbin/iptables -t filter -A OUTPUT -p udp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p udp --dport 7075 -j ACCEPT

What am I missing? Thank you.

/sbin/iptables -I INPUT -p udp --dport 7075 -j ACCEPT
/sbin/iptables -I OUTPUT -p udp --dport 7075 -j ACCEPT

Been trying to use the NANO Wallet on Windows.

It's the worst Crypto wallet I ever used.

Chaotic.

I was interested into NANO but this clearly isn't good enough for adoption.

Plus, NANO rebranding was a mistake. "NANO" on Google gives millions of other results and XRB Raiblocks still gives way more intel than NANO.
Fail...