Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Markus Wernig
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

Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Brian Brombacher
> 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

Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Brian Brombacher
>> 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

Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Brian Brombacher
> 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

Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Ernest Stewart
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

Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Theo de Raadt
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?

Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Ernest Stewart
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.

Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Ernest Stewart
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=

Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Brian Brombacher
> 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

Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Janne Johansson
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

Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Janne Johansson
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

Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Ernest Stewart
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.

Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Rafael Possamai
>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

Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Ernest Stewart
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

Re: Routing and forwarding: directly connected computers

2020-09-03 Thread Janne Johansson
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