Welcome Guest. Please Login or Register  
Client Area  |  Softaculous Cloud  |  Calendar  |  Quick Links  |  
   


You are here: Index > Virtualizor - Virtual Server Control Panel > General Support > Topic : Networking Error



Threaded Mode | Print  

 Networking Error (3 Replies, Read 3973 times)
SpaceSrv
Posted on # June 7, 2021, 1:41 am
Group: Member
Post Group: Newbie
Posts: 2
Status:
I have setup multiple Virtualizor servers in the past with no issue, but now I am getting this when creating a vps: "The viifbr0 is not started. Please run service virtnetwork start"

Here is my netplan file bridge:

  bridges:
    viirbr0:
      interfaces: [ enp1s0f0 ]
      addresses:
      - 5.39.223.0/24
      gateway4: 5.39.223.1
      nameservers:
        addresses:
        - 8.8.8.8
        - 8.8.4.4
  version: 2

Here is my ip link show results:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master viirbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 0c:c4:7a:15:f5:ce brd ff:ff:ff:ff:ff:ff
3: enp1s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 0c:c4:7a:15:f5:cf brd ff:ff:ff:ff:ff:ff
5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
6: viirbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 0c:c4:7a:15:f5:ce brd ff:ff:ff:ff:ff:ff

I have my network interface set to enp1s0f1 within virtualizor master settings.

Any ideas to what could be the problem?
IP: --   

Networking Error
SpaceSrv
Posted on # June 7, 2021, 1:55 am | Post: 1
Group: Member
Post Group: Newbie
Posts: 2
Status:
I have just updated my address to match my interfaces and here is ifconfig results:

(I am still getting the error that viibr0 is not up, which is strange because its showing its up.

root@unknown35030:~# ifconfig
enp1s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 5.39.223.26  netmask 255.255.255.128  broadcast 5.39.223.127
        ether 0c:c4:7a:15:f5:ce  txqueuelen 1000  (Ethernet)
        RX packets 195875  bytes 17271384 (17.2 MB)
        RX errors 0  dropped 419  overruns 0  frame 0
        TX packets 16547  bytes 7117317 (7.1 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0xe0000000-e007ffff 

enp1s0f1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 0c:c4:7a:15:f5:cf  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0xe0080000-e00fffff 

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 138  bytes 11439 (11.4 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 138  bytes 11439 (11.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

viirbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 5.39.223.26  netmask 255.255.255.128  broadcast 5.39.223.127
        inet6 fe80::f49d:4fff:fe1e:2f8b  prefixlen 64  scopeid 0x20<link>
        ether 0c:c4:7a:15:f5:ce  txqueuelen 1000  (Ethernet)
        RX packets 145876  bytes 10298795 (10.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 33  bytes 3294 (3.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 138  bytes 11439 (11.4 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 138  bytes 11439 (11.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

viirbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 5.39.223.26  netmask 255.255.255.128  broadcast 5.39.223.127
        inet6 fe80::f49d:4fff:fe1e:2f8b  prefixlen 64  scopeid 0x20<link>
        ether 0c:c4:7a:15:f5:ce  txqueuelen 1000  (Ethernet)
        RX packets 145876  bytes 10298795 (10.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 33  bytes 3294 (3.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
IP: --   

Networking Error
wolke
Posted on # June 7, 2021, 7:27 am | Post: 2
Group: NOC
Post Group: Elite Member
Posts: 437
Status:
You should not create the bridge manually, let virtualizor do this job automatically.
IP: --   

Networking Error
jevingala
Posted on # June 8, 2021, 7:33 am | Post: 3
Group: Virtualizor Team
Post Group: Super Member
Posts: 742
Status:
Hi,


Does the bridge shows up under brctl show command output ?


-----------------------
Regards,
Virtualizor Team.
http://virtualizor.com/
IP: --   

« Previous    Next »

Threaded Mode | Print  



Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is April 18, 2024, 12:42 pm.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 11  |  Page Created In:0.033