LOL!
IKnowNot, You didn't miss anything other than thoughts which were going on inside myself throughout this thread. My mind seems to take a subject and expand it in several different directions at once. So dont feel bad, you missed nothing. Bring up a subject and my mind just does that to me.
So at any rate, let me try to address each issue or question you had.
Quote:
It has changed from IPSec to IPv6 ( not that that is bad!, IMHO )
true. But on the other hand, that is also the logical progression happening in real life as well. Had I had the knowledge earlier that I got from this post, I would have more likely asked the question, how many of you are using IPv6. Again, I did not realize that one could have both in the kernel. I thought you either needed to implement IPv6 all the way around or leave it at IPv4. And then th13 brought up the issue about IPv6, and now, several topics are being disucssed here including, IPSec, IPv6, Wireless and WPA!
Quote:
How did Dr. Psy come up with.....
Again, this was an internal process happening in my mind as the thread unraveled. Nothing of that exact nature was discussed on this board. It was just the direction this post led my mind in.
Quote:
For some reason, in eight and a half hours and without discernable reason he recompiled a kernel ( doable, even on an i486, ) but then in eleven minutes realized the difference between IP6tables and iptables ( where is that documented? How did he find it so quick? )
The kernel recompile took little time, really. And where is the ip6tables documented and how did I find it so fast?
Google. After having recompiled the kernel and booted it, my first thought was my firewall [always thinking security first]. Looked it up as this thread was unraveling.
Quote:
then in another thirty-seven minutes had tried ip6tables rules in IPv4 firewall script which worked, no wait, fourteen minutes later edited to state ( I think ) that he needed to use iptables ( IPv4 ruleset ) to drop everything then it defaults to the ip6tables rules ??????
No, no, no. Originally I was trying to figure out how I could enforce the use of IPv6, and figured I would need to do it with firewall rules. But wasnt sure if I could use ip6tables rules in ipv4 ruleset. I wasnt sure if one could actually use iptables and ip6tables rules at the same time [which I now know, you can) So I simply added the ip6tables rules to the firewall script that I already had. And it worked. Appended iptables rule to drop everything on eth1 on my already running firewall with iptables. And also appended ip6tables rules to the script, which allowed IPv6 on the same interfaces via ip6tables.
Quote:
OK, if anyone is following here ( only if you are as drunk as me I expect ) I was under the assumption ( it has been a few months ) that there were Internet Servers that one could test IPv6 on, but one would have to tunnel to them via IPv4. Is this still the case?
As far as I know, yes. If you are setup via IPv6, you can connect to other systems running IPv6 via a tunnel. However, thisis not what I am doing. I am running IPv6 strictly internally. I am still 100% IPv4 externally.
Quote:
And how does one test IPv6 firewall rules unless both sides ( internal and external ) are both using IPv6? ( Dr. Psy must have set up internally multiple IPv6 machines in that eight and a half hours? Again, doable, but nothing stated as such. )
Yes, this is the case. On my external interface, I am still using IPv4. But internally, am using IPv6 set up on multiple systems. Which is, of course how I could test this myself at both ends. On the question of testing procedures, no 'thorough' testing has been done yet TH13. Obviously, thre hasn't been time for that. I simply tested IPv6 accessibility by setting up two systems which were IPv6 enabled. The IPv6 firewall rules were added and an echo request was sent to system number two, while system number two was running tcpdump in IPv6 mode to capture the IPv6 ICMP echo request packet, and vice versa.
I agree with you 110% IKnowNot. I really wish that this IPv6 thing was in place across the entire net. Wish it was already standard. Being as security oriented as I am, I am always trying to think of ways to add more security to whatever I do. It's not that I am the paranoid type really. And it's not that I have nuclear Missle Launch Codes on my system that I must protect with my life! It's just that I LOVE computer security! It's what I eat for dinner! This being the case, and knowing a little bit about IPv6, I know that it is much more robust and secure than IPv4. I want this thing in place ASAP! But I know the reasons why it is taking so long.
So... I was really extremely happy to come to the realization that IPv6 could be set up on my internal network, while still maintaining IPv4 connectivity and functionality. I realize that nobody said that here. It was not discussed or posted. But while this thread was unravelling, another window on my computer had a console open, and yet another, was running searches on Google. So I understand your confusion. However I thanked TH13, because simply by him bringing up the subject in this context, it led me to look some things up as I wondering about a few things on the subject of IPv6, which then led me to discover that I indeed could have both IPv6 and IPv4 running on my system at the same time. Realizing this, I whipped out make menuconfig and recompiled my kernel [all that needed to be done to my existing kernel was check about 7 or 8 options for IPv6 fuinctionality). Compiled it, booted it, and came back here and thanked TH13! And while the thread was still unravaling, I was testing various things in another open window, and still researching on google. I posted the question about iptables and ip6tables after I had started thinking about how I could enforce the use of IPv6 internally, since any servers I had open to the public would still need an IPv4 interface. They would also have an IPv6 interface but how would I force the use of IPv6 only internally if the interface was also accessible via IPv4. And while posting that, I was researching the issue. Didnt find anything exactly pertaining to that, so I started testing it myself to find out. When I discovered that I could use iptables and ip6tables together at the same ime through the use of a script. I came back and posted that this was possible.
So, as you can see there was a lot more going on on my side of things inside my own head rather than just wht was posted on this thread, I was researching, compiling and testing throughout this thread.
Sorry for the confusion there! Now you understand. correct? lol!
