[SOLVED] Changed NIC, changed settings, now I can only ping the internet?

D

DR4GON

Member
Sep 7, 2021
40
0
11
36
TL;DR I can ping 1.1.1.1, but I cannot ping the router on the same network, nor access the GUI from another computer.

I’ve changed NIC’s before, when I swapped motherboards, so I have solved this issue before, but I’m completely stumped with how my setup is currently broken. I know there is an easy solution, I just can’t figure it out.

I can ping the internet:
Code: 
# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=6.18 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=60 time=8.98 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=60 time=5.98 ms
--- 1.1.1.1 ping statistics ---
3 packets transmitted, 3 recieved, 0% packet loss, time 5ms
rtt min/avg/max/ndev = 5.979/7.043/8.975/1.368 ms

I can ping itself:
Code: 
# ping 192.168.100.253
PING 192.168.100.253 (192.168.100.253) 56(84) bytes of data.
64 bytes from 192.168.100.253: icmp_seq=1 ttl=64 time=0.038 m
64 bytes from 192.168.100.253: icmp_seq=2 ttl=64 time=0.026 m
64 bytes from 192.168.100.253: icmp_seq=3 ttl=64 time=0.028 m
--- 192.168.100.253 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 32ms
rtt min/avg/max/mdev 0.026/0.030/0.038/0.008 ms

But I can’t ping the router:
Code: 
# ping 192.160.100.254
PING 192.168.100.254 (192.168.100.254) 56(84) bytes of data.
From 192.168.100.253 icmp_seq=1 Destination Host Unreachable
From 192.168.100.253 icmp_seq=2 Destination Host Unreachable
From 192.168.100.253 icmp_seq=3 Destination Host Unreachable
--- 192.168.100.254 ping statistics ---
3 packets transmitted, 0 received, 3 errors, 100% packet loss, time 58ms
pipe 4

I installed ethtools so I could get more info on the NIC. It says Fiber instead of Twisted Pair, but it is a SAS to RJ45, and has worked fine for the past 2 months in my Ubuntu PC. Plug and play. It’s using a nice new Cat6e cable that is allowing internet access, but not LAN access, and the cable works fine plugged into my other 10gbe devices.
Code: 
ethtool enp9s0
Settings for enp9s0:
Supported ports: [ FIBRE ]
Supported link modes: 10000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: 10000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000014 (20)
link ifdown
Link detected: yes

Code: 
nano /etc/network/interfaces
auto lo
iface lo inet loopback
iface enp2s0 inet manual
iface enp3s0 inet manual
iface enp9s0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.100.253/24
bridge-ports enp2s0
bridge-stp off
bridge-fd 0

auto vmbr1
iface vmbr1 inet static
address 192.168.100.253/24
bridge-ports enp3s0
bridge-stp off
bridge-fd 0

auto vmbr2
iface vmbr2 inet static
address 192.168.100.253/24
gateway 192.168.100.254
bridge-ports enp9s0
bridge-stp off
bridge-fd 0

Any ideas? I’ve rebooted 3 times now..
 
Is there a reason why you are using the same IP for all 3 interfaces? I think this is where your problem is buried.
 
If I don’t, the internet drops out all together. Only enp9s0 is connected via a cable, and before adding enp9s0, enp2s0 and enp3s0 had the same IP, but only enp2s0 was connected via a cable. Edit: and it worked fine.

I can delete them, and loose internet access, but now I have no lan or wlan access, so what would be the next step?
 
So enp9s0 should be what is providing the internet access, right? The other two are not connected at all? What is the output of your ip a? Did you reload networking after changing the configuration? (systemctl reload networking)
 
Code: 
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master vmbr1 state DOWN group default qlen 1000
    link/ether ::::8b:b4 brd ::::ff:ff
3: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master vmbr0 state DOWN group default qlen 1000
    link/ether ::::8a:89 brd ::::ff:ff
4: enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr2 state UP group default qlen 1000
    link/ether ::::b2:f2 brd ::::ff:ff
5: vmbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether ::::8a:89 brd ::::ff:ff
    inet 192.168.100.253/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 ::::fe48:8a89/64 scope link 
       valid_lft forever preferred_lft forever
6: vmbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether ::::8b:b4 brd ::::ff:ff
    inet 192.168.100.253/24 scope global vmbr1
       valid_lft forever preferred_lft forever
7: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether ::::b2:f2 brd ::::ff:ff
    inet 192.168.100.253/24 scope global vmbr2
       valid_lft forever preferred_lft forever
    inet6 ::::fe55:b2f2/64 scope link 
       valid_lft forever preferred_lft forever

