Just figured out how to get OPNsense on a Lenovo, why do you need "Lenovo Fix"?!? Sorry, I have to name and shame.
Anyway, I can reach it, and it's handing out IP to other systems on the network (DNS with some static).
My ISP can see it through the modem.
But any attempt to get on the web times out.
I even did a reset just incase. Did not change any settings, just [Next] on all of them
# /sbin/ping -4 -c '3' '8.8.8.8'
PING 8.8.8.8 (8.8.8.8): 56 data bytes
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
WAN is on igb1, the MoBo NIC This was wrong, it should be ro0, see FIX1
I don't know what other info you need
EDIT: System: Gateways: Single only has IPV6. I tried copying that and putting IPV4, but can't get it to run
EDIT2: System: Routes: Status
ipv6 $NUMBER link#2 U NaN 1500 igb1 wan
There's no IPV4 equivalent for WAN.
FIX1: When I System: Configuration: Defaults it sets WAN as igb1, not as I set it ro0. Still not fixed, and can't ping, but getting an IP now.
I'm looking at Firewall: NAT right now. I don't know how it should look... how can I tell if it's wrong???
Firewall: NAT: Port Forward
The only thing I'm seeing is the Anti-Lock-Out, nothing else.
There's nothing saying WAN<-->LAN, or WAN-->LAN or WAN<--LAN
Also, nothing in One-to-One, Outbound has two Loopback, NTP6 is blank
interfaces > overview.
are the status plugs green, as in showing corrected?
system > settings > general > plugin a dns server like 9.9.9.9 and see if it helps
Can you ping anything (e.g. 8.8.8.8) from the firewall itself?
If that output in your first post is from the OPNsense and not from a client system behind it, then your WAN link is not configured correctly. I suggest to contact your ISP again if that is the case.
Before the OPNsense can "ping 8.8.8.8" you don't need to care about anything else (like DNS, NAT, ...) - that one MUST work first.
Try ping from the firewall itself ping 1.1.1.1 and ping www.google.com
Quote from: DEC670airp414user on December 13, 2024, 11:47:20 AMinterfaces > overview.
are the status plugs green, as in showing corrected?
system > settings > general > plugin a dns server like 9.9.9.9 and see if it helps
Ok, this is going to be long...
9.9.9.9 did not help
I don't see any color in
interfaces > overviewWhat I do see:
WAN Status upDHCP
DHCPv4 up DHCPv6 up
MAC address d4:xx:xx:xx:xx:d5 - Micro-Star Int'l Co, Ltd
MTU 1500
IPv4 address 205.xx.xx.xxx/22
IPv4 gateway : 205.xxx.xxx.1
IPv6 link-local fe80::xxxx:xxxx:xxxx:5ad5/64
IPv6 address
DNS servers 8.8.8.8 8.8.4.4
Media 1000baseT <full-duplex>
In/out packets 8377 / 83 (614 KB / 9 KB)
In/out packets (pass) 0 / 83 (0 bytes / 9 KB)
In/out packets (block) 628547 / 0 (8 KB / 0 bytes)
In/out errors 0 / 0
Collisions 0WAN Status up
DHCP
DHCPv4 up DHCPv6 up
MAC address d4:xx:xx:xx:xx:d5 - Micro-Star Int'l Co, Ltd
MTU 1500
IPv4 address 205.xx.xx.xxx/22
IPv4 gateway : 205.xxx.xxx.1
IPv6 link-local fe80::xxxx:xxxx:xxxx:5ad5/64
IPv6 address
DNS servers 8.8.8.8 8.8.4.4
Media 1000baseT <full-duplex>
In/out packets 8377 / 83 (614 KB / 9 KB)
In/out packets (pass) 0 / 83 (0 bytes / 9 KB)
In/out packets (block) 628547 / 0 (8 KB / 0 bytes)
In/out errors 0 / 0
Collisions 0
====================================================================================
LAN Status upMAC address 00:xx:xx:xx:xx:88 - Intel Corporate
MTU 1500
IPv4 address 192.168.1.1/24
IPv6 address
Media 1000baseT <full-duplex>
In/out packets 27113 / 31115 (1.88 MB / 12.91 MB)
In/out packets (pass) 27113 / 31115 (1.88 MB / 12.91 MB)
In/out packets (block) 0 / 0 (0 bytes / 0 bytes)
In/out errors 0 / 0
Collisions 0
Interrupts
irq device total rate
irq32 igb0:rxq0 46726 5
irq33 igb0:rxq 117839 2
irq34 igb0:aq 12 0
Quote from: Patrick M. Hausen on December 13, 2024, 11:50:41 AMCan you ping anything (e.g. 8.8.8.8) from the firewall itself?
If that output in your first post is from the OPNsense and not from a client system behind it, then your WAN link is not configured correctly. I suggest to contact your ISP again if that is the case.
Before the OPNsense can "ping 8.8.8.8" you don't need to care about anything else (like DNS, NAT, ...) - that one MUST work first.
Quote from: peterwkc on December 13, 2024, 02:09:12 PMTry ping from the firewall itself ping 1.1.1.1 and ping www.google.com
Yes, the ping is from inside OPNsense. I got the right port "ro0", see FIX1 in OP.
Quote from: imWACCo on December 13, 2024, 03:28:29 PMYes, the ping is from inside OPNsense. I got the right port "ro0", see FIX1 in OP.
But does the ping work after the fix? If it doesn't you need to get your WAN connection working above anything else.
Quote from: Patrick M. Hausen on December 13, 2024, 03:41:38 PMBut does the ping work after the fix? If it doesn't you need to get your WAN connection working above anything else.
No, still can't Ping. Any ideas on how to do that? I'm a hardware guy, networking is out of my skillset.
If you have any links I should be reading....
Quote from: imWACCo on December 13, 2024, 04:55:51 PMQuote from: Patrick M. Hausen on December 13, 2024, 03:41:38 PMBut does the ping work after the fix? If it doesn't you need to get your WAN connection working above anything else.
No, still can't Ping. Any ideas on how to do that? I'm a hardware guy, networking is out of my skillset.
If you have any links I should be reading....
Configure the WAN interface matching the requirements of your ISP. They should be able to tell you how. There are at least three completely different ways to do that and all of them require information from your ISP.
- DHCP (ok, that one you can just try if it works - if it doesn't, your ISP does not use DHCP)
- static (in that case you need IP address, subnet mask, default gateway from your ISP)
- PPPoE (you need at least a user name and a password from your ISP)
All of these can be combined with a VLAN or not in which case you need the information if a VLAN is used at all and if yes, which one precisely.
None of this can be inferred out of thin air via this forum. You need this information up front to connect
any router to your ISP line. Unless it comes preconfigured by your ISP ...
It's fixed, had to power cycle the modem. I'm an old vet, had to ask a friends kid to come over and climb under the desk.