Softaculous

Topic : VPS network problem

Posted By: MehdiK120 on April 16, 2024, 3:19 pm

Hello
I installed virtualizor with xen on ubuntu 20.04 server
Currently my main server has two IPs, by default the first IP is installed on the main server.

I use the second IP to create vps
vps is built without problem but its network is not working
With the second IP, I can't enter the built vps

Which of the interfaces should I add the second IP to in the main server?
I added the second ip in the ip pool but on the main server I don't know how to configure it for the vps to work properly

Posted By: rohitbind on April 17, 2024, 6:00 am | Post: 1

Hi Sir,

Firstly, you need to remove the ip from the server then add it to the ip pool then try to make vps with it and check.

Please let us know,

Posted By: interpretshot on April 25, 2024, 4:47 am | Post: 2

Quote From : MehdiK120 April 16, 2024, 3:19 pm

Hello
I installed virtualizor with xen on ubuntu 20.04 server
Currently my main server has two IPs, by default the first IP is installed on the main server.
happy wheels
I use the second IP to create vps
vps is built without problem but its network is not working
With the second IP, I can't enter the built vps

Which of the interfaces should I add the second IP to in the main server?
I added the second ip in the ip pool but on the main server I don't know how to configure it for the vps to work properly

When you add the second IP to the server, I recommend you reset the ip from the server and add it again later with the vps.

Posted By: netPika on May 15, 2024, 5:59 am | Post: 3