Hopfully this is helpful, it took litterally forever to type out, because I can't copy paste anything because no network access... zzz

shanreich said:
Did you reload networking after changing the configuration? (systemctl reload networking)
Click to expand...
Yes, and when that failled to work, I rebooted. I assume there is just a setting somewhere that I haven't changed, but I didn't have this issue last time. All I had to do was move IP's around and everything worked first try.
 
Code: 
# systemctl status networking
● networking.service - Network initialization
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: active (exited) since Tue 2022-10-18 16:57:53 AEDT; 6h ago
     Docs: man:interfaces(5)
           man:ifup(8)
           man:ifdown(8)
  Process: 3515 ExecStart=/usr/share/ifupdown2/sbin/start-networking start (code=exited, status=0/SUCCESS)
  Process: 819846 ExecReload=/usr/share/ifupdown2/sbin/start-networking reload (code=exited, status=0/SUCCESS)
 Main PID: 3515 (code=exited, status=0/SUCCESS)
 
3000ms response is not normal and indicates an issue with your router/network.

As a way to reduce complexity - remove/comment/dont specify "auto" on vmbr0 and vmbr1. Restart network or reboot your host. Confirm that the interfaces that are down are not in your routing table or other IP related outputs.

As an experiment, try to ping with large timeout: ping -W 45 192.168.100.254

If the long timeout ping works - the issue is your router, likely. As to access from "other computer" - is it on the same network? What are the IP/routing/ping/traceroute/etc results from that computer, if its on the same network?

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
bbgeek17 said:
As a way to reduce complexity - remove/comment/dont specify "auto" on vmbr0 and vmbr1. Restart network or reboot your host. Confirm that the interfaces that are down are not in your routing table or other IP related outputs.
Click to expand...
Turned off auto start, on vmbr0 and vmbr1. Rebooted router and server.
bbgeek17 said:
As an experiment, try to ping with large timeout: ping -W 45 192.168.100.254
Click to expand...
Code: 
# ping -W 45 192.168.100.254
PING 192.168.100.254 (192.168.100.254) 56(84) bytes of data.
64 bytes from 192.168.100.254: icmp_seq=1 ttl=64 time=0.383 ms
64 bytes from 192.168.100.254: icmp_seq=2 ttl=64 time=0.403 ms
64 bytes from 192.168.100.254: icmp_seq=3 ttl=64 time=0.352 ms
64 bytes from 192.168.100.254: icmp_seq=4 ttl=64 time=0.361 ms
^C
--- 192.168.100.254 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 75ms
rtt min/avg/max/mdev = 0.352/0.374/0.403/0.030 ms

Interesting...
Code: 
# ping 192.168.100.254
PING 192.168.100.254 (192.168.100.254) 56(84) bytes of data.
64 bytes from 192.168.100.254: icmp_seq=1 ttl=64 time=0.387 ms
64 bytes from 192.168.100.254: icmp_seq=2 ttl=64 time=0.490 ms
64 bytes from 192.168.100.254: icmp_seq=3 ttl=64 time=0.357 ms
64 bytes from 192.168.100.254: icmp_seq=4 ttl=64 time=0.445 ms
^C
--- 192.168.100.254 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 53ms
rtt min/avg/max/mdev = 0.357/0.419/0.490/0.057 ms

Wait, what?
Code: 
# ping 192.168.100.248
PING 192.168.100.248 (192.168.100.248) 56(84) bytes of data.
64 bytes from 192.168.100.248: icmp_seq=1 ttl=128 time=0.205 ms
64 bytes from 192.168.100.248: icmp_seq=2 ttl=128 time=0.233 ms
64 bytes from 192.168.100.248: icmp_seq=3 ttl=128 time=0.199 ms
64 bytes from 192.168.100.248: icmp_seq=4 ttl=128 time=0.227 ms
^C
--- 192.168.100.248 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 68ms
rtt min/avg/max/mdev = 0.199/0.216/0.233/0.014 ms

So it turns out it just works now... The fuck? I've rebooted the server 5 times in total, and the router 3 times, and all I had to do was turn Autostart off on 2 of the NICs? I hate everything.
bbgeek17 said:
As to access from "other computer" - is it on the same network? What are the IP/routing/ping/traceroute/etc results from that computer, if its on the same network?
Click to expand...
There are a few computers on the network, but I was specifically unable to access https://192.168.100.253:8006/ from 3 PC's and an iPad, 192.168.100.148, 192.168.100.246, 192.168.100.248, 192.168.100.250. But now everything just works... So thanks for the help. I'll keep these troubleshooting steps for the next time I load up a server, lol.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back