You guys forget that a lot of the connections to the SQL port are from a source port of 53. Since there are plenty of firewalls out there which don't do stateful UDP firewalling, the packet filter things the packet coming from port 53 is just an answer to a DNS request the SQL server sent to the internet.
It'll be interesting playing this with the GPRS/GSM attachment you can get for the iPaq. You'd be sitting in the train waiting for the next stop fragging someone on an instagib server over the other side of the world.
Re:Mirroring google - Malkovitch Malkovitch
on
Interview With Linus
·
· Score: 1
Most low-end routers (1700's, 2500's, 3600's, etc) do packet forwarding in software. It's when you've got something like a Catalyst 5000 with a route supervisor engine card that it can do switching in hardware. If routes change however, the first packet gets routed in software. This establishes a path for all subsequent packets to follow in hardware.
7500s and 7200s can do this sort of stuff as well. There are two types of forwarding the Cisco's can do - CEF (Cisco express forwarding and multilayer switching).
I know I'm probably wrong, but I thought the signal traveled through air an was reflected by the glass anyway? The wasn't as good as it distorted the final light result at the other end or something like that.
FSKing with wireless networks works by jumping between a set of frequencies in a period of time to create some form of privacy out of the link.
What about jumping between between a set of IP's over a period of time... sort of like creating a blur out of the originating address? Would be a horrendus waste of addresses though, but there is always NAT I spose. This could be something to be implemented at the ISP end, with them providing the engine and NAT to go between the destination and their border network address translation device
I agree entirely. We installed the Solaris version at work here and if you haven't had a lot of prior knowledge of Solaris package management and DB2 (IBM's database) along with JDK you'd find it pretty hard going.
Aparently Websphere initially was just a hacked-together version of their intranet server which ran on apache. The documentation is just a quickly hashed-together piece of trash. Doesn't work out of the box.. the documentation is incomplete.. the list goes on.
IBM may have done wonders with OS/2 but that is to be no longer. Rumours coming out of the woodwork are that IBM is going to drop support for its own OS - OS/2 and support NT instead.
I dunno about Nitrogen being inert. Nitrogen Dioxide (the brown pungent gas.. not sure if that's the right compound) is pretty poisonous.
That's the stuff that forms when you're making nitric acid.
While you're tweaking the DB2 engine, can you tweak it so you can drop columns from a table?
I've found it a real hassle copying a table minus a column to a new table, then back again.
ALTER TABLE DROP COLUMN BLA
mmm
After a while the light is eventually going to be turned into heat due to the reflection from the glass cable. I wonder how many loops around the earth it can manage before it peters out.
You guys forget that a lot of the connections to the SQL port are from a source port of 53. Since there are plenty of firewalls out there which don't do stateful UDP firewalling, the packet filter things the packet coming from port 53 is just an answer to a DNS request the SQL server sent to the internet.
It'll be interesting playing this with the GPRS/GSM attachment you can get for the iPaq. You'd be sitting in the train waiting for the next stop fragging someone on an instagib server over the other side of the world.
Being John Malkovitch anyone?
There are ways of getting around the anti-user interaction feature of banjo.
Most low-end routers (1700's, 2500's, 3600's, etc) do packet forwarding in software. It's when you've got something like a Catalyst 5000 with a route supervisor engine card that it can do switching in hardware. If routes change however, the first packet gets routed in software. This establishes a path for all subsequent packets to follow in hardware. 7500s and 7200s can do this sort of stuff as well. There are two types of forwarding the Cisco's can do - CEF (Cisco express forwarding and multilayer switching).
Here's a good cisco doco that I should have included in the origional post: here
Aparently with Cisco's next major IOS train release, there will be support for IPV6 which I'm certainly looking forward to.
I know I'm probably wrong, but I thought the signal traveled through air an was reflected by the glass anyway? The wasn't as good as it distorted the final light result at the other end or something like that.
What makes this even funnier is Bill's a college dropout. Nothing wrong with that though.
I'd like you to show the audience exactly what TCPv4 is. My bet is you'd find it a bit of a struggle. IPv4 yes, but TCP, probably not.
FSKing with wireless networks works by jumping between a set of frequencies in a period of time to create some form of privacy out of the link. What about jumping between between a set of IP's over a period of time... sort of like creating a blur out of the originating address? Would be a horrendus waste of addresses though, but there is always NAT I spose. This could be something to be implemented at the ISP end, with them providing the engine and NAT to go between the destination and their border network address translation device
- a major international subterrainian cable linking Hawaii, New Zealand, Australia.
I spose that's one way to spread your seed.
I agree entirely. We installed the Solaris version at work here and if you haven't had a lot of prior knowledge of Solaris package management and DB2 (IBM's database) along with JDK you'd find it pretty hard going. Aparently Websphere initially was just a hacked-together version of their intranet server which ran on apache. The documentation is just a quickly hashed-together piece of trash. Doesn't work out of the box.. the documentation is incomplete.. the list goes on.
IBM may have done wonders with OS/2 but that is to be no longer. Rumours coming out of the woodwork are that IBM is going to drop support for its own OS - OS/2 and support NT instead.
I dunno about Nitrogen being inert. Nitrogen Dioxide (the brown pungent gas.. not sure if that's the right compound) is pretty poisonous. That's the stuff that forms when you're making nitric acid.
While you're tweaking the DB2 engine, can you tweak it so you can drop columns from a table? I've found it a real hassle copying a table minus a column to a new table, then back again. ALTER TABLE DROP COLUMN BLA mmm
After a while the light is eventually going to be turned into heat due to the reflection from the glass cable. I wonder how many loops around the earth it can manage before it peters out.
Pesonally I think packets are best transferred by homing peidgeons. Only really applies to pings though. Huge packet loss when it's hunting season.
**sigh** wonder why he didn't put a ;) to make it more OBVIOUS than a slap in the face with a wet trout :P