public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Bug Report: OVPN and changed green
Date: Tue, 20 May 2014 12:54:09 -0500	[thread overview]
Message-ID: <537B96C1.1060609@dailydata.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]

This MAY not be a bug. I was part of the testing for the original
openVPN ccd stuff and, when I upgraded the router that I had modified to
77, I did several things at one time. However, it appears to be a bug.
Here is exactly what I did. Note: I do not think #3 had anything to do
with this.

1. Upgraded from v75 to v77. Forgot to reboot.
2. Modified green interface to set subnet mask to /23 vs /24
3. Changed external IP.

When I did the above, many vpn connections did not have access to the
network. These were mainly the ones I had modified in the past to have
fixed IP addresses (with hard coded IPTables rules to allow them
access). Again, likely not part of the problem, but included for
completeness.

However, when I looked at the other files in ccd/, I noticed none of
them had the new subnet mask in the push statement. Thus, users would
not have the ability to get to the full range of green.

Very low priority as anyone changing this should know enough to go in
and edit it. But, should there be some script fired off when the green
interface changes that sets the new IP/subnet on the OVPN connections?

Rod


-- 
R. W. Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net

                 reply	other threads:[~2014-05-20 17:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=537B96C1.1060609@dailydata.net \
    --to=rodo@dailydata.net \
    --cc=development@lists.ipfire.org \
    /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