Routing error with new bridge

B

Bluemerlin

New Member
Jun 20, 2011
1
0
1
I think I have a routing problem with a new server I have setup.

It's a hetzer EQ4.

I can connect to the guest. A tracert goes circular.

I'll post the configs.

Host /etc/network/interfaces

Code: 
### Hetzner Online AG - installimage# Loopback device:
auto lo
iface lo inet loopback


# device: eth0
auto  eth0
iface eth0 inet static
  address   46.4.121.187
  broadcast 46.4.121.191
  netmask   255.255.255.224
  gateway   46.4.121.161
  post-up mii-tool -F 100baseTx-FD eth0




auto vmbr0
iface vmbr0 inet static
 address 46.4.121.187
 netmask 255.255.255.255
 broadcast 46.4.121.191
 bridge_ports none
 bridge_stp off
 bridge_fd 0


 up ip route add 46.4.121.162/32 dev vmbr0
 up ip route add 46.4.121.166/32 dev vmbr0
 up ip route add 46.4.121.167/32 dev vmbr0


auto vmbr1
iface vmbr1 inet static
 address  10.10.0.1
 netmask  255.255.255.0
 bridge_ports none
 bridge_stp off
 bridge_fd 0


host route-n

Code: 
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
46.4.121.166    0.0.0.0         255.255.255.255 UH    0      0        0 vmbr0
46.4.121.167    0.0.0.0         255.255.255.255 UH    0      0        0 vmbr0
46.4.121.162    0.0.0.0         255.255.255.255 UH    0      0        0 vmbr0
46.4.121.160    0.0.0.0         255.255.255.224 U     0      0        0 eth0
10.10.0.0       0.0.0.0         255.255.255.0   U     0      0        0 vmbr1
0.0.0.0         46.4.121.161    0.0.0.0         UG    0      0        0 eth0



Guest /etc/network/interfaces

Code: 
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).


# The loopback network interface
auto lo
iface lo inet loopback


# The primary network interface
auto eth1
allow-hotplug eth1
iface eth1 inet static
        address 10.10.0.3
        netmask 255.255.255.0
        network 10.10.0.0
        broadcast 10.10.0.255
        # gateway 10.10.0.1
        # dns-* options are implemented by the resolvconf package, if installed
        dns-nameservers 8.8.8.8
        dns-search blueservers.co.uk


auto eth0
allow-hotplug eth0
iface eth0 inet static
        address 46.4.121.166
        netmask 255.255.255.224
        broadcast 46.4.121.191
        gateway 46.4.121.187

guest route-n

Code: 
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
46.4.121.160    0.0.0.0         255.255.255.224 U     0      0        0 eth0
10.10.0.0       0.0.0.0         255.255.255.0   U     0      0        0 eth1
0.0.0.0         46.4.121.187    0.0.0.0         UG    0      0        0 eth0


tracert guest ip.

