There is an intersection between the tasks iptables/ebtables/arptables can perform, so someties you need to decide which responsibility you want to delegate to which.
But you are correct, ebtables was never a replacement.for iptables.
This diagram is very useful when you get deep in the weeds.
It's not new at all, but doesn't have to be. It's a paradigm that has been challenging the CS community to build a good UI or language around for decades. So far the results have been mediocre.
It's good to see a more serious effort, however, using side-effect-free FBP isn't exaclty a good first step towards making a natural feeling UI, given that functional programming is essentially the polish arithmetic of the programming field, and is absolutely awful at modeling real-time.
Anywhere you're likely to want an Ethernet port you have wall sockets, so no point in powered varieties.
I think here you may be underestimating the level to which the home consumer will finick over convenience. Having one universal power adaptor (an RJ-45 cable) lying around that any gadget can charge off with the added benefit of more reliable low-latency performance beats buying a bunch of wall warts for each device or carrying said wall wart around with you. I could see inductive pads competing, but not wall outlets.
Yup. My thoughts exactly when I bought the PS3 at the right time in the cycle. That and I wanted a system where I never had to sit down ready for a relaxing game and then end up spending the next hour mucking around with driver updates. It didn't quite deliver on that: the updates were moron-level easy with nothing to do but piss and get piss-to-be out of the fridge while they ran, but tended to be mandatory on-the-spot, whereas PC was "fiddle around with a lot of stuff, but you can put it off for a week or two."
It would be nice if fiber optic made it to the home, other than S/PDIF connections, and preferably with a more idiot-resistant connector than what existing fiber uses, especially with fouling lightpipes due to dust and such. Copper is useful, but eventually for faster connections, we will have to jump ship completely to fiber.
I doubt fiber will ever make it in the home market aside from storage attachment. The only way to persuade a typical commodity user to plug anything in these days is if they can charge their battery of it. Will likely see penetration of PoE,PoE+,etc and 10GBase-T, but not much beyond that.
Generic Eastern European Coldwar Badguy: Sure you are das Americans do not know? Generic Eastern European Coldwar Badgeek: Nyet. Ze messages ver hidden across million email to sell Viagra.
Ah, I see. Thought full USB soundcard profile devices did not work on the PS3. Another instance where the majority of people answering questions on the Internet are completely wrong. SIgh.
I understood that. Ignore my first sentence it was pasto. That's the product I was looking for, and as the above post says I could not find said product, and the alternative is to go Wireless USB to a wired USB headset. There I could find a couple products, but none with a battery powered device-side, so then I'd have about 2 pounds of stuff taped together on my lap: The excess wire from the USB earphones, the wireless-usb device-side gadget, its wall-wart, and a mini 120V/Li-FePO4 covertor pack.
I think I'll wait for either Wireless-USB-pairable headset or a Wireless USB transciever set that has integrated battery for low-current USB clients.
I don't anymore; this was pretty much the only time I got spanked by Sony and otherwise I've been happy with the PS3 (fat) overall, for what I use it for. Won't be getting a PS4. There's just no point. By the time I've tapped the entertainment value of the PS3, it'll be that sweet mid-gerenation spot where PCs are kicking console ass, and I'll jump to PC then. Though some days I am tempted to jump early, especially given the abysmal lack of controller button remapping and dead zone reduction options in many console games.
Yeah I doubt Sony is going to support add-on BT busses via USB. Having just been looking for such an animal as you describe, I came up empty. Decided to go wired for now and wait for a better selection of Wireless USB kit to hit the market. The additional benefit of to that is that Certified Wireless USB uses different frequency ranges than BT, so it won't be clogging up that band, which is pretty messy as is. Also when I'm done with the headset use the wireless USB component will probably end up useful for some other task.
FTFY. There are multiple audio protocols in BT, e.g. mono versus A2DP and on top of A2DP a bunch of optional codecs. Also there is Certified Wireless USB, if you can find it.
They allow core developers to claim credit for their work. Note that this is for a bug report with patch, and the patch is expected to be more a systemic fix that is of high enough quality to be part of the codebase going forward than a workaround. If the hackathon produces such code and shepards it through the upstream pull request process, then the organization might try to see if Google would cut them a check instead of an individual developer. However, that pull process often takes a few days.
At 80MHz in the US there will be 5 non-overlapping channels. This may sound only 66% better than 3, but the topology of the packing problem makes it many, many times better than 3.
I doubt 160MHz will be in use by people that have to actually manage frequencies, except near the offices of the PHB. I could only see that becoming a problem in dense apartment buildings with many individually "administered" OTS systems -- in residential neighborhoods the 5G will be pretty much stopped by walls, at least to the point of not being strong enough to cause much interference.
I would not call those results atypical. Signal strength will drop, though in many cases 5GHz will be cleaner in the first place so it makes up for it in quality.
But the client behavior when presented with multiple APs on both 2.5GHz and 5GHz, and when presented with multiple APs some of which are N-capable and some just a/b/g is generally abysmal. We have lots of clients that students bring from their simple single-AP 2.5GHz home networks and just cannot cut it in a WPA-enterprise environment with lots of infrastrcuture APs around. They jump around between APs constantly, often choose APs based on mysterious metrics which are probably the worst choice of available APs, and very often the worst of them manage to trigger themselves to re-ask for credentials despite being told to remember them -- I don't know how that got into their codebase, but we've got several users that get constant cred popups. To top it off the UI on the devices has been dumbed down to the point where there is no user-level control to the degree of selecting preferred BSSIDs or tweaking any parameters whatsoever. Most cannot even tell the user what BSSID they are currently connected to.
I'm glad 11ac is going to force device manufacturers to start putting 5G antennas in again, but anyone running an enterprise WAN would be well advised to increase their AP density to 5G full coverage, drastically reduce the tx power on their 2.5GHz radios so they look quieter than the 5G radios, and not rely on the devices falling back to b/g/n-2.5 reliably. WiFi driver software is apparently written by conpanies that have invested zero into recreating real-world "BYOD" scenarios for QA purposes.
you don't actually have to write much low level code anymore in most situations, but you should know that it's there, how it works, and how efficient or inefficient it is.
To wit, none of the lists seem to include: 2's compliment math, signed versus unsigned integer data types, endianness conversions, and alignment/locality.
To the modern dynamic language coder these things sound like gory details to be avoided at all costs, and that's a huge problem: you cannot avoid the unavoidable. Endian issues especially are embedded in the core of everything, not just machine code, but also network protocols. This is why you end up with code in a dynamic language using big-integer operands and virtually-dispatched shift and mask operators to slowly shuffle bits about to deal with endianness. In pursuit of GC efficiency and lockless contention protection, the backend VMs seem to go to great lengths to avoid ever allowing the user to see a pointer or any information about memory layout, so no user of these facilities can ever write any code that actually suggests efficient memory layout based on knowlege of the algorithm, and any facilities offered to produce a final data structure e.g. a network packet that must have a definite layout necessarily involves an extra serialization step even if it would be possible to generate code to build the structure in place. And don't get me started that a good number of dynamic language backend VMs do not even have unsigned integer types at the register level.
Being a highly regulated industry, I could see the eventual evolution of a competent security culture in medical IT/manufacturing. We certainly don't have it quite together now, but if and when that comes to pass, do you see the lessons learned in that sector promulgating out to other industries, or will the environment of high regulation (and high stakes) produce too alien a solution set for general application?
Problem with that is you cannot trust users to secure their keys any more than you can trust them to choose good passwords. Once you give them a keyfile they can change the password to whatever they want, or leave it naked.
Really if you want to excercise hard security, it should be both password and key. No, not password protected key, password stored on the remote host and require a key. What's truly retarded is the failure of most people including crypto software developers to see the use case for this, and endless arguments between the relative merits of one or the other.
just try to ping a known website (like apple.com).
Actually you have to do an HTTP GET because ICMP might be blocked while web is permitted. And this is a cheezy way to do things, since it makes the thing look broken if local policy doesn't allow access to apple.com or whatever site you use, or if that particular site crashes (which happened with hilarious consequences a couple years ago IIRC.) Anyway throwing up an OS wrapper around portal login pages was fairly evil. The're designed to work from a browser, just let them work.
It's called 802.11u. Though really how evil it is is entirely up to the people who write the UI for it. dot11u in and of itself is a plausibly useful and beneficial technology.
This, and you can easily distinguish a reflected attack by the type of packet, which will be an unsolicited reply to an application level request.
I just wish the stupid script kiddies would realize that not every SNMPv2/SNMPv3 client that responds actually amplifies traffic or gives maybe a 30% gain (because what you're getting back is an "access denied") and so isn't worth it, and stop trying to reflect off the printers here. I'm sick of chasing around the people who are supposed to lock them down, and banning entire protocols that don't really, really deserve it just fills me with ick.
anything that they MAY have touched is likely infested.
That would pretty much mean everything is infested. I mean, unless you think running into the arms of whatever crypto suite lying around out there that has never had bad press about intelligence agency meddling is a good way to avoid intelligence agency meddling -- I don't.
Slashdot Mirror
There is an intersection between the tasks iptables/ebtables/arptables can perform, so someties you need to decide which responsibility you want to delegate to which.
But you are correct, ebtables was never a replacement.for iptables.
This diagram is very useful when you get deep in the weeds.
It's not new at all, but doesn't have to be. It's a paradigm that has been challenging the CS community to build a good UI or language around for decades. So far the results have been mediocre.
It's good to see a more serious effort, however, using side-effect-free FBP isn't exaclty a good first step towards making a natural feeling UI, given that functional programming is essentially the polish arithmetic of the programming field, and is absolutely awful at modeling real-time.
The Internet is configured to strip sarcastic inflection at the edge. If you want to use it, you have to tunnel it.
The government doesn't produce anything
I'm sure S&P will be persuaded of that as soon as you drive on over there without using any government-produced product and tell them to their faces.
Umm, negative 24 billion dollars? That is after all, what they are attempting to assess with this figure.
Anywhere you're likely to want an Ethernet port you have wall sockets, so no point in powered varieties.
I think here you may be underestimating the level to which the home consumer will finick over convenience. Having one universal power adaptor (an RJ-45 cable) lying around that any gadget can charge off with the added benefit of more reliable low-latency performance beats buying a bunch of wall warts for each device or carrying said wall wart around with you. I could see inductive pads competing, but not wall outlets.
Yup. My thoughts exactly when I bought the PS3 at the right time in the cycle. That and I wanted a system where I never had to sit down ready for a relaxing game and then end up spending the next hour mucking around with driver updates. It didn't quite deliver on that: the updates were moron-level easy with nothing to do but piss and get piss-to-be out of the fridge while they ran, but tended to be mandatory on-the-spot, whereas PC was "fiddle around with a lot of stuff, but you can put it off for a week or two."
It would be nice if fiber optic made it to the home, other than S/PDIF connections, and preferably with a more idiot-resistant connector than what existing fiber uses, especially with fouling lightpipes due to dust and such. Copper is useful, but eventually for faster connections, we will have to jump ship completely to fiber.
I doubt fiber will ever make it in the home market aside from storage attachment. The only way to persuade a typical commodity user to plug anything in these days is if they can charge their battery of it. Will likely see penetration of PoE,PoE+,etc and 10GBase-T, but not much beyond that.
I can see the movie dialogue now:
Generic Eastern European Coldwar Badguy: Sure you are das Americans do not know?
Generic Eastern European Coldwar Badgeek: Nyet. Ze messages ver hidden across million email to sell Viagra.
Ah, I see. Thought full USB soundcard profile devices did not work on the PS3. Another instance where the majority of people answering questions on the Internet are completely wrong. SIgh.
I understood that. Ignore my first sentence it was pasto. That's the product I was looking for, and as the above post says I could not find said product, and the alternative is to go Wireless USB to a wired USB headset. There I could find a couple products, but none with a battery powered device-side, so then I'd have about 2 pounds of stuff taped together on my lap: The excess wire from the USB earphones, the wireless-usb device-side gadget, its wall-wart, and a mini 120V/Li-FePO4 covertor pack.
I think I'll wait for either Wireless-USB-pairable headset or a Wireless USB transciever set that has integrated battery for low-current USB clients.
I don't anymore; this was pretty much the only time I got spanked by Sony and otherwise I've been happy with the PS3 (fat) overall, for what I use it for. Won't be getting a PS4. There's just no point. By the time I've tapped the entertainment value of the PS3, it'll be that sweet mid-gerenation spot where PCs are kicking console ass, and I'll jump to PC then. Though some days I am tempted to jump early, especially given the abysmal lack of controller button remapping and dead zone reduction options in many console games.
Yeah I doubt Sony is going to support add-on BT busses via USB. Having just been looking for such an animal as you describe, I came up empty. Decided to go wired for now and wait for a better selection of Wireless USB kit to hit the market. The additional benefit of to that is that Certified Wireless USB uses different frequency ranges than BT, so it won't be clogging up that band, which is pretty messy as is. Also when I'm done with the headset use the wireless USB component will probably end up useful for some other task.
bluetooth is the standards for wireless headsets
FTFY. There are multiple audio protocols in BT, e.g. mono versus A2DP and on top of A2DP a bunch of optional codecs. Also there is Certified Wireless USB, if you can find it.
The Playstation Store works. It is what they seem to put 99% of their development effort into.
(Disclaimer: The above opinion is from an angry owner of a very nice Sony-Ericsson bt headset that the PS3 won't use.)
They allow core developers to claim credit for their work. Note that this is for a bug report with patch, and the patch is expected to be more a systemic fix that is of high enough quality to be part of the codebase going forward than a workaround. If the hackathon produces such code and shepards it through the upstream pull request process, then the organization might try to see if Google would cut them a check instead of an individual developer. However, that pull process often takes a few days.
At 80MHz in the US there will be 5 non-overlapping channels. This may sound only 66% better than 3, but the topology of the packing problem makes it many, many times better than 3.
I doubt 160MHz will be in use by people that have to actually manage frequencies, except near the offices of the PHB. I could only see that becoming a problem in dense apartment buildings with many individually "administered" OTS systems -- in residential neighborhoods the 5G will be pretty much stopped by walls, at least to the point of not being strong enough to cause much interference.
I would not call those results atypical. Signal strength will drop, though in many cases 5GHz will be cleaner in the first place so it makes up for it in quality.
But the client behavior when presented with multiple APs on both 2.5GHz and 5GHz, and when presented with multiple APs some of which are N-capable and some just a/b/g is generally abysmal. We have lots of clients that students bring from their simple single-AP 2.5GHz home networks and just cannot cut it in a WPA-enterprise environment with lots of infrastrcuture APs around. They jump around between APs constantly, often choose APs based on mysterious metrics which are probably the worst choice of available APs, and very often the worst of them manage to trigger themselves to re-ask for credentials despite being told to remember them -- I don't know how that got into their codebase, but we've got several users that get constant cred popups. To top it off the UI on the devices has been dumbed down to the point where there is no user-level control to the degree of selecting preferred BSSIDs or tweaking any parameters whatsoever. Most cannot even tell the user what BSSID they are currently connected to.
I'm glad 11ac is going to force device manufacturers to start putting 5G antennas in again, but anyone running an enterprise WAN would be well advised to increase their AP density to 5G full coverage, drastically reduce the tx power on their 2.5GHz radios so they look quieter than the 5G radios, and not rely on the devices falling back to b/g/n-2.5 reliably. WiFi driver software is apparently written by conpanies that have invested zero into recreating real-world "BYOD" scenarios for QA purposes.
you don't actually have to write much low level code anymore in most situations, but you should know that it's there, how it works, and how efficient or inefficient it is.
To wit, none of the lists seem to include: 2's compliment math, signed versus unsigned integer data types, endianness conversions, and alignment/locality.
To the modern dynamic language coder these things sound like gory details to be avoided at all costs, and that's a huge problem: you cannot avoid the unavoidable. Endian issues especially are embedded in the core of everything, not just machine code, but also network protocols. This is why you end up with code in a dynamic language using big-integer operands and virtually-dispatched shift and mask operators to slowly shuffle bits about to deal with endianness. In pursuit of GC efficiency and lockless contention protection, the backend VMs seem to go to great lengths to avoid ever allowing the user to see a pointer or any information about memory layout, so no user of these facilities can ever write any code that actually suggests efficient memory layout based on knowlege of the algorithm, and any facilities offered to produce a final data structure e.g. a network packet that must have a definite layout necessarily involves an extra serialization step even if it would be possible to generate code to build the structure in place. And don't get me started that a good number of dynamic language backend VMs do not even have unsigned integer types at the register level.
Being a highly regulated industry, I could see the eventual evolution of a competent security culture in medical IT/manufacturing. We certainly don't have it quite together now, but if and when that comes to pass, do you see the lessons learned in that sector promulgating out to other industries, or will the environment of high regulation (and high stakes) produce too alien a solution set for general application?
Problem with that is you cannot trust users to secure their keys any more than you can trust them to choose good passwords. Once you give them a keyfile they can change the password to whatever they want, or leave it naked.
Really if you want to excercise hard security, it should be both password and key. No, not password protected key, password stored on the remote host and require a key. What's truly retarded is the failure of most people including crypto software developers to see the use case for this, and endless arguments between the relative merits of one or the other.
just try to ping a known website (like apple.com).
Actually you have to do an HTTP GET because ICMP might be blocked while web is permitted. And this is a cheezy way to do things, since it makes the thing look broken if local policy doesn't allow access to apple.com or whatever site you use, or if that particular site crashes (which happened with hilarious consequences a couple years ago IIRC.) Anyway throwing up an OS wrapper around portal login pages was fairly evil. The're designed to work from a browser, just let them work.
Though I'm sure that's next.
It's called 802.11u. Though really how evil it is is entirely up to the people who write the UI for it. dot11u in and of itself is a plausibly useful and beneficial technology.
This, and you can easily distinguish a reflected attack by the type of packet, which will be an unsolicited reply to an application level request.
I just wish the stupid script kiddies would realize that not every SNMPv2/SNMPv3 client that responds actually amplifies traffic or gives maybe a 30% gain (because what you're getting back is an "access denied") and so isn't worth it, and stop trying to reflect off the printers here. I'm sick of chasing around the people who are supposed to lock them down, and banning entire protocols that don't really, really deserve it just fills me with ick.
anything that they MAY have touched is likely infested.
That would pretty much mean everything is infested. I mean, unless you think running into the arms of whatever crypto suite lying around out there that has never had bad press about intelligence agency meddling is a good way to avoid intelligence agency meddling -- I don't.