Den tors 3 sep. 2020 kl 14:55 skrev Ernest Stewart <
erneststewar...@hotmail.com>:
> I was actually wondering about using netmask 0x for the external
> interface. As you noted, they are different networks, I just wanted to be
> able to use any 192.168/16 ip address in the internal network
Den tors 3 sep. 2020 kl 17:01 skrev Ernest Stewart <
erneststewar...@hotmail.com>:
> I forgot to say, in every computer I have /etc/sysctl.conf with
> "net.inet.ip.forwarding=1".
>
> And I insist, what shocks me the most is that tcpdump shows in both
> computers the right icmp packets but ping
I was actually wondering about using netmask 0x for the external
interface. As you noted, they are different networks, I just wanted to be able
to use any 192.168/16 ip address in the internal network and use nat-to and
rdr-to in Computer1 so every packet going to or from the ISP router
I forgot to say, in every computer I have /etc/sysctl.conf with
"net.inet.ip.forwarding=1".
And I insist, what shocks me the most is that tcpdump shows in both computers
the right icmp packets but ping says 100% packets lost.
> On Sep 3, 2020, at 11:02 AM, Ernest Stewart
> wrote:
>
> I forgot to say, in every computer I have /etc/sysctl.conf with
> "net.inet.ip.forwarding=1".
>
> And I insist, what shocks me the most is that tcpdump shows in both computers
> the right icmp packets but ping says 100% packets
On Sep 3, 2020, at 15:07 AM, Brian Brombacher wrote:
"Your setup ... requires pf \rules and additional routing tables to make this
work."
And which pf rules and how to establish those routing tables are exactly what
I'm asking.
But ok, let's say I reassign addresses so Comp1 re1=
>1) Why is this little test not working?
>
>2) How should I configure pf.conf (and maybe rc.conf.local with route
>commands) to allow computers >communicate with each other (including Computer1
>with Computer5, thru Computer2)? In every information I >have found this is
>automatically done with
According to my understanding of the manpages (specifically
httpd.conf(5) and tls_config_set_protocols(3)), setting up TLSv1.3
should be just as easy as adding:
tls {
protocols "TLS_PROTOCOL_TLSv1_3"
}
to the appropriate server in /etc/httpd.conf . But when I do
> On Sep 3, 2020, at 12:38 PM, Brian Brombacher wrote:
>
>
>
On Sep 3, 2020, at 12:15 PM, Ernest Stewart
wrote:
>>> Theo de Raadt wrote:
>>> Oh my. Have you considered hiring a consultant?
>>>
>>> Of course. As you have already noticed, I have no idea about how to do what
>> On Sep 3, 2020, at 12:15 PM, Ernest Stewart
>> wrote:
> Theo de Raadt wrote:
> Oh my. Have you considered hiring a consultant?
>
> Of course. As you have already noticed, I have no idea about how to do what
> I'm trying to do. But a consultant is out of my budget.
>
> Are you guys
Ernest Stewart wrote:
> You guys are focusing on the netmasks. Let's consider my setup again
> BUT with all netmasks at 0x, so all the forwarding and routing
> need to be explicitly configured.
Oh my. Have you considered hiring a consultant?
On 9/3/20 5:41 PM, Ernest Stewart wrote:
> And which pf rules and how to establish those routing tables are exactly what
> I'm asking.
Maybe if you share the output of the ping test from your original mail
we could see what is actually happening.
>From your setup I would assume that the IP
You guys are focusing on the netmasks. Let's consider my setup again BUT with
all netmasks at 0x, so all the forwarding and routing need to be
explicitly configured.
Theo de Raadt wrote:
Oh my. Have you considered hiring a consultant?
Of course. As you have already noticed, I have no idea about how to do what I'm
trying to do. But a consultant is out of my budget.
Are you guys saying all I have to do is the following, and packets will
automatically be
> On Sep 3, 2020, at 11:44 AM, Ernest Stewart
> wrote:
>
> On Sep 3, 2020, at 15:07 AM, Brian Brombacher wrote:
>
> "Your setup ... requires pf \rules and additional routing tables to make this
> work."
>
> And which pf rules and how to establish those routing tables are exactly what
Hi Misc,
I'm getting some error messages on dmesg but couldn't understand what's really
going on.
I have one binary running under OpenBSD 6.7 and it crashes few times in a day.
I see these error messages at dmesg:
pmap_unwire: wiring for pmap 0xfd8782e1b710 va 0xc00032c000 didn't change!
On Thu, September 3, 2020 2:18 pm, Parker Ellertson wrote:
> According to my understanding of the manpages (specifically
> httpd.conf(5) and tls_config_set_protocols(3)), setting up TLSv1.3
> should be just as easy as adding:
>
> tls {
> protocols "TLS_PROTOCOL_TLSv1_3"
>
On Thu, Sep 03, 2020 at 08:39:45PM -0600, Austin Hook wrote:
>
> Can't seem to parse the instructions in
> http://www.openbsd.org/faq/upgrade67.html
>
> for how to re-enable an ordinary non root user of Firefox or mplayer to
> output audio.
>
> mplayer works fine as root, but what command
Can't seem to parse the instructions in
http://www.openbsd.org/faq/upgrade67.html
for how to re-enable an ordinary non root user of Firefox or mplayer to
output audio.
mplayer works fine as root, but what command lines are necessary to allow
a non root user get sound output?
let's username
Den tors 3 sep. 2020 kl 11:39 skrev Ernest Stewart <
erneststewar...@hotmail.com>:
> I have a local network with 5 computers:
>
> computer1)
> /etc/hostname.re0: 192.168.1.10 0xff00
>
Different netmask here?
> /etc/hostname.re1: 192.168.2.11 0x
> /etc/hostname.re2: 192.168.2.12
I have a local network with 5 computers:
computer1)
/etc/hostname.re0: 192.168.1.10 0xff00
/etc/hostname.re1: 192.168.2.11 0x
/etc/hostname.re2: 192.168.2.12 0x
/etc/hostname.re3: 192.168.2.13 0x
/etc/mygate:
192.168.1.1
computer2)
/etc/hostname.re0: 192.168.1.11
On 1.9.2020. 15:22, Stuart Henderson wrote:
> On 2020-09-01, Hrvoje Popovski wrote:
>> Hi all,
>>
>> does anyone use an openconnect server on openbsd and have guidelines on
>> how to configure it? i see that an openconnect server can use radius, so
>> it's interesting to me. Which client do you
22 matches
Mail list logo