Code: 
[COLOR=#000000][FONT=Times New Roman] 1  biad401-fe0-0-0-3-isl-1.gip.net (204.59.152.205)  1.046 ms  0.756 ms  0.659 ms[/FONT][/COLOR]
 2  57.64.2.77 (57.64.2.77)  0.752 ms  0.803 ms  0.784 ms 
3  57.64.2.189 (57.64.2.189)  0.886 ms  0.866 ms  0.918 ms 
4  gi5-1.oakse1.OakHill.opentransit.net (193.251.242.13)  1.002 ms  1.004 ms  1.041 ms 
5  gi5-24.ashse2.Ashburn.opentransit.net (193.251.240.114)  2.365 ms  2.391 ms  2.458 ms
 6  xe-3-0-0-0.ashtr1.Ashburn.opentransit.net (193.251.128.149)  15.196 ms  2.328 ms  2.189 ms 
7  so-6-0-0-0.lontr2.London.opentransit.net (193.251.240.181)  75.041 ms xe-2-0-0-0.lontr2.London.opentransit.net (193.251.129.62)  76.818 ms so-6-0-0-0.lontr2.London.opentransit.net (193.251.240.181)  75.106 ms 
8  tengige0-0-0-0.ffttr3.Frankfurt.opentransit.net (193.251.132.13)  96.535 ms  93.47 ms tengige0-0-0-1.ffttr3.Frankfurt.opentransit.net (193.251.132.17)  95.859 ms 
9  kpn.GW.opentransit.net (193.251.254.138)  88.445 ms  154.098 ms  87.526 ms
10  ffm-s1-rou-1005.DE.eurorings.net (134.222.145.225)  92.299 ms  92.195 ms  91.057 ms
11  ffm-s1-rou-1021.DE.eurorings.net (134.222.231.205)  86.535 ms  88.758 ms  88.689 ms
12  nbgs1rou1001.DE.eurorings.net (134.222.225.26)  90.632 ms  91.489 ms  91.534 ms
13  kpn-gw.hetzner.de (134.222.107.21)  91.873 ms  91.981 ms  92.049 ms
14  hos-bb2.juniper1.fs.hetzner.de (213.239.240.146)  93.214 ms hos-bb2.juniper2.rz14.hetzner.de (213.239.240.151)  94.472 ms hos-bb2.juniper1.fs.hetzner.de (213.239.240.146)  94.198 ms
15  hos-tr2.ex3k12.rz14.hetzner.de (213.239.224.173)  95.296 ms  95.112 ms hos-tr3.ex3k12.rz14.hetzner.de (213.239.224.205)  95.293 ms
16  merlin3.blueservers.co.uk (46.4.121.187)  94.581 ms  93.139 ms  93.833 ms
17  static.161.121.4.46.clients.your-server.de (46.4.121.161)  95.137 ms  95.156 ms  94.2 ms
18  merlin3.blueservers.co.uk (46.4.121.187)  94.315 ms  92.25 ms  93.447 ms
19  static.161.121.4.46.clients.your-server.de (46.4.121.161)  104.044 ms  93.799 ms  95.036 ms
20  merlin3.blueservers.co.uk (46.4.121.187)  93.648 ms *  94.869 ms
21  static.161.121.4.46.clients.your-server.de (46.4.121.161)  95.016 ms  96.886 ms  93.894 ms
22  merlin3.blueservers.co.uk (46.4.121.187)  94.287 ms  93.351 ms  94.827 ms
23  static.161.121.4.46.clients.your-server.de (46.4.121.161)  94.792 ms  95.413 ms  94.246 ms
24  merlin3.blueservers.co.uk (46.4.121.187)  94.604 ms  94.475 ms *
25  static.161.121.4.46.clients.your-server.de (46.4.121.161)  95.398 ms  95.324 ms  95.384 ms
26  merlin3.blueservers.co.uk (46.4.121.187)  94.407 ms  93.363 ms  94.569 ms
27  static.161.121.4.46.clients.your-server.de (46.4.121.161)  94.33 ms  93.211 ms  93.856 ms
28  merlin3.blueservers.co.uk (46.4.121.187)  94.801 ms  94.383 ms  94.391 ms
29  static.161.121.4.46.clients.your-server.de (46.4.121.161)  98.33 ms  94.953 ms  95.37 ms*
[COLOR=#000000][FONT=Times New Roman]30  merlin3.blueservers.co.uk (46.4.121.187)  94.332 ms *  94.772 ms
[/FONT][/COLOR]

Please help
 
Hi Bluemerlin

look at your /etc/sysctl.conf

and make sure you have enabled ipv4 forwarding.

IF NOT this helps:

Code: 
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 'net.ipv4.ip_forward=1' >> /etc/sysctl.conf

and if you want use ipv6 in your guest

Code: 
echo 1 > /proc/sys/net/ipv6/conf/all/proxy_ndp
echo 'net.ipv6.conf.all.proxy_ndp=1' >> /etc/sysctl.conf'

Greets

Wiggerl
 
You must log in or register to reply here.
Top Bottom