Tuesday, January 24, 2023

Re: OpenBSD routing - detects WAN IP links back to firewall?

> So yesterday I was working on my BSD router, I realised that if I nmap'ed my
> external IP from my internal IP, it would treat it still as an internal
> request. ^^^^^^^^^^^^

The router treat it like an internal request because it IS an internal
request.



> with traditional ISP routers, if you send a packet to their WAN address, you
> would see the following:
> My laptop (192.168.0.104) --> ISP router (192.168.0.1) - NAT'd -> ISP -->
> ISP router

I don't know what you mean with "traditional router".
Maybe you mean the plastic boxes given away from ISP's with modem, VOIP,
WLAN and more. If such a device routes packets like you describe above
then it is doing it's job wrong.

Maybe such behavior you described feels more like something that works
on layer 2 ...?
I am not sure about that layer thing - maybe someone can shed some light
on this. There are many experienced IT professionals on this list.



> Now when I was setting up my OpenBSD router, I believe the following was
> occurring (hence why the nmap preserved permissions set for internal IPs and
> not external).
> My laptop (192.168.2.3) --> OpenBSD Router

Thats expected behaviour.



> But despite using the public IP address of the BSD router, it still seemed
> to detect that the packet was for it, and I am not too sure why?

This is because the packet IS for it.
What would you do if I give you a letter which is adressed to you? Would
you give it to another person so that this person can relay it again?

Maybe I don't understand the real question.
But please feel free to explain.



> If anyone could explain to me their thoughts about this, or how it works, it
> would be appreciated.

Your Website says that you are interested in networking stuff but whats
the real question here? You want to hear someone thoughts? About what
exactly?

No comments:

Post a Comment