N9 ICMP PING failed - Samsung Galaxy Note 9 Questions & Answers

I've a newly bought N9 without installing firewall. I'm trying a few apps to ICMP PING but all failed. Is it denied by default in N9 or Oreo? What is the problem with it?

Related

Chromecast [Fix Guide]

Hello everyone, I'm new on here. I have been an Android user since 2010. I recently purchased a Chromecast to use with my Nexus 5 however I was struggling to get it to work with some apps, including Netflix.
It occurred to me that every time I connect a new device to my home, I am redirected to a page which let's me set up the new device on the network. I realised that Chromecast would lack the ability to navigate through this set up process and the process was preventing the device from working correctly...
Sure enough, I went into my router admin settings and disabled the 'Smart Setup' and my Chromecast immediately allowed me to cast Netflix. So check your router settings! Hope this helps!

OpenVPN on KitKat

So I haven't yet rooted my phone. That's next up on the list. I'm just wondering if (after rooting) if there will be a way to manually add a route when connecting via OpenVPN. The device connects perfectly to the server and the server pushes a route to my device. It's just that when I type 'ip route' in a terminal app on the Note, the pushed routes don't actually get added to the device's routing table. I've read many threads that don't really offer any solution.
I'm just hoping that I can create a Tasker or similar automated task that establishes the connection, manually adds the routes, and then packets start a flowing.
Any thoughts on OpenVPN on KitKat? Surely I'm not the only one stuck in this rut!
Any replies or thoughts are appreciated!
Sent from my Note 4 using the XDA app. Damn this thing's sweet!
EDIT: So I rooted the phone using ChainFire's method. It worked flawlessly. I connected to my VPN (which locally is 192.168.1.1/24). After connecting, I verified that the route didn't exist using a terminal command.
su
ip route
I saw nothing mentioning the 192 network. So, I added 'ip route add 192.168.1.0/24 dev tun0' and BAM I'm in business. (I ran netcfg to determine which interface my VPN was on -- I assumed tun0 but I did check!)
Hopefully this helps somebody as I've been tearing my hair out for a couple days over this thing. I did reboot and although the routes weren't there (they're evidently not persistent) the VPN still functioned as designed. I ran a DNS leak test and all of my requests were successfully being routed over the VPN -- and that was all I wanted! Cheers....

Ifconfig wlan0 up Failed.

Basically I'm running GNURoot, as I'm not a great fan of what kali does to my camera, and considering as GNURoot is a debian and kali is too, I thought I'd give it a wirl for some Pen-Testing on my everyday phone. But.
Code:
If config wlan0 up
SIOCSIFFLAGS: operation not permitted
I also tried it in termiux same sort of error. I currently don't have my wifi dongel attached. So I'm wondering if that's the issue. The one plus 3t's network card might essentially be telling me to go for a run?
But has anyone had this issue?
Anyone solved it?
Or is it as started. Ive googled but no real help.
Cheers
Arch.

Fortnite help

I've installed fortnite for the galaxy app store signed up using my mail. Every single game.. I kicked out whey I try to land.. Changed the acc. Hide it from magisk.. Used VPN.. Still The same
And same happened with me using op6
I got this
THERE WAS ANERROR
You were removed from the match due to internet lag,
yourlP or machine, VPN usage, forcheating, or being on
an untrusted platform. We recommend not utilizing VPN
or proxy services while attempting to play Fortnite.
Got the same isseu. 1st on my Note 9 and a day later on my S9+
On XBL it works fine
It happend since the 74mb update
Something to do with USB Debugging being turned on? I know was getting an error when I had it on. Now with it off it works.
Did a factory reset and still persists,
For my s9+ it worked.
Customer support is dead at Epic games Headquarters

RPi4 bash script ping failure

I have a bash script to check the connectivity of IP/MAC combinations on my network. Have used it on linux Mint laptop successfully and RPi3b, latest Raspbian, successfully. Want to upgrade to RPi4b, latest Raspbian. However, couldn't get ping to work properly.
Knowing successful IP/MACs that are successful on RPi3b, I can ctrl-c out of Rpi4b at appropriate time. Then a cli ping works, the IP/MAC on the RPi4b is actually connected, but .sh isn't successful. Experimenting, an additional ping was added in the .sh with both displaying to console. On connected IP/MAC, the first ping is never successful but the second ping is successful. So I tried a single ping with -c 2 - never successful. Back to two pings on RPi4b only.
After a great deal of research, I can't find a solution. Anyone have ideas on why first ping, even with multiple counts, in .sh never works on RPi4b only but a second ping does.

Categories

Resources