Subject: Well...
Author:
Posted on: 2015-08-04 22:44:00 UTC
CIDR notation is a syntax for specifying IP addresses and their associated routing prefix. It appends a slash character to the address and the decimal number of leading bits of the routing prefix, e.g., 192.168.2.0/24 for IPv4, and 2001:db8::/32 for IPv6.
Basically, you should so a WHOIS on the IPv6 address and try blocking what it recommends to see if it helps.
For some reason, certain web browsers have been eating posts whenever I try and make posts to the Board. Both Safari and Google Chrome just behave like I never posted anything, but I discovered Firefox works for my purposes.
Darkotas is having the same problem, except he can't find a single browser that doesn't cause his posts to go kaput.
Thoughts?
It's essentially the beta/dev version. Oddly, I've had less problems using it than normal Chrome. It may also be the ads. A ton of people have been getting severe issues with them, and I've seen ads do even stranger things to certain computers. I'm using adblock, so if I were you, I'd give it a shot and see if it's any better afterwards.
Also, I don't know if you noticed, but you put the author and subject lines in the wrong place. They should be reversed, otherwise the rest of us get confused. :)
Are these browsers running on the same computer? I don't know what it looks like if your IP is accidentally blocked, and I see you have the same prefix (99) as the blocked zdimensia; it could potentially be that (though her whole IP address was actually entered to block).
Also, does it still take you straight to the post when you post it, then just not make it show up? If so, can you grab the link and link to a vanished post? (This is what happens to me all the time over at the Help forum; new threads just vanish, new posts simply never appear on the thread.)
~
And, sorry for hijacking, but Sean has updated the YourWebApps software to allow blocking IPv6 addresses. Only he can't test it properly because he doesn't have one. ^_^ So, someone on IPv6 (Tomash is the only one I know about - other than Ammo Guy), can I block you on the Other Board so we can check if it works? :D
hS
Are you blocking individual IP address or CIDR ranges?
For zdimensia, we blocked the individual IP, because she was only using one. Ammo Guy originally wandered a bit, so we just blocked the first two sections. His IPv6 is now blocked to three colons; I don't know how precise those things are, so.
hS
That is most likely what is causing your problems. Try blocking CIDR ranges instead of colons. What you blocked could have affected thousands of IPs.
CIDR notation is a syntax for specifying IP addresses and their associated routing prefix. It appends a slash character to the address and the decimal number of leading bits of the routing prefix, e.g., 192.168.2.0/24 for IPv4, and 2001:db8::/32 for IPv6.
Basically, you should so a WHOIS on the IPv6 address and try blocking what it recommends to see if it helps.
So, er.
What extra information does appending /24 to the IPv4 address give? Surely you've just blocked the whole thing anyway? And on the flip side, how is adding :/32 to the first two sections of the v6 any more specific than just giving the blocks?
Please remember I'm not a network expert; I just work here. ^_~
hS
I'm not a network expert either, Wikia Stars just have to perform range blocks occasionally. ;)
IPv6 addresses are each 128 bits long. Because each digit in an IPv6 address can have 16 different values (from 0 to 15), each digit represents the overall value of 4 bits (one nibble), with 32 digits total. As with IPv4, CIDR notation describes ranges in terms of a common prefix of bits. For example 2001:db8::/32 means that the range described has the first 32 bits set to the binary digits 00100000000000010000110110101000.
Aren't the first 32 bits the ones you just quoted? So why are you telling it that 2001:db8: is the first 32? Pre...sumably it already knows that?
(YourWebApps certainly does; it specifically blocks 'IP prefixes.)
hS
Alright, if this post goes through, I'll be shocked.
*crosses fingers*
Using Google Chrome at the moment and it posted, apparently. That was just... strange.
Anyway, to answer your earlier question, yes, I was trying the different browsers from the same computer. And it would take me to the vanished post, but when I would hit 'return to messages' it would vanish.
It may have been my fault. ^_^
I see that your Chrome install is giving an IPv6 address - one which starts with the same four digits as Ammo Guy's address. Until today, to block Ammo Guy, I had to enter just those four digits - IPv6 blocking wasn't really supported. I checked it against Tomash's IP, but didn't know you had a v6 address.
But now Sean has enabled it, and I changed the block to more of Ammo Guy's address - and you can post. So yeah, my fault.
(To test whether Ammo Guy is blocked - can you try posting from Chrome to the Other Board? You should be temporarily blocked, and since we now think we know what that ought to look like...)
hS
Maybe it was just a one-time situation? I've been using Chrome ever since I joined and everything was fine..