Maybe you can help me with something I'm not able to see...
My situation is the next; For days I have not been able to get the vps that is created by virtualizor onto the internet, within an Alma Linux 8.9. This Alma Linux is installed on my physical PC, Windows 2022, connected to a router with lan ip 192.168.0.100 gate way 192.168.0.1 and ip "internet" because it would be a subnet, the network 192.168.1.200 with gateway 192.168.1.1 ( the mother of CLARO INTERNET WITH 300 mbps and WAN ip 181.168.242.8. I hope my query is understood; I cannot provide internet to my vps, can someone give me 3 weeks ago?

Thank you!

Posted By: jevingala on May 17, 2024, 6:33 am | Post: 4

Hi,

Virtualizor will not handle the routing part, it will only assign the IP to VPS.
Is viifbr0 created ?
Can you share output of ' brctl show ' command ?
Also can you check in Windows VPS if it has received IP properly ?

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

Posted By: netPika on May 17, 2024, 8:38 pm | Post: 5

Quote From : jevingala May 17, 2024, 6:33 am

Hi there! Thanks for your answer!

Attached some pics.

The int lan is just for trying things.
I don't think I need explicit configuration details unless you want to give them to me. What I think I need is to know how to follow or what type of protocol to use so that my internal vps receive WAN.

I think my windows configuration is fine, my virtualizor vps receives internet from my brigde windows

Posted By: netPika on May 17, 2024, 8:40 pm | Post: 6

i cant add pics.

root@master ~]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 viifbr0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 viifbr0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 intbr0
[root@master ~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default _gateway 0.0.0.0 UG 0 0 0 viifbr0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 viifbr0
192.168.1.0 0.0.0.0 255.255.255.0 U 425 0 0 intbr0

----------------------------------------------------------------------------------------------

[root@master ~]# brctl show
bridge name bridge id STP enabled interfaces
intbr0 8000.fe163ef92213 yes vinfv1001
viifbr0 8000.00155d00b50f no eth0
viifv1001
[root@master ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::215:5dff:fe00:b50f prefixlen 64 scopeid 0x20<link>
ether 00:15:5d:00:b5:0f txqueuelen 1000 (Ethernet)
RX packets 112244 bytes 23312175 (22.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 67767 bytes 10633258 (10.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

intbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::98df:1fb7:4605:5d99 prefixlen 64 scopeid 0x20<link>
ether fe:16:3e:f9:22:13 txqueuelen 1000 (Ethernet)
RX packets 22 bytes 1456 (1.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 87 bytes 5606 (5.4 KiB)
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 46 bytes 5173 (5.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 46 bytes 5173 (5.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

viifbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.135 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::7007:45ff:fe71:6baf prefixlen 64 scopeid 0x20<link>
ether 00:15:5d:00:b5:0f txqueuelen 1000 (Ethernet)
RX packets 89531 bytes 12618191 (12.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 65956 bytes 10574308 (10.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

viifv1001: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether fe:16:3e:bf:c6:c9 txqueuelen 1000 (Ethernet)
RX packets 2375 bytes 123294 (120.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 17895 bytes 1626395 (1.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vinfv1001: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fc16:3eff:fef9:2213 prefixlen 64 scopeid 0x20<link>
ether fe:16:3e:f9:22:13 txqueuelen 1000 (Ethernet)
RX packets 36 bytes 2672 (2.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 28115 bytes 1463444 (1.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Posted By: netPika on Today at 12:52 am | Post: 7

[root@master ~]# brctl show
bridge name bridge id STP enabled interfaces
viifbr0 8000.00155d00b50f no eth0

[root@master ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.135 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::215:5dff:fe00:b50f prefixlen 64 scopeid 0x20<link>
ether 00:15:5d:00:b5:0f txqueuelen 1000 (Ethernet)
RX packets 2924 bytes 889038 (868.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2675 bytes 4187618 (3.9 MiB)
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 30 bytes 7509 (7.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 30 bytes 7509 (7.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

viifbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.135 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::b7:40ff:fe49:bf18 prefixlen 64 scopeid 0x20<link>
ether 00:15:5d:00:b5:0f txqueuelen 1000 (Ethernet)
RX packets 2959 bytes 768087 (750.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2573 bytes 4191456 (3.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

viifv1001: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fc16:3eff:feba:7370 prefixlen 64 scopeid 0x20<link>
ether fe:16:3e:ba:73:70 txqueuelen 1000 (Ethernet)
RX packets 282 bytes 21930 (21.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 233 bytes 24322 (23.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[root@master ~]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 viifbr0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 viifbr0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

[root@master ~]# systemctl status virtnetwork
● virtnetwork.service - Virtualizor Network Service
Loaded: loaded (/usr/local/virtualizor/virtnetwork.service; enabled; vendor preset: disabled)
Active: active (exited) since Fri 2024-05-17 20:39:50 EDT; 7min ago
Process: 940 ExecStart=/usr/local/virtualizor/bridge start (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 35132)
Memory: 0B
CGroup: /system.slice/virtnetwork.service

may 17 20:39:38 master.cloudsting.ar systemd[1]: Starting Virtualizor Network Service...
may 17 20:39:39 master.cloudsting.ar bridge[943]: Bringing up viifbr0 - OK
may 17 20:39:49 master.cloudsting.ar bridge[943]: Waiting for 10 seconds...1...2...3...4...5...6...7>
may 17 20:39:49 master.cloudsting.ar bridge[943]: Internet connectivity check successful viifbr0 - OK
may 17 20:39:50 master.cloudsting.ar systemd[1]: Started Virtualizor Network Service.
lines 1-13/13 (END)

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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master viifbr0 state UP group default qlen 1000
link/ether 00:15:5d:00:b5:0f brd ff:ff:ff:ff:ff:ff
inet6 fe80::215:5dff:fe00:b50f/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: viifbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:15:5d:00:b5:0f brd ff:ff:ff:ff:ff:ff
inet 192.168.0.135/24 brd 192.168.0.255 scope global viifbr0
valid_lft forever preferred_lft forever
inet6 fe80::8851:85ff:fe27:c20b/64 scope link
valid_lft forever preferred_lft forever

---------------------------------------------------------------------------------------------

ssh to vps but without wan just lan

----------------------------------->

root@192.168.0.122's password:
Last login: Tue Apr 25 09:29:46 2023
[root@dns1 ~]# ping google.com
ping: google.com: Nombre o servicio desconocido
[root@dns1 ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.122 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::216:3eff:feba:7370 prefixlen 64 scopeid 0x20<link>
ether 00:16:3e:ba:73:70 txqueuelen 1000 (Ethernet)
RX packets 144 bytes 16190 (15.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 163 bytes 13820 (13.4 KiB)
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 76 bytes 7656 (7.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 76 bytes 7656 (7.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[root@dns1 ~]# ip addr
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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:16:3e:ba:73:70 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.122/24 brd 192.168.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::216:3eff:feba:7370/64 scope link
valid_lft forever preferred_lft forever
[root@dns1 ~]#

Posted By: netPika on Today at 12:59 am | Post: 8

SRY! THIS IS THE REAL ACTUAL INFO, SRY I CANT DELETE OR EDIT THE OTHER POSTS, SRY!!!

[root@master ~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default _gateway 0.0.0.0 UG 0 0 0 viifbr0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 viifbr0

[root@master ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::215:5dff:fe00:b50f prefixlen 64 scopeid 0x20<link>
ether 00:15:5d:00:b5:0f txqueuelen 1000 (Ethernet)
RX packets 2300 bytes 640689 (625.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1527 bytes 380852 (371.9 KiB)
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 15 bytes 1653 (1.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 15 bytes 1653 (1.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

viifbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.135 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::8851:85ff:fe27:c20b prefixlen 64 scopeid 0x20<link>
ether 00:15:5d:00:b5:0f txqueuelen 1000 (Ethernet)
RX packets 1898 bytes 450759 (440.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1512 bytes 380454 (371.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

viifv1001: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fc16:3eff:feba:7370 prefixlen 64 scopeid 0x20<link>
ether fe:16:3e:ba:73:70 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1 bytes 110 (110.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[root@master ~]# ip addr
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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master viifbr0 state UP group default qlen 1000
link/ether 00:15:5d:00:b5:0f brd ff:ff:ff:ff:ff:ff
inet6 fe80::215:5dff:fe00:b50f/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: viifbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:15:5d:00:b5:0f brd ff:ff:ff:ff:ff:ff
inet 192.168.0.135/24 brd 192.168.0.255 scope global viifbr0
valid_lft forever preferred_lft forever
inet6 fe80::8851:85ff:fe27:c20b/64 scope link
valid_lft forever preferred_lft forever
4: viifv1001: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master viifbr0 state UNKNOWN group default qlen 1000
link/ether fe:16:3e:ba:73:70 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc16:3eff:feba:7370/64 scope link
valid_lft forever preferred_lft forever

---------------------------------------------------------------------------------------------

ssh to vps but without wan just lan

----------------------------------->

root@192.168.0.122's password:
Last login: Tue Apr 25 09:29:46 2023
[root@dns1 ~]# ping google.com
ping: google.com: Nombre o servicio desconocido
[root@dns1 ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.122 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::216:3eff:feba:7370 prefixlen 64 scopeid 0x20<link>
ether 00:16:3e:ba:73:70 txqueuelen 1000 (Ethernet)
RX packets 144 bytes 16190 (15.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 163 bytes 13820 (13.4 KiB)
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 76 bytes 7656 (7.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 76 bytes 7656 (7.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[root@dns1 ~]# ip addr
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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:16:3e:ba:73:70 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.122/24 brd 192.168.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::216:3eff:feba:7370/64 scope link
valid_lft forever preferred_lft forever
[root@dns1 ~]#

Posted By: netPika on Today at 1:00 am | Post: 9

[root@master ~]# brctl show
bridge name bridge id STP enabled interfaces
viifbr0 8000.00155d00b50f no eth0
viifv1001

[root@master ~]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 viifbr0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 viifbr0

Posted By: jevingala on Today at 7:12 am | Post: 10

Hi,

No need to use 2 different bridges.

Simply use normal IP pool and that will use viifbr0 as bridge for VPS and the NATting/Routing will be done by router.

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