Damn, I had to choose between modding you up or posting a rather unique experience I had. I'm afraid you won't get mod points from me;-P
About 5 years ago I had a small black spot, just in the middle my visual field (of the left eye). Actually the doctors could not diagnose it with 100% acurracy, but they suggested it due to a lack of some vitamines. Back then I was a CS undergrad student, so this explaination is quite reasonable;)
The spot lasted for about 2 months, then luckily it vanished. It was really distracting, as it moved with every movement of my (left) eye. It was something like having a aiming dot (target scope) mounted on top of my eye.
However it was really annoying, since your eye make little moves, even if - or especially when - you focus on something. So I had this little point jumping around in my vision, driving me mad. I always thought that when I was talking to someone, they would notice that my eyes would move in an erratic way. Maybe that was the case, but I now think that perhaps I was a little bit paranoid.
Anyway, this changed the way how I think of people with 'weird eyes' (movement)...
Most Mainboards have only 33MHz/32bit PCI slots.
However "Conventional PCI" actually goes up to 66MHz/64bit = (533 MB/s), although you'll only find that in older workstation/server mainboards (newer ones often use PCI-X instead).
Then there is PCI-X. The latest PCI-X standard specifies PCI-X 533 (64bit), giving you a theoretical I/O limit of 4.3 GB/s.
And of course there is this new PCI-Express, with a transfer rate of 250 MB/s for a single lane (and you can bundle 32 of them = 8 GB/s). However most new mainboards that offer PCI-Express come with only one 16X-PCI-Express slot (as replacement for AGP) and a couple of 1X-PCI-Express slots (still faster than 'normal' PCI).
Usually the IPv6 addresses are derived from your (48bit)-MAC address to automatically create a (64bit)-EUI-64 IPv6 address.
Of course this means that you still have (128bit - 48prefix - 64bit-EUI =) 16bit you can use for subnetting.
An example:
You have been assigned the following/46 subnet prefix: "2001:1234:5678::/48".
Then you will be able to use the following/64 subnets: from "2001:1234:5678:0001::/64" to "2001:1234:5678:FFFF::/64". Note that one/64 subnet is usually more than enough for most people.
If you then use radvd to broadcast the prefix "2001:1234:5678:0001::/64" on a network interface, all the PCs which receive the broadcasts will automatically setup their IPv6 addresses accordingly and can connect to the (IPv6) internet.
Re:I do wish
on
IPv6 is Here
·
· Score: 2, Informative
I was indeed referring to an IPv6 router with no NAT involved, which is what I meant by "live" IP addresses. Sorry about the confusion.
Well, there are global scope IPv6 addresses (like official 'live' IPv6 addresses), site local (internal lan addresses, like 192.168.x.x for IPv4, but its use is deprecated) and link-local (used for IPv6 autoconfiguration). If you want to have a working IPv6 connection to the rest of the world, you will need (a) global scope IPv6 address(es). Thats what the IPv6 providers (native ISPs, tunnel broker) will assign to you.
Most IPv6 tunnel brokers (freenet6, sixxs,...) will give you one (single) IPv6 address for your end of the IPv6 tunnel, and if you requested e.g. a/48 subnet, they'll additionally give you the 48bit-prefix you have to use within your subnet. So you can use a whole (128 - 48 =) 80bit address range for your subnet, just the first 48bits are fixed.
Usually the IPv6 addresses are derived from your (48bit)-MAC address to automatically create a (64bit)-EUI-64 IPv6 address. For this to work you have set up a router advertizing service (e.g. radvd under Linux), which will broadcast - within your lan - the prefix to use, and the PCs in your lan will use this info and automatically create proper IPv6 addresses by themselves. However if the IPv6 'privacy extensions/temporary addresses' are enabled on a PC (by default enabled on Windows, disabled on Linux), it won't create a EUI-64 IPv6 address (from which you can easily figure out their MAC), but it will use a randomized IPv6 address instead.
You can also avoid using 'radvd' entirely and just setup your PCs to use statically assigned IPv6 addresses (e.g. in the PC's boot scripts), and thus you can make full use of the 80 bit address range.
N.B. there is also a DHCPv6, so you can assign to each MAC address a unique IPv6 address YOU specify, but the DHCPv6 protocol is work-in-progress and I haven't seen a working implementation yet.
I suppose your current network setup is something like this:
Internet ------ NAT box ------ Hub ====== PCs
In this setup you can either use the NAT box itself as a IPv6 tunnel endpoint/router, which will provide your subnet with IPv6 connectivity.
Another way would be to port-forward the IPv6 tunnel traffic to any of the PCs behind the NAT box, and do the IPv6 routing from there.
Anyway, when the PCs in your lan want to connect to a host on the internet via IPv6, they will connect to the IPv6 router, and the router will forward the packets though the IPv6 tunnel to your IPv6 tunnel broker. Since the tunnel broker need to know that you are entitled to use their service and where they should forward the IPv6 tunnel traffic, you might also have to 'login' or use a special software to initiate/enable the IPv6 tunnel. How this works exaclty depends on your IPv6 tunnel provider.
Have any people successfully set up something like this, maybe using services like freenet6?
Yes, quite some have, including me. I was using freenet6 (with a/48 subnet) before I discovered www.sixxs.net (which I can really recommend to european users). Sixxs.net just announced it's 1000th subnet (and has a little more than 2000 users). There are many more IPv6 tunnel ISPs, just google for "IPv6 tunnel broker". Choose the ones which are closest to your location (low pings) and offer the good service/support (no filtering, good forums).
I would also love a block of live IPv6 addresses for my home. I currently have an old P200 doing NAT for the network, and it's bloody great. I run Smoothwall linux on it, which is designed to be run on machines acting as a firewall/router.
I do not fully understand your question. There is no NAT for IPv6 (at least Linux doesn't support it, there is no need for it, and AFAIK it doesn't even exist). If you referring to a IPv6 router/tunnel gateway, then yes, Linux can do that easily.
Do any similar distros do this for IPv6?
I haven't come across a all-in-one IPv6 capable firewall Linux distribution. However it is not to difficult to enhance an existing with IPv6 support (usually you just need ip6tables, radvd and a IPv6-enabled kernel).
Is it easy to migrate an IPv4 NAT network like mine to IPv6 (assuming all the clients are IPv6-capable)?
Yes, it is rather easy. The only thing you'll need in most setups is running 'radvd' on the IPv6 router.
Oh, and what do people mean by "/48"?
Let's assume you have the IPv4 class-A network 45.x.x.x. Its netmask is therefore 255.255.255.0. This is often abbreviated with the suffix/8 (like in 45.0.0.0/24). The/8 means that the first 8 bit of the IP address specify the network (and are fixed), and the rest (32bit - 8bit = 24bit) specify the host (and can be used by you). In our example this means you can have/choose IP addresses from between 45.0.0.0 - 45.255.255.255.
If you have a IPv6 network with a/48 prefix, it is quite similar; however a IPv6 address has 128bit. instead of 32bit (for IPv4). For example, let's assume you have the following IPv6 network 2001:1:1::/48. This means the first 48 bit are fixed (2001:1:1:) and you can use (128bit - 48bit =) 80bit to address any host in your subnet. Just a remark: the numbers between two colons ':' of an IPv6 address are 16bit wide. So the range would be from 2001:0001:0001:0000:0000:0000:0000:0000 to 2001:0001:0001:FFFF:FFFF:FFFF:FFFF:FFFF.
That's a big number:
1,208,925,819,614,629,174,706,176 addresses just for you!
The problem is not the brightness contrast (which you can change by reducing the transparency level), but the colour contrast.
Choosing the right colours is more important than choosing the right brightness difference. Most PC user are not aware of this fact.
Equiluminant colors is only once think that comes to mind when I think what can go wrong...
Although I think transparency/translucency is a nice feature to have, a X terminal window is definitely is NOT an application where you want to use it. Do you really want to damage your eyesight?
Not neccessary at this early step, ie. not needed for compiling the kernel. Do a 'su' when you are about to install the compiled kernel&modules.
2) cd/usr/src
5) ln -s./linux-2.6.7./linux
Not needed. 5) is actually discouraged by Linus. Just unpack the linux kernel sources somewhere and cd into that directory.
9) make bzImage
10) make modules
both commands are only needed for 2.4.x kernels and if you compile a kernel for the ix86 platform. If you are using 2.6.x, you should simply do a 'make'.
11) cd arch/i386/boot
12) cp bzImage/boot/
13) edit/etc/grub.conf
are also only needed if you compile for the Linux/ix86 platform. 13) only applies if you are using GRUB as a bootloader on a RedHat system. BTW, GRUB's config file is usually in/boot/grub/menu.lst.
You are also missing a 'make modules_install' and it might be a good idea to save your System.map and.config aswell.
Instead of 11-12) you might want to do a simple 'make install' (for 2.6.x kernels). Also try out 'make help'.
Grandparent post makes much more sense if you replace "unstable" with "testing" (and vice versa).
Unstable is unstable, because it is - packages are not guaranteed to *work* on all platforms - using unstable might have broken dependencies, ie. apt-get is not guaranteed to work properly - the pool is quite 'unstable', ie. you'll get alot of updates every day
Having said that, 'unstable' is indeed rather stable most of the time (at least on ix86), at least comparable to what RedHat or SuSE call a 'new release'.
Testing however contains only packages from unstable that didn't have any bug reports for the last 10 days (IIRC, and meet dependency requirements, and more).
So 'unstable' is if you really want to use the absolutely latest software (just a few days old), and testing if you want very recent software, but at least with no (big, bad) surprises.
I know its compilable on other platforms, its just not used by any signifigant numbers of developers on other platforms.
GNUstep is there and is ported on many platforms: all kinds of Unix variants (Linux, *BSD, Solaris etc.), Windows and even Mac OS X.
It is very stable (actually for quite a long time now), OpenStep Foundation is implemented 100%, but just AppKit (graphical stuff) is missing some things. And of course the stuff that was added in Cocoa and was not part in the OpenStep specification is also added in GNUstep when possible.
BTW, we always look for developers (both for GNUstep and for apps that run on GNUstep)!
Their drivers seem to me very stable, and they support 2.6 aswell (N.B. just building one driver with e.g. "make pccard" didn't work for me for 2.6, but building ALL drivers with a simple "make" worked.)
I'm not talking about using the card in HostAP mode (ie. using your wireless network card as a access point). You can do that of course, but I just wanted to recommend these drivers because I've tried all other drivers for prism2/2.5 cards, and none worked for the various non-ix86 architectures I'm using. The HostAP drivers however work on all of them!
Sorry for being to rude in my previous post, you actually have a point here.
He said ditto and implied that RFC 2396 was superceded by RFC 2616, but this is not the case.
However the description of HTTP URLs in RFC 2616 is another hint for you that you might be wrong...
Again you missed the point! It is not clear to me whether you are a troll or just stubborn.
His link points to a RFC that makes references to your beloved RFC 2396, but STILL MENTIONS that "user:password" is not allowed for HTTP URLs. Why would it do that if it was allowed in RFC 2396 (according to you)?
Slashdot Mirror
Damn, I had to choose between modding you up or posting a rather unique experience I had. I'm afraid you won't get mod points from me ;-P
;)
...
About 5 years ago I had a small black spot, just in the middle my visual field (of the left eye). Actually the doctors could not diagnose it with 100% acurracy, but they suggested it due to a lack of some vitamines. Back then I was a CS undergrad student, so this explaination is quite reasonable
The spot lasted for about 2 months, then luckily it vanished. It was really distracting, as it moved with every movement of my (left) eye. It was something like having a aiming dot (target scope) mounted on top of my eye.
However it was really annoying, since your eye make little moves, even if - or especially when - you focus on something. So I had this little point jumping around in my vision, driving me mad. I always thought that when I was talking to someone, they would notice that my eyes would move in an erratic way. Maybe that was the case, but I now think that perhaps I was a little bit paranoid.
Anyway, this changed the way how I think of people with 'weird eyes' (movement)
Here you go: .
Almost correct.
Most Mainboards have only 33MHz/32bit PCI slots.
However "Conventional PCI" actually goes up to 66MHz/64bit = (533 MB/s), although you'll only find that in older workstation/server mainboards (newer ones often use PCI-X instead).
Then there is PCI-X. The latest PCI-X standard specifies PCI-X 533 (64bit), giving you a theoretical I/O limit of 4.3 GB/s.
And of course there is this new PCI-Express, with a transfer rate of 250 MB/s for a single lane (and you can bundle 32 of them = 8 GB/s). However most new mainboards that offer PCI-Express come with only one 16X-PCI-Express slot (as replacement for AGP) and a couple of 1X-PCI-Express slots (still faster than 'normal' PCI).
One more thing:
/46 subnet prefix: "2001:1234:5678::/48".
/64 subnets: from "2001:1234:5678:0001::/64" to "2001:1234:5678:FFFF::/64". /64 subnet is usually more than enough for most people.
Usually the IPv6 addresses are derived from your (48bit)-MAC address to automatically create a (64bit)-EUI-64 IPv6 address.
Of course this means that you still have (128bit - 48prefix - 64bit-EUI =) 16bit you can use for subnetting.
An example:
You have been assigned the following
Then you will be able to use the following
Note that one
If you then use radvd to broadcast the prefix "2001:1234:5678:0001::/64" on a network interface, all the PCs which receive the broadcasts will automatically setup their IPv6 addresses accordingly and can connect to the (IPv6) internet.
Well, there are global scope IPv6 addresses (like official 'live' IPv6 addresses), site local (internal lan addresses, like 192.168.x.x for IPv4, but its use is deprecated) and link-local (used for IPv6 autoconfiguration). If you want to have a working IPv6 connection to the rest of the world, you will need (a) global scope IPv6 address(es). Thats what the IPv6 providers (native ISPs, tunnel broker) will assign to you.
Most IPv6 tunnel brokers (freenet6, sixxs,
Usually the IPv6 addresses are derived from your (48bit)-MAC address to automatically create a (64bit)-EUI-64 IPv6 address. For this to work you have set up a router advertizing service (e.g. radvd under Linux), which will broadcast - within your lan - the prefix to use, and the PCs in your lan will use this info and automatically create proper IPv6 addresses by themselves.
However if the IPv6 'privacy extensions/temporary addresses' are enabled on a PC (by default enabled on Windows, disabled on Linux), it won't create a EUI-64 IPv6 address (from which you can easily figure out their MAC), but it will use a randomized IPv6 address instead.
You can also avoid using 'radvd' entirely and just setup your PCs to use statically assigned IPv6 addresses (e.g. in the PC's boot scripts), and thus you can make full use of the 80 bit address range.
N.B. there is also a DHCPv6, so you can assign to each MAC address a unique IPv6 address YOU specify, but the DHCPv6 protocol is work-in-progress and I haven't seen a working implementation yet.
I suppose your current network setup is something like this:
In this setup you can either use the NAT box itself as a IPv6 tunnel endpoint/router, which will provide your subnet with IPv6 connectivity.
Another way would be to port-forward the IPv6 tunnel traffic to any of the PCs behind the NAT box, and do the IPv6 routing from there.
Anyway, when the PCs in your lan want to connect to a host on the internet via IPv6, they will connect to the IPv6 router, and the router will forward the packets though the IPv6 tunnel to your IPv6 tunnel broker.
Since the tunnel broker need to know that you are entitled to use their service and where they should forward the IPv6 tunnel traffic, you might also have to 'login' or use a special software to initiate/enable the IPv6 tunnel. How this works exaclty depends on your IPv6 tunnel provider.
Let's assume you have the IPv4 class-A network 45.x.x.x. Its netmask is therefore 255.255.255.0.
...
I meant 255.0.0.0 of course
Max
Oh, I forgot to answer your last question:
/48 subnet) before I discovered www.sixxs.net (which I can really recommend to european users). Sixxs.net just announced it's 1000th subnet (and has a little more than 2000 users).
Have any people successfully set up something like this, maybe using services like freenet6?
Yes, quite some have, including me. I was using freenet6 (with a
There are many more IPv6 tunnel ISPs, just google for "IPv6 tunnel broker". Choose the ones which are closest to your location (low pings) and offer the good service/support (no filtering, good forums).
I would also love a block of live IPv6 addresses for my home. I currently have an old P200 doing NAT for the network, and it's bloody great. I run Smoothwall linux on it, which is designed to be run on machines acting as a firewall/router.
/8 (like in 45.0.0.0/24). /8 means that the first 8 bit of the IP address specify the network (and are fixed), and the rest (32bit - 8bit = 24bit) specify the host (and can be used by you). In our example this means you can have/choose IP addresses from between 45.0.0.0 - 45.255.255.255.
/48 prefix, it is quite similar; however a IPv6 address has 128bit. instead of 32bit (for IPv4).
I do not fully understand your question. There is no NAT for IPv6 (at least Linux doesn't support it, there is no need for it, and AFAIK it doesn't even exist). If you referring to a IPv6 router/tunnel gateway, then yes, Linux can do that easily.
Do any similar distros do this for IPv6?
I haven't come across a all-in-one IPv6 capable firewall Linux distribution. However it is not to difficult to enhance an existing with IPv6 support (usually you just need ip6tables, radvd and a IPv6-enabled kernel).
Is it easy to migrate an IPv4 NAT network like mine to IPv6 (assuming all the clients are IPv6-capable)?
Yes, it is rather easy. The only thing you'll need in most setups is running 'radvd' on the IPv6 router.
Oh, and what do people mean by "/48"?
Let's assume you have the IPv4 class-A network 45.x.x.x. Its netmask is therefore 255.255.255.0. This is often abbreviated with the suffix
The
If you have a IPv6 network with a
For example, let's assume you have the following IPv6 network 2001:1:1::/48.
This means the first 48 bit are fixed (2001:1:1:) and you can use (128bit - 48bit =) 80bit to address any host in your subnet. Just a remark: the numbers between two colons ':' of an IPv6 address are 16bit wide. So the range would be from
2001:0001:0001:0000:0000:0000:0000:0000 to
2001:0001:0001:FFFF:FFFF:FFFF:FFFF:FFFF.
That's a big number: 1,208,925,819,614,629,174,706,176 addresses just for you!
arglll. I think I need some sleep. Typos all over the place. Please forgive me!
/.
Oh, I forgot, this is
The problem is not the brightness contrast (which you can change by reducing the transparency level), but the colour contrast.
...
Choosing the right colours is more important than choosing the right brightness difference. Most PC user are not aware of this fact.
Equiluminant colors is only once think that comes to mind when I think what can go wrong
A remark to screenshot 1:
;)
Although I think transparency/translucency is a nice feature to have, a X terminal window is definitely is NOT an application where you want to use it. Do you really want to damage your eyesight?
The background picture is nice 'though
This exploit, as well as the mremap ones, were derived from intimate examination of the source.
Some might disagree. This bug was discovered here and was later posted and analysed on the lkml.
Just a few comments to your build guide:
/usr/src ./linux-2.6.7 ./linux
/boot/ /etc/grub.conf
/boot/grub/menu.lst. .config aswell.
1) su -
Not neccessary at this early step, ie. not needed for compiling the kernel. Do a 'su' when you are about to install the compiled kernel&modules.
2) cd
5) ln -s
Not needed. 5) is actually discouraged by Linus. Just unpack the linux kernel sources somewhere and cd into that directory.
9) make bzImage
10) make modules
both commands are only needed for 2.4.x kernels and if you compile a kernel for the ix86 platform. If you are using 2.6.x, you should simply do a 'make'.
11) cd arch/i386/boot
12) cp bzImage
13) edit
are also only needed if you compile for the Linux/ix86 platform. 13) only applies if you are using GRUB as a bootloader on a RedHat system. BTW, GRUB's config file is usually in
You are also missing a 'make modules_install' and it might be a good idea to save your System.map and
Instead of 11-12) you might want to do a simple 'make install' (for 2.6.x kernels). Also try out 'make help'.
No, it isn't
and perhaps grandparent down a bit.
Grandparent post makes much more sense if you replace "unstable" with "testing" (and vice versa).
Unstable is unstable, because it is
- packages are not guaranteed to *work* on all platforms
- using unstable might have broken dependencies, ie. apt-get is not guaranteed to work properly
- the pool is quite 'unstable', ie. you'll get alot of updates every day
Having said that, 'unstable' is indeed rather stable most of the time (at least on ix86), at least comparable to what RedHat or SuSE call a 'new release'.
Testing however contains only packages from unstable that didn't have any bug reports for the last 10 days (IIRC, and meet dependency requirements, and more).
So 'unstable' is if you really want to use the absolutely latest software (just a few days old), and testing if you want very recent software, but at least with no (big, bad) surprises.
No, I think he meant this.
Is it 'myth'?
Unfortunately such methods have been used in ancient Egypt 4000 years ago already.
Yes, but this guy is using nigerian sand, not egyptian sand!
Microsoft Word/Office or any other Microsoft products after Bill Gates gave this interview in 1995.
And no, it's not a fake.
Well, we might not have clippy, but we have Vigor
... inspired by User Friendly
I know its compilable on other platforms, its just not used by any signifigant numbers of developers on other platforms.
GNUstep is there and is ported on many platforms: all kinds of Unix variants (Linux, *BSD, Solaris etc.), Windows and even Mac OS X.
It is very stable (actually for quite a long time now), OpenStep Foundation is implemented 100%, but just AppKit (graphical stuff) is missing some things.
And of course the stuff that was added in Cocoa and was not part in the OpenStep specification is also added in GNUstep when possible.
BTW, we always look for developers (both for GNUstep and for apps that run on GNUstep)!
Liberated? So it means it's out in the wild!
...)
Now the laws of nature applies: survival of the fittest!
I wonder how long it will survive with all these evil predators out there (Linux, *BSD,
You might want to try out HostAP.
Their drivers seem to me very stable, and they support 2.6 aswell (N.B. just building one driver with e.g. "make pccard" didn't work for me for 2.6, but building ALL drivers with a simple "make" worked.)
I'm not talking about using the card in HostAP mode (ie. using your wireless network card as a access point). You can do that of course, but I just wanted to recommend these drivers because I've tried all other drivers for prism2/2.5 cards, and none worked for the various non-ix86 architectures I'm using.
The HostAP drivers however work on all of them!
Sorry for being to rude in my previous post, you actually have a point here.
...
He said ditto and implied that RFC 2396 was superceded by RFC 2616, but this is not the case.
However the description of HTTP URLs in RFC 2616 is another hint for you that you might be wrong
Again you missed the point!
It is not clear to me whether you are a troll or just stubborn.
His link points to a RFC that makes references to your beloved RFC 2396, but STILL MENTIONS that "user:password" is not allowed for HTTP URLs. Why would it do that if it was allowed in RFC 2396 (according to you)?