From: "Eric S. Johansson" <esj@eggo.org>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Isn't right with the configuration script
Date: Mon, 22 Sep 2014 19:51:20 -0400 [thread overview]
Message-ID: <5420B5F8.8040708@eggo.org> (raw)
I changed the internal subnet and it looks like everything changes
correctly but what happens is the interface comes up and I can ping it.
I see IPv6 traffic coming from it (I believe) but there's no IPv4
response .I should see if I can set up my Linux machine as IPv6 and see
if I can access any of the services there. IPv6 is new terrain for me so
helpful pointers would be quite welcome.
I would also appreciate any pointers to documentation explaining why all
the little subnets and why so many network interfaces.
My goal in this reconfiguration is to create a /24 subnet and give all
the interfaces ethernet, Wi-Fi access to the subnet. I'm also going to
put in a VPN so that outside consultants can have access to the subnet.
I think I can improve the configuration script so that it can "fix" what
is breaking the IPv4 services and hopefully, increase flexibility. I
would like to be able to change the entire network configuration for
different subnet sizes etc. but in order to do that, I will need a much
better understanding of what the network architecture is supposed to be.
I would also like to fix the configuration script so that you don't need
to know the starting IP address/network. I should be able to just change
the desired IP address and rerun the script and have it work. Again,
with the knowledge, I'm going to put in the effort to make this happen.
For some reason, every time I work on a firewall project, I get stuck
with IP address management. :-)
--- eric
next reply other threads:[~2014-09-22 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 23:51 Eric S. Johansson [this message]
2014-09-23 10:56 ` Rich Brown
2014-09-23 23:03 ` Eric S. Johansson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5420B5F8.8040708@eggo.org \
--to=esj@eggo.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox