329 reputation
725
bio website melikedev.com
location Murrieta, CA
age 41
visits member for 3 years, 3 months
seen yesterday

We are working on the next big social media project. If you are interested in the project drop me a line @ mike.purcell@shouttag.com.


Oct
14
awarded  Popular Question
Sep
27
comment Google Apps MX for User Accounts, Custom Postfix for Sending only, same domain
Awesome I'll check it out. Thanks for the response. Wanted to give you credit via accepted answer if it worked out.
Sep
27
comment Google Apps MX for User Accounts, Custom Postfix for Sending only, same domain
Could you convert to an answer with more information about the acronyms you stated, and why they are relevant?
Sep
27
asked Google Apps MX for User Accounts, Custom Postfix for Sending only, same domain
Sep
25
awarded  Notable Question
Sep
6
comment How to Configure Secure Connectivity between Multiple Subnets
In the example you gave you have -a 10.254.10.1, the 10.x is a class A non-routable range correct? I assumed that the supernode was able to store the gateway information so it knows how to reach that node.
Sep
6
comment How to Configure Secure Connectivity between Multiple Subnets
Why? It makes more sense to me to have each edge node register the internal, assigned ip address with the supernode, not have an actual ip address, then a different ip address just for the n2n to work.
Sep
5
comment How to Configure Secure Connectivity between Multiple Subnets
The eth0:0 alias allows for the server to be on the 10.0.0.0/18 network as the primary eth0 config is assigned a static ip via linode.
Sep
5
comment How to Configure Secure Connectivity between Multiple Subnets
I cloned the n2n_v2_fork version, and followed the rpm build instructions given via the INSTALL file, and it appears the version is 2.1.0-1, which is the same version available via epel repo. You mentioned that you setup a supernode and a single edge node, as I mentioned in my latest update I setup supernode and edge node on one server (diff ports: 55555, 55554) and edge node on another subnet. But was unable to get the two to ping each other. All while iptables was off, and router on subnet1 was pinholed to allow incoming udp traffic to 55554.
Sep
5
comment How to Configure Secure Connectivity between Multiple Subnets
Is that the same version as available via epel? The version I tried to work with on this project is 2.1.0-1.el6
Sep
5
accepted libvirtd - Getting vps to use existing bridge
Sep
5
comment libvirtd - Getting vps to use existing bridge
Thanks for the confirmation. When I first setup the vps I didn't notice the new interfaces, so when I started noticing them after a recent rebuild, I thought I did something wrong.
Sep
4
comment How to Configure Secure Connectivity between Multiple Subnets
The supernode is not behind a router, rather it is running iptables, and I disabled iptables for testing. Supernode is accessible to all nodes.
Sep
4
revised How to Configure Secure Connectivity between Multiple Subnets
added 40 characters in body
Sep
4
comment How to Configure Secure Connectivity between Multiple Subnets
Added an update to OP.
Sep
4
revised How to Configure Secure Connectivity between Multiple Subnets
added 1259 characters in body
Sep
4
asked libvirtd - Getting vps to use existing bridge
Sep
3
comment How to Configure Secure Connectivity between Multiple Subnets
Right, I figured that, the problem I have is the docs posted in previous comment show the user creating a tunnel tun0, but then reference -d n2n0, is this a typo, shouldn't it read: -d tun0?
Sep
3
comment How to Configure Secure Connectivity between Multiple Subnets
Thanks for the edge node config example, I noticed you have a -d edge87 switch, I assume edge87 is the name of the tunnel you created when following the steps outlined via the n2n git readme file? github.com/lukablurr/n2n_v2_fork
Aug
29
comment How to Configure Secure Connectivity between Multiple Subnets
Not really a strong response, as I have poured over documents related to n2n since you posted your answer. I'm still trying to figure out how the supernodes fit within the overall architecture of the network. Basically if I have subnet1 and subnet2 and no tunnel is established between the respective routers, adding a supernode to subnet1 will allow subnet2 to access nodes on subnet1? Or is it that as long as a node on subnet1 has access to supernode, as does a node on subnet2, then both nodes can communicate, even with no actual tunnel between the subnets?