How do I set the IP address on the lan

Started by ajoeiam, September 04, 2023, 10:57:18 PM

Previous topic - Next topic
Greetings

Installed opnsense w/o configuration.
Boot up machine.
Log in as root.
LAN (on ue0) is listed as 0.0.0.0/8

In the console when I use option 2 (set interface IP address)

(I see)
Enter the new LAN IPv4 address. Press<ENTER> for none:
I can enter my desired address
192.168.xx.xx but if I then hit enter I'm in a loop (if I press 'enter' I'm saying I don't want
an ip address) so what do I enter at that point so complete the configuration?

Please advise

TIA

that should be how. Can you check you are entering a valid ip, for instance 192.168.10.1
Third octet is less important but creates the network range so in that case all the LAN clients would be 192.168.10.x/24 range by default. The last one is what completes the network address for the interface, 1 is customary for the interfaces i.e the first host address.

Hmmmmmmmmm - - - - after I enter the address what key do I hit?

Quote from: ajoeiam on September 04, 2023, 11:21:23 PM
Hmmmmmmmmm - - - - after I enter the address what key do I hit?

ok this time I managed to plow through that.

I think is was entering 01 as the final quad and that isn't allowed I guess.

Thanks for the help!

Check out Patrick's pointers in this thread.

https://forum.opnsense.org/index.php?topic=35764.0


There should be no need for you to manually set up the LAN --- you might be doing something wrong there and end up with duplicate IPs on the FW NICs if you don't identify the one that already responds to pings on 192.168.1.1

Quote from: newsense on September 04, 2023, 11:55:06 PM
Check out Patrick's pointers in this thread.

https://forum.opnsense.org/index.php?topic=35764.0


There should be no need for you to manually set up the LAN --- you might be doing something wrong there and end up with duplicate IPs on the FW NICs if you don't identify the one that already responds to pings on 192.168.1.1


I'm not sure what's going on.
followed the above listed thread for order of plug in etc
booting opnsense m/c  and ue0 (lan) is listed as 192.168.1.1/24
boot laptop and set using ip tools so its ip address is 192.168.1.100

I can ping 192.168.1.100 from 192.168.1.1
I can NOT ping 192.168.1.1 from 192.168.1.100

( from 192.168.1.100 icmp_seq=1 Destination Host Unreachable )

I've tried setting the ip address down and up (on the laptop)
still only one way connection
what do I do now?

(I've only tried this complete system some 4 or 5 times already - - - just not sure how to fix the problem - - - whatever it is!!!)

Please advise

September 07, 2023, 10:33:50 AM #6 Last Edit: September 07, 2023, 05:38:44 PM by meyergru
If the laptop cannot be pinged from OpnSense, it is not the firewall of OpnSense that is blocking it.

There are lots of possibilities why the laptop does not respond to pings, among which these come to mind:

1. You set the network mask of your laptop incorrectly, like just 192.168.1.100, which corresponds to 192.168.1.100/32, it should be 192.168.1.100/24.

2. If it is a Windows laptop with its network type set incorrectly, thus pings are not allowed (https://bitlaunch.io/blog/how-to-make-windows-10-pingable/). BTW: Even if the type is correct, you can only ping the laptop from its own subnet, unless you modify the source network in the firewall rules.
Intel N100, 4 x I226-V, 16 GByte, 256 GByte NVME, ZTE F6005

1100 down / 770 up, Bufferbloat A

Quote from: meyergru on September 07, 2023, 10:33:50 AM
If the laptop cannot bin pinged from OpnSense, it is not the firewall of OpnSense that is blocking it.

There are lots of possibilities why the laptop does not respond to pings, among which these come to mind:

1. You set the network mask of your laptop incorrectly, like just 192.168.1.100, which corresponds to 192.168.1.100/32, it should be 192.168.1.100/24.

2. It is a Windows laptop with its network type set incorrectly, thus pings are not allowed (https://bitlaunch.io/blog/how-to-make-windows-10-pingable/). BTW: Even if the type is correct, you can only ping the laptop from its own subnet, unless you modify the source network in the firewall rules.

Seems like it was #1 that was the issue.
(Its a Devuan daedalus laptop so I don't think it could be #2)

Further fun:
started laptop
made sure ip address was set to 192.168.1.100/24
started opnsense box
logged in
plugged ion net connection from opnsense box to laptop
could ping in both directions (wonderful)
go to browser and ask for http:192.168.1.1 (opnsense box)
notice on monitor for opnsense box that
ue0: link state changed to down
(log in screen shows up on browser (on laptop) but its not connected)
can no longer ping either way
after checking ping from router to laptop (using #8 from the console)
then returning to the console - - - - no lan address is listed at the console
(sorta to be expected as ue0 is down)

so what to I try next?

TIA