On 24/4/18 12:11 am, John Lyon wrote:
If you found that thread, you found my answer. :-) I'm one of the posters
on that particular PFSense thread.
In short summary, I have a theory that should work but I haven't tested it
yet due to a lack of opportunity. The netgraph code that forwards the
EA
That's interesting. Why did you insert ng_vlan "backwards". My though is
that you would want to do something like this (because the whole point is
you want to remove the VID=0 tag since FreeBSD won't bind to VID=0):
ONT]em0]lower---downstream_vlan0[VLAN]--downstream
[eapfilter:]nomatch--
If you found that thread, you found my answer. :-) I'm one of the posters
on that particular PFSense thread.
In short summary, I have a theory that should work but I haven't tested it
yet due to a lack of opportunity. The netgraph code that forwards the
EAP-OL traffic works. The problem is hand
On 23/4/18 6:11 pm, Julian Elischer wrote:
On 23/4/18 5:55 pm, Julian Elischer wrote:
On 22/4/18 12:52 pm, GPz1100a wrote:
@John
Did you ever get this fully figured out? I'm trying to do what I
think is
the same thing with my fiber internet connection - eliminate the
need to use
the isp pro
On 23/4/18 5:55 pm, Julian Elischer wrote:
On 22/4/18 12:52 pm, GPz1100a wrote:
@John
Did you ever get this fully figured out? I'm trying to do what I
think is
the same thing with my fiber internet connection - eliminate the
need to use
the isp provided gateway (or at least reduce its functi
On 22/4/18 12:52 pm, GPz1100a wrote:
@John
Did you ever get this fully figured out? I'm trying to do what I think is
the same thing with my fiber internet connection - eliminate the need to use
the isp provided gateway (or at least reduce its function). I'm running
*opnsense*. This thread
htt
On 22/4/18 12:52 pm, GPz1100a wrote:
@John
Did you ever get this fully figured out? I'm trying to do what I think is
the same thing with my fiber internet connection - eliminate the need to use
the isp provided gateway (or at least reduce its function). I'm running
*opnsense*. This thread
htt
@John
Did you ever get this fully figured out? I'm trying to do what I think is
the same thing with my fiber internet connection - eliminate the need to use
the isp provided gateway (or at least reduce its function). I'm running
*opnsense*. This thread
https://forum.pfsense.org/index.php?topic
Hi John, did you ever try out my version?
Julian
On 7/1/18 4:06 am, Julian Elischer wrote:
On 7/1/18 4:02 am, John Lyon wrote:
Thanks for the clarification and all the help.
After Marko clarified that that edges/hooks are bidirectional, I
was able to get it working WAN to LAN and LAN to WAN
On 7/1/18 4:02 am, John Lyon wrote:
Thanks for the clarification and all the help.
After Marko clarified that that edges/hooks are bidirectional, I was
able to get it working WAN to LAN and LAN to WAN by using a pair of
one2many and ETF nodes.
The commands were (from memory):
#Create Unfilt
Thanks for the clarification and all the help.
After Marko clarified that that edges/hooks are bidirectional, I was able
to get it working WAN to LAN and LAN to WAN by using a pair of one2many and
ETF nodes.
The commands were (from memory):
#Create Unfiltered WAN Path
ngctl mkpeer igb0: one2many
On 6/1/18 9:22 pm, John Lyon wrote:
I just woke up with a follow-up question that may be my aha moment.
Are Netgraph edges between nodes always bidirectional? I have been
treating all of the edges as unidirectional, requiring me to create
two separate Netgraphs. But if they are bidirectional,
On Sat, 6 Jan 2018 08:22:25 -0500
John Lyon wrote:
> I just woke up with a follow-up question that may be my aha moment.
> Are Netgraph edges between nodes always bidirectional? I have been
> treating all of the edges as unidirectional, requiring me to create
> two separate Netgraphs. But if the
I just woke up with a follow-up question that may be my aha moment. Are
Netgraph edges between nodes always bidirectional? I have been treating all of
the edges as unidirectional, requiring me to create two separate Netgraphs.
But if they are bidirectional, that would explain some things.
Tha
Julian,
So this didn't work when I tried to implement it on hardware in real life
and I can't figure out why. I am sure it's really basic, but the error
message is not very descriptive.
I use the following script to create a graph that filters the EAP traffic
and forwards directly from the first
On 29/12/17 10:52 am, John Lyon wrote:
It works!!! In virtual machine land at least, it works! It will be
interesting to see what happens when the rubber meets the road and I
actually test it "in the field."
The issue was a missing single line that was not obvious from the
man pages:
On 29/12/17 10:52 am, John Lyon wrote:
It works!!! In virtual machine land at least, it works! It will be
interesting to see what happens when the rubber meets the road and I
actually test it "in the field."
The issue was a missing single line that was not obvious from the
man pages:
It works!!! In virtual machine land at least, it works! It will be
interesting to see what happens when the rubber meets the road and I
actually test it "in the field."
The issue was a missing single line that was not obvious from the man pages:
sudo ngctl connect eapfilter: ix1: eapout low
On 28/12/17 9:59 pm, Julian Elischer wrote:
On 28/12/17 1:37 am, John Lyon wrote:
Julian,
Unfortunately, this issue remains unresolved. I would like to
think that this is just a PEBKAC issue, but I have tried every
permutation of escape characters in case it's an issue with my
syntax and I
19 matches
Mail list logo
