[prev in list] [next in list] [prev in thread] [next in thread]
List: pfsense-dev
Subject: Re: [pfS-Dev] IPV6 Development
From: "Robert B. Nelson" <robertn () the-nelsons ! org>
Date: 2015-05-21 18:42:00
Message-ID: 2045955873.1847.1432233720484.JavaMail.zimbra () the-nelsons ! org
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Has anyone had a chance to play with this yet?
| From: "Robert Nelson" <robertn@the-nelsons.org>
| To: "dev" <dev@lists.pfsense.org>
| Sent: Wednesday, May 6, 2015 9:16:39 PM
| Subject: Re: [pfS-Dev] IPV6 Development
| So I made a few interesting discoveries with DHCP and DNS.
| I have a server on my internal network that I want to publish.
| If I configure a static address in DHCP then DHCP doesn't update the DNS server
| so that is a non starter.
| If I let DHCP assign the address it publishes the correct address with the
| current prefix on the external DNS server using DDNS. It also puts the hostname
| in the leases file but it is a ddns-fwd-name which isn't what dhcpleases6 looks
| for. I can't get the host-name into the leases file for dhcpleases6 to add it
| to /etc/hosts. I can't use the DNS resolver overrides since I don't know the
| prefix and the GUI doesn't provide any clean way to specify the context so I
| can mangle the prefix into the address.
| But ..
| I have a rather elegant way to make it all work. :-)
| I let DHCP assign the address. This takes care of the external DNS.
| I configure the clients to update the DNS, I'm running an Active Directory
| Domain on my home network so that gets both IPv4 and IPv6 addresses in the
| local DNS.
| I use Firewall aliases with the local names in my Firewall rules.
| The best part is I don't need to add any special processing for prefix addresses
| in the Firewall.
| So I'm done!!
|| From: "Robert Nelson" <robertn@the-nelsons.org>
|| To: "dev" <dev@lists.pfsense.org>
|| Sent: Wednesday, May 6, 2015 12:22:26 AM
|| Subject: Re: [pfS-Dev] IPV6 Development
|| I believe all the DHCP work is complete now.
|| This includes:
|| DHCP configuration
|| DDNS support
|| Static leases
|| Registration of static entries in Unbound/Dnsmasq
|| I'm going to take a break before I tackle Firewall rules. Please let me know if
|| you encounter any issues or have any feedback.
|| Thanks
||| From: "Robert Nelson" <robertn@the-nelsons.org>
||| To: "dev" <dev@lists.pfsense.org>
||| Sent: Monday, May 4, 2015 2:24:51 PM
||| Subject: Re: [pfS-Dev] IPV6 Development
||| I completed the first step, enabling the DHCP server on interfaces with
||| delegated prefixes.
||| There are two branches one based off master and one based off RELENG_2_2, here
||| are the links:
||| master:
||| https://github.com/Robert-Nelson/pfsense/tree/tracking-dhcp
||| RELENG_2_2:
||| https://github.com/Robert-Nelson/pfsense/tree/tracking-dhcp_2_2
|||| From: "Ermal Luçi" <ermal.luci@gmail.com>
|||| To: "dev" <dev@lists.pfsense.org>
|||| Sent: Saturday, May 2, 2015 2:03:41 AM
|||| Subject: Re: [pfS-Dev] IPV6 Development
|||| What you can do here is just to allow on DHCP server the part extra of the
|||| delegation and the subnet.
|||| The other part can be concatenated when the prefix is assigned during track
|||| events.
|||| On Fri, May 1, 2015 at 11:17 PM, Robert B. Nelson < robertn@the-nelsons.org >
|||| wrote:
||||| Okay I see now why a special character won't work. I was thinking about the
||||| simple case, one WAN, one LAN. But that doesn't provide any context in the case
||||| of multiple WANs or even one WAN but multiple LANs using portions of a /60
||||| prefix.
|||||| From: "Robert Nelson" < robertn@the-nelsons.org >
|||||| To: "dev" < dev@lists.pfsense.org >
|||||| Sent: Friday, May 1, 2015 12:02:28 PM
|||||| Subject: Re: [pfS-Dev] IPV6 Development
|||||| Since aliases are for Firewall rules how does that help DHCP or DNS? I need some
|||||| way to represent the current prefix EVERWHERE an IP address can be used
||||||| From: "Ermal Luçi" < ermal.luci@gmail.com >
||||||| To: "dev" < dev@lists.pfsense.org >
||||||| Sent: Friday, May 1, 2015 8:52:13 AM
||||||| Subject: Re: [pfS-Dev] IPV6 Development
||||||| Please do not use special chars.
||||||| You can use a form of alias with that name or trackWAN or similar :)
||||||| On Fri, May 1, 2015 at 9:51 AM, Robert B. Nelson < robertn@the-nelsons.org >
||||||| wrote:
|||||||| ----- Original Message -----
|||||||| | From: "Chris Buechler" < cmb@pfsense.org >
|||||||| | To: "dev" < dev@lists.pfsense.org >
|||||||| | Sent: Thursday, April 30, 2015 8:44:19 PM
|||||||| | Subject: Re: [pfS-Dev] IPV6 Development
|||||||| | On Fri, Apr 24, 2015 at 5:52 PM, Robert B. Nelson
|||||||| | < robertn@the-nelsons.org > wrote:
|||||||| |> Is anyone working on improving support for IPv6?
|||||||| | At this moment, not any of what you're referring to here.
|||||||| |> Specifically I'm talking
|||||||| |> about the ability to run the DHCP server on the LAN interface when it is set
|||||||| |> up to track a delegated prefix from the WAN. Also the ability to specify
|||||||| |> Firewall rules that reference source/destination addresses using the
|||||||| |> delegated prefix. Without these two features I can't see how one can expose
|||||||| |> services available on the private network to the internet using IPv6.
|||||||| | This covers all my big wants with PD IPv6. Those feature gaps would be
|||||||| | really nice to fill.
|||||||| | Functionality-wise, where there is v6 PD enabled, DHCPv6 should just
|||||||| | allow entering 64 bits of address space for "from" and "to", and show
|||||||| | the delegated prefix will be appended to the beginning of the
|||||||| | user-entered input.
|||||||| | Firewall rules and aliases are more difficult. Especially since PD is
|||||||| | interface-specific. For firewall and NAT rules, I guess the src/dst
|||||||| | drop down could add an option for "LAN PD prefix" alongside "LAN net",
|||||||| | etc., which appends the prefix to 64 bits of user-configurable host
|||||||| | address. Aliases, I can't think of a great way to handle that.
|||||||| | Allowing a keyword like LANPREFIX that becomes a variable when the
|||||||| | alias is loaded maybe an option, but it's ugly. Then you rename LAN
|||||||| | and your alias is broken.
|||||||| I was thinking about perhaps using some special character such as * or % to
|||||||| represent the prefix in an IPv6 address. For example *:0123:4567:89ab:cdef. This
|||||||| would be used anywhere in the UI that an IPv6 host address is allowed and then
|||||||| replaced with the current prefix whenever the configuration files are generated.
|||||||| |> If these are not being addressed I'd be willing to give it a try providing
|||||||| |> someone was available to answer questions. I'm a very experienced developer
|||||||| |> but I have limited experience with IPv6.
|||||||| | This is definitely something I would help test, and can answer any
|||||||| | questions re: IPv6. My native IPv6 at home is via PD, and these things
|||||||| | have been annoying me. If you could do it out of a fork on github, I
|||||||| | can sync from there to help test.
|||||||| I'm also using IPv6 with prefix delegation at home. I'll set up a branch on my
|||||||| github
|||||||| fork and let everyone here know when I've made enough progress to allow others
|||||||| to give
|||||||| it a try.
|||||||| | _______________________________________________
|||||||| | Dev mailing list
|||||||| | Dev@lists.pfsense.org
|||||||| | https://lists.pfsense.org/mailman/listinfo/dev
|||||||| _______________________________________________
|||||||| Dev mailing list
|||||||| Dev@lists.pfsense.org
|||||||| https://lists.pfsense.org/mailman/listinfo/dev
||||||| --
||||||| Ermal
||||||| _______________________________________________
||||||| Dev mailing list
||||||| Dev@lists.pfsense.org
||||||| https://lists.pfsense.org/mailman/listinfo/dev
|||||| _______________________________________________
|||||| Dev mailing list
|||||| Dev@lists.pfsense.org
|||||| https://lists.pfsense.org/mailman/listinfo/dev
||||| _______________________________________________
||||| Dev mailing list
||||| Dev@lists.pfsense.org
||||| https://lists.pfsense.org/mailman/listinfo/dev
|||| --
|||| Ermal
|||| _______________________________________________
|||| Dev mailing list
|||| Dev@lists.pfsense.org
|||| https://lists.pfsense.org/mailman/listinfo/dev
||| _______________________________________________
||| Dev mailing list
||| Dev@lists.pfsense.org
||| https://lists.pfsense.org/mailman/listinfo/dev
|| _______________________________________________
|| Dev mailing list
|| Dev@lists.pfsense.org
|| https://lists.pfsense.org/mailman/listinfo/dev
| _______________________________________________
| Dev mailing list
| Dev@lists.pfsense.org
| https://lists.pfsense.org/mailman/listinfo/dev
[Attachment #5 (text/html)]
<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; \
color: #000000"><div>Has anyone had a chance to play with this \
yet?</div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div \
data-marker="__HEADERS__"><blockquote style="border-left:2px solid \
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:norm \
al;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: \
</b>"Robert Nelson" <robertn@the-nelsons.org><br><b>To: </b>"dev" \
<dev@lists.pfsense.org><br><b>Sent: </b>Wednesday, May 6, 2015 9:16:39 \
PM<br><b>Subject: </b>Re: [pfS-Dev] IPV6 Development<br></blockquote></div><div \
data-marker="__QUOTED_TEXT__"><blockquote style="border-left:2px solid \
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:norm \
al;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div \
style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: \
#000000"><div>So I made a few interesting discoveries with DHCP and \
DNS.</div><br><div>I have a server on my internal network that I want to \
publish.</div><br><div>If I configure a static address in DHCP then DHCP doesn't \
update the DNS server so that is a non starter.</div><br><div>If I let DHCP assign \
the address it publishes the correct address with the current prefix on the external \
DNS server using DDNS. It also puts the hostname in the leases file but it is a \
ddns-fwd-name which isn't what dhcpleases6 looks for. I can't get the host-name \
into the leases file for dhcpleases6 to add it to /etc/hosts. I can't use the \
DNS resolver overrides since I don't know the prefix and the GUI doesn't provide \
any clean way to specify the context so I can mangle the prefix into the \
address.</div><br><div>But ..</div><br><div>I have a rather elegant way to make it \
all work. :-)</div><br><div>I let DHCP assign the address. This takes care of \
the external DNS.</div><br><div>I configure the clients to update the DNS, I'm \
running an Active Directory Domain on my home network so that gets both IPv4 and IPv6 \
addresses in the local DNS.</div><br><div>I use Firewall aliases with the local names \
in my Firewall rules.</div><br><div>The best part is I don't need to add any \
special processing for prefix addresses in the Firewall.</div><br><div>So I'm \
done!!</div><br><hr id="zwchr"><div><blockquote style="border-left:2px solid \
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:norm \
al;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: \
</b>"Robert Nelson" <robertn@the-nelsons.org><br><b>To: </b>"dev" \
<dev@lists.pfsense.org><br><b>Sent: </b>Wednesday, May 6, 2015 12:22:26 \
AM<br><b>Subject: </b>Re: [pfS-Dev] IPV6 \
Development<br></blockquote></div><div><blockquote style="border-left:2px solid \
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:norm \
al;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div \
style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: \
#000000"><div>I believe all the DHCP work is complete now.</div><br><div>This \
includes:</div><div> DHCP configuration</div><div> DDNS \
support</div><div> Static leases</div><div> Registration of \
static entries in Unbound/Dnsmasq</div><br><div>I'm going to take a break before I \
tackle Firewall rules. Please let me know if you encounter any issues or have \
any feedback.</div><br><div>Thanks</div><br><hr id="zwchr"><div><blockquote \
style="border-left:2px solid \
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:norm \
al;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: \
</b>"Robert Nelson" <robertn@the-nelsons.org><br><b>To: </b>"dev" \
<dev@lists.pfsense.org><br><b>Sent: </b>Monday, May 4, 2015 2:24:51 \
PM<br><b>Subject: </b>Re: [pfS-Dev] IPV6 \
Development<br></blockquote></div><div><blockquote style="border-left:2px solid \
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:norm \
al;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div \
style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: \
#000000"><div>I completed the first step, enabling the DHCP server on interfaces with \
delegated prefixes.</div><br><div>There are two branches one based off master and one \
based off RELENG_2_2, here are the \
links:</div><br><div>master:</div><div> https://github.com/Robe \
rt-Nelson/pfsense/tree/tracking-dhcp</div><br><div>RELENG_2_2:</div><div> & \
nbsp; https://github.com/Robert-Nelson/pfsense/tree/tracking-dhcp_2_2</div><br><hr \
id="zwchr"><div><blockquote style="border-left:2px solid \
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:norm \
al;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: \
</b>"Ermal Luçi" <ermal.luci@gmail.com><br><b>To: </b>"dev" \
<dev@lists.pfsense.org><br><b>Sent: </b>Saturday, May 2, 2015 2:03:41 \
AM<br><b>Subject: </b>Re: [pfS-Dev] IPV6 \
Development<br></blockquote></div><div><blockquote style="border-left:2px solid \
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:norm \
al;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div \
dir="ltr">What you can do here is just to allow on DHCP server the part extra of the \
delegation and the subnet.<div>The other part can be concatenated when the prefix is \
assigned during track events.</div></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Fri, May 1, 2015 at 11:17 PM, Robert B. Nelson <span \
dir="ltr"><<a href="mailto:robertn@the-nelsons.org" \
target="_blank">robertn@the-nelsons.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div><div \
style="font-family:arial,helvetica,sans-serif;font-size:12pt;color:#000000"><div>Okay \
I see now why a special character won't work. I was thinking about the simple \
case, one WAN, one LAN. But that doesn't provide any context in the case of \
multiple WANs or even one WAN but multiple LANs using portions of a /60 \
prefix.</div><br><hr><div><blockquote style="border-left:2px solid \
#1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:norm \
al;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><b>From: \
</b>"Robert Nelson" <<a href="mailto:robertn@the-nelsons.org" \
target="_blank">robertn@the-nelsons.org</a>><br><b>To: </b>"dev" <<a \
href="mailto:dev@lists.pfsense.org" \
target="_blank">dev@lists.pfsense.org</a>><br><b>Sent: </b>Friday, May 1, 2015 \
12:02:28 PM<div><div class="h5"><br><b>Subject: </b>Re: [pfS-Dev] IPV6 \
Development<br></div></div></blockquote></div><div><div class="h5"><div><blockquote \
style="border-left:2px solid \
#1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:norm \
al;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><div \
style="font-family:arial,helvetica,sans-serif;font-size:12pt;color:#000000"><div><span \
style="color:rgb(0,0,0);font-family:'Times New \
Roman';font-size:14.1599998474121px;font-style:normal;font-variant:normal;font-weight: \
normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text- \
transform:none;white-space:normal;word-spacing:0px;display:inline!important;float:none;background-color:rgb(255,255,255)">Since \
aliases are for Firewall rules how does that help DHCP or DNS? I need some way \
to represent the current prefix EVERWHERE an IP address can be \
used</span></div><br><hr><div><blockquote style="border-left:2px solid \
#1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:norm \
al;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><b>From: \
</b>"Ermal Luçi" <<a href="mailto:ermal.luci@gmail.com" \
target="_blank">ermal.luci@gmail.com</a>><br><b>To: </b>"dev" <<a \
href="mailto:dev@lists.pfsense.org" \
target="_blank">dev@lists.pfsense.org</a>><br><b>Sent: </b>Friday, May 1, 2015 \
8:52:13 AM<br><b>Subject: </b>Re: [pfS-Dev] IPV6 \
Development<br></blockquote></div><div><blockquote style="border-left:2px solid \
#1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:norm \
al;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><div \
dir="ltr">Please do not use special chars.<br><div>You can use a form of alias with \
that name or trackWAN or similar :)</div></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Fri, May 1, 2015 at 9:51 AM, Robert B. Nelson <span \
dir="ltr"><<a href="mailto:robertn@the-nelsons.org" \
target="_blank">robertn@the-nelsons.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div><div><br> <br> ----- Original Message -----<br> | From: \
"Chris Buechler" <<a href="mailto:cmb@pfsense.org" \
target="_blank">cmb@pfsense.org</a>><br> | To: "dev" <<a \
href="mailto:dev@lists.pfsense.org" target="_blank">dev@lists.pfsense.org</a>><br> \
| Sent: Thursday, April 30, 2015 8:44:19 PM<br> | Subject: Re: [pfS-Dev] IPV6 \
Development<br> <br> | On Fri, Apr 24, 2015 at 5:52 PM, Robert B. Nelson<br> | <<a \
href="mailto:robertn@the-nelsons.org" target="_blank">robertn@the-nelsons.org</a>> \
wrote:<br> |> Is anyone working on improving support for IPv6?<br> |<br> | At this \
moment, not any of what you're referring to here.<br> |<br> |> Specifically \
I'm talking<br> |> about the ability to run the DHCP server on the LAN interface \
when it is set<br> |> up to track a delegated prefix from the WAN. Also the \
ability to specify<br> |> Firewall rules that reference source/destination \
addresses using the<br> |> delegated prefix. Without these two features I \
can't see how one can expose<br> |> services available on the private network to \
the internet using IPv6.<br> |><br> |<br> | This covers all my big wants with PD \
IPv6. Those feature gaps would be<br> | really nice to fill.<br> |<br> | \
Functionality-wise, where there is v6 PD enabled, DHCPv6 should just<br> | allow \
entering 64 bits of address space for "from" and "to", and show<br> | the delegated \
prefix will be appended to the beginning of the<br> | user-entered input.<br> |<br> | \
Firewall rules and aliases are more difficult. Especially since PD is<br> | \
interface-specific. For firewall and NAT rules, I guess the src/dst<br> | drop down \
could add an option for "LAN PD prefix" alongside "LAN net",<br> | etc., which \
appends the prefix to 64 bits of user-configurable host<br> | address. Aliases, I \
can't think of a great way to handle that.<br> | Allowing a keyword like LANPREFIX \
that becomes a variable when the<br> | alias is loaded maybe an option, but it's \
ugly. Then you rename LAN<br> | and your alias is broken.<br> <br></div></div>I was \
thinking about perhaps using some special character such as * or % to<br> represent \
the prefix in an IPv6 address. For example *:0123:4567:89ab:cdef. \
This<br> would be used anywhere in the UI that an IPv6 host address is allowed and \
then<br> replaced with the current prefix whenever the configuration files are \
generated.<br> <span><br> |<br> |> If these are not being addressed I'd be willing \
to give it a try providing<br> |> someone was available to answer questions. \
I'm a very experienced developer<br> |> but I have limited experience with \
IPv6.<br> |><br> |<br> | This is definitely something I would help test, and can \
answer any<br> | questions re: IPv6. My native IPv6 at home is via PD, and these \
things<br> | have been annoying me. If you could do it out of a fork on github, I<br> \
| can sync from there to help test.<br> <br> </span>I'm also using IPv6 with prefix \
delegation at home. I'll set up a branch on my github<br> fork and let everyone \
here know when I've made enough progress to allow others to give<br> it a \
try.<br><div><div><br> | _______________________________________________<br> | Dev \
mailing list<br> | <a href="mailto:Dev@lists.pfsense.org" \
target="_blank">Dev@lists.pfsense.org</a><br> | <a \
href="https://lists.pfsense.org/mailman/listinfo/dev" \
target="_blank">https://lists.pfsense.org/mailman/listinfo/dev</a><br> \
_______________________________________________<br> Dev mailing list<br> <a \
href="mailto:Dev@lists.pfsense.org" target="_blank">Dev@lists.pfsense.org</a><br> <a \
href="https://lists.pfsense.org/mailman/listinfo/dev" \
target="_blank">https://lists.pfsense.org/mailman/listinfo/dev</a><br></div></div></blockquote></div><br><br \
clear="all"><br>-- <br><div>Ermal</div></div><br>_______________________________________________<br>Dev \
mailing list<br><a href="mailto:Dev@lists.pfsense.org" \
target="_blank">Dev@lists.pfsense.org</a><br><a \
href="https://lists.pfsense.org/mailman/listinfo/dev" \
target="_blank">https://lists.pfsense.org/mailman/listinfo/dev</a><br></blockquote></div></div><br>_______________________________________________<br>Dev \
mailing list<br><a href="mailto:Dev@lists.pfsense.org" \
target="_blank">Dev@lists.pfsense.org</a><br><a \
href="https://lists.pfsense.org/mailman/listinfo/dev" \
target="_blank">https://lists.pfsense.org/mailman/listinfo/dev</a><br></blockquote></d \
iv></div></div></div></div><br>_______________________________________________<br> \
Dev mailing list<br> <a href="mailto:Dev@lists.pfsense.org" \
target="_blank">Dev@lists.pfsense.org</a><br> <a \
href="https://lists.pfsense.org/mailman/listinfo/dev" \
target="_blank">https://lists.pfsense.org/mailman/listinfo/dev</a><br> \
<br></blockquote></div><br><br clear="all"><br>-- <br><div \
class="gmail_signature">Ermal</div> </div>
<br>_______________________________________________<br>Dev mailing \
list<br>Dev@lists.pfsense.org<br>https://lists.pfsense.org/mailman/listinfo/dev<br></blockquote></div></div><br>_______________________________________________<br>Dev \
mailing list<br>Dev@lists.pfsense.org<br>https://lists.pfsense.org/mailman/listinfo/de \
v<br></blockquote></div></div><br>_______________________________________________<br>Dev \
mailing list<br>Dev@lists.pfsense.org<br>https://lists.pfsense.org/mailman/listinfo/de \
v<br></blockquote></div></div><br>_______________________________________________<br>Dev \
mailing list<br>Dev@lists.pfsense.org<br>https://lists.pfsense.org/mailman/listinfo/dev<br></blockquote></div></div></body></html>
_______________________________________________
Dev mailing list
Dev@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic