No response == no address 103.163.36.18 at the end, or arp filtering.
Run
monitor traffic interface eth7.538
Is there any traffic ?
I just set the ethernet configuration
nothing else
So itâs impossible for there to be any traffic because i havenât set anything up yet
just connect VLAN and network 103.163.36.18
not yet moved to the next stage
such as routing and nat
Just the interface is already RTO
after replay
just entered traffic
Iâm just connecting the Vyos interface to the network
in this case the interface eth.538 address 103.163.36.19
to be able to connect to the 103.163.36.18 network
103.163.36.18 is not a network address, it is a regular address. You use the /31 prefix, so there is no network or broadcast address. Such addressing is treated as point-to-point. Read RFC3021
Run two ssh sessions to your VyOS.
On first run ping to 103.163.36.18.
On second run monitor traffic interface eth7.538
What you see ?
then what is the correct configuration so that it can connect point to point
from 103.163.36.19
redirected directly to 103.163.36.18
This can be done on a Mikrotik
but the problem is I want to move or replace the system from Mikrotik to Vyos
what form of configuration should I input?
You have correct configuration.
set interfaces ethernet eth7 vif 538 address 103.163.36.19/31
set protocols static route 0.0.0.0/0 next-hop 103.163.36.18
Show interface vlan538-fs configuration (from Mikrotik)
vyos@vyos# set interfaces ethernet eth7 vif 538 address 103.163.36.19/31
[edit]
vyos@vyos# commit
WARNING: could not change âeth7â flow control setting!
[edit]
vyos@vyos# set interface ethernet eth7 disable-flow-control
[edit]
vyos@vyos# commit
[edit]
vyos@vyos# set interfaces ethernet eth7 vif 538 address 103.163.36.19/31
Configuration path: [interfaces ethernet eth7 vif 538 address 103.163.36.19/31] already exists
[edit]
vyos@vyos# set protocols static route 0.0.0.0/0 next-hop 103.163.36.18
[edit]
vyos@vyos# commit
[edit]
vyos@vyos# ping 103.163.36.18
PING 103.163.36.18 (103.163.36.18) 56(84) bytes of data.
From 103.163.36.19 icmp_seq=1 Destination Host Unreachable
From 103.163.36.19 icmp_seq=2 Destination Host Unreachable
From 103.163.36.19 icmp_seq=3 Destination Host Unreachable
From 103.163.36.19 icmp_seq=4 Destination Host Unreachable
From 103.163.36.19 icmp_seq=5 Destination Host Unreachable
From 103.163.36.19 icmp_seq=6 Destination Host Unreachable
^C
â 103.163.36.18 ping statistics â
8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7194ms
pipe 4
[edit]
vyos@vyos#
Answer this: Gateway connected but rto - #24 by pepe
and this: Gateway connected but rto - #28 by pepe
In mikrotik, if using âAddressâ and âNetworkâ, itâs a point to point.
If you want that both devices are within a same network, please, in mikroik remote what is written in âNetworkâ and add appropiate mask in address. Such as 103.163.16.19/30
I only have one device on which device I installed Vyos
they just give it to me or my boss or whoever
to input IP address to device interface 103.163.36.19 without netmask
with network 103.163.36.18
if ping replay then it is connected
if you canât find a way in Vyos
So it is recommended to look for another system
if i donât want to use a mikrotik
it should be like this
then what should I do to be able to reply to 103.163.36.18
on Vyos where there is an IP on the interface 103.163.36.19
as you mean, namely point-to-point
Everything looks good.
Run monitor traffic on interface eth7.538
monitor traffic interface eth7.538
Log in again with a second session to VyOS and ping address 103.163.36.18.
What the âmonitor trafficâ shows ?
where should ido that
i have to run two ssh or what
Yes two ssh sessions.
No ARP response.
How VyOS is connected with network ? To switch ? To the same port as Mikrotik ?
Replace âmonitor trafficâ with:
sudo tcpdump -i eth7 -n -e
Then ping again.
What tcpdump shows ?
1 Like