| 1 |
server: |
| 2 |
|
| 3 |
# ip route s |
| 4 |
default via 10.96.25.129 dev br0 |
| 5 |
10.96.25.128/25 dev br0 proto kernel scope link src 10.96.25.131 |
| 6 |
192.168.1.0/24 dev eno2 proto kernel scope link src 192.168.1.201 |
| 7 |
|
| 8 |
# !tra |
| 9 |
traceroute 172.32.99.12 |
| 10 |
traceroute to 172.32.99.12 (172.32.99.12), 30 hops max, 60 byte packets |
| 11 |
1 ipfire (10.96.25.129) 0.410 ms 1.213 ms 1.302 ms |
| 12 |
2 10.96.25.2 (10.96.25.2) 3.853 ms 3.835 ms 3.825 ms |
| 13 |
|
| 14 |
^C |
| 15 |
|
| 16 |
on the router "ipfire" (which is 10.96.25.129 on its LAN-side) |
| 17 |
|
| 18 |
# ip r s |
| 19 |
default via 10.96.25.1 dev blue0 |
| 20 |
|
| 21 |
no specific routes on there |
| 22 |
|
| 23 |
The route should go via 10.96.25.1 for targets in 172.32.99.0/24 as |
| 24 |
well ... |
| 25 |
|
| 26 |
I don't get where it gets 10.96.25.2 from *scratch* |
| 27 |
|
| 28 |
This routing issue might be the problem with my libvirt-connections (see |
| 29 |
other current thread). |
| 30 |
|
| 31 |
Even when I do |
| 32 |
|
| 33 |
# ip route add 172.32.99.12/32 via 10.96.25.1 |
| 34 |
|
| 35 |
on the router (explicit route for my desktop IP) the traceroute still shows: |
| 36 |
|
| 37 |
# traceroute 172.32.99.12 |
| 38 |
traceroute to 172.32.99.12 (172.32.99.12), 30 hops max, 60 byte packets |
| 39 |
1 ipfire.mlp-ag.com (10.96.25.129) 0.294 ms 0.270 ms 0.258 ms |
| 40 |
2 10.96.25.2 (10.96.25.2) 0.569 ms 0.746 ms 0.987 ms^C |
| 41 |
|
| 42 |
Any hints on this? |
| 43 |
I need a vacation, btw ;-) |
| 44 |
|
| 45 |
And the best: I do this via ssh, so I am already connected ... which |
| 46 |
means I get packages back ... |
| 47 |
|
| 48 |
S |
Archives