Networking help - long

E

emergant

New Member
Sep 10, 2009
4
0
1
I'm pretty green about networking and I've tried searching the forum, looking at the wiki and google. I'm at a loss so would appreciate any help I'm building a home server with three interfaces as follows: eth0 > ddwrt router on 192.168.1.0/24 wireless internet eth2 (vmbr0) to switch for internal Lan plus containers on 192.168.2.0/24 eth3 internal lan 192.168/3/101 (experimental not such a big deal at the moment.) I may play with jumbo frames later and use it for management. I can ssh to the the server on the eth0 or eth3 subnets no problem. I can ping all networks and access the net from the host on its subnets including ssh to 192.168.2.101 and then run apt-get update. But if I enter a container I cant ping the router or run apt-get update The following are run on the host roxmox:~# ip route show 192.168.2.104 dev venet0 scope link 192.168.3.0/24 dev eth1 proto kernel scope link src 192.168.3.101 192.168.2.0/24 dev vmbr0 proto kernel scope link. src192.168.2.101 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.140 default via 192.168.1.1 dev eth0 proxmox:~# cat /etc/network/interfaces # network interface settings auto lo iface lo inet loopback auto eth1 iface eth1 inet static address 192.168.3.101 netmask 255.255.255.0 auto eth0 iface eth0 inet static address 192.168.1.140 netmask 255.255.255.0 gateway 192.168.1.1 auto vmbr0 iface vmbr0 inet static address 192.168.2.101 netmask 255.255.255.0 gateway 192.168.1.1 bridge_ports eth2 bridge_stp off bridge_fd 0 While running apt-get update on the container tcpdump on the host shows proxmox:~# tcpdump host 192.168.2.104 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 14:55:10.682183 IP 192.168.2.104.59784 > DD-WRT.domain: 15192+ AAAA? security.debian.org. (37) 14:55:10.682193 IP 192.168.2.104.37443 > DD-WRT.domain: 15192+ AAAA? ftp.debian.org. (32) 14:55:15.678473 IP 192.168.2.104.37443 > DD-WRT.domain: 15192+ AAAA? ftp.debian.org. (32) 14:55:15.678480 IP 192.168.2.104.59784 > DD-WRT.domain: 15192+ AAAA? security.debian.org. (37) 14:55:20.678538 IP 192.168.2.104.43265 > DD-WRT.domain: 37482+ AAAA? security.debian.org.domain.net. (48) 14:55:20.678543 IP 192.168.2.104.45823 > DD-WRT.domain: 38250+ AAAA? ftp.debian.org.domain.net. (43) DDWRT is the router. Oddly if I run ip route show on the container I get: squeeze:/# ip route show 192.0.2.1 dev venet0 scope link This looks wrong but I don't know where these addresses come from I know this long but I'm hoping I've given enough info for someone to see the problem Mark
 
Last edited:
Re: Networking help - long - clarity

I'm pretty green about networking and I've tried searching the forum, looking at the wiki and google. I'm at a loss so would appreciate any help I'm building a home server with three interfaces as follows:
Code: 
eth0 > ddwrt router on 192.168.1.0/24 
eth2 (vmbr0)  > wireless internet to switch for internal Lan plus containers on 192.168.2.0/24 
eth3 > internal lan 192.168/3/101 (experimental not such a big deal at the moment.)
I may play with jumbo frames later and use it for management.
I can ssh to the the server on the eth0 or eth3 subnets no problem.
I can ping all networks and access the net from the host on its subnets including ssh to 192.168.2.101 and then run apt-get update.
But if I enter a container I can't ping the router or run apt-get update
The following are run on the host
Code: 
 proxmox:~# [B]ip route show[/B] 
 
192.168.2.104 dev venet0 scope link 
192.168.3.0/24 dev eth1 proto kernel scope link src 
192.168.3.101 192.168.2.0/24 dev vmbr0 proto kernel scope link. src
192.168.2.101 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.140 
default via 192.168.1.1 dev eth0

Code: 
 proxmox:~# [B]cat /etc/network/interfaces[/B] 
 
# network interface settings 
auto lo 
iface lo inet loopback 
 
auto eth1 
iface eth1 inet static 
    address 192.168.3.101 
    netmask 255.255.255.0 
 
auto eth0 
iface eth0 inet static 
    address 192.168.1.140 
    netmask 255.255.255.0 
    gateway 192.168.1.1 
 
auto vmbr0 
iface vmbr0 inet static 
    address 192.168.2.101 
    netmask 255.255.255.0 
    gateway 192.168.1.1 
    bridge_ports eth2 
    bridge_stp off 
    bridge_fd 0
While running apt-get update on the container tcpdump on the host shows:
Code: 
 proxmox:~# [B]tcpdump[/B] 
 
host 192.168.2.104
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 
14:55:10.682183 IP 192.168.2.104.59784 > DD-WRT.domain: 15192+ AAAA? security.debian.org. (37) 14:55:10.682193 IP 192.168.2.104.37443 > DD-WRT.domain: 15192+ AAAA? ftp.debian.org. (32) 
14:55:15.678473 IP 192.168.2.104.37443 > DD-WRT.domain: 15192+ AAAA? ftp.debian.org. (32) 14:55:15.678480 IP 192.168.2.104.59784 > DD-WRT.domain: 15192+ AAAA? security.debian.org. (37)
14:55:20.678538 IP 192.168.2.104.43265 > DD-WRT.domain: 37482+ AAAA? security.debian.org.domain.net. (48) 14:55:20.678543 IP 192.168.2.104.45823 > DD-WRT.domain: 38250+ AAAA? ftp.debian.org.domain.net. (43)
DDWRT is the router. Oddly if I run ip route show on the container I get:
Code: 
 squeeze:/# [B]ip route show[/B] 
 
192.0.2.1 dev venet0 scope link
This looks wrong but I don't know where these addresses come from I know this long but I'm hoping I've given enough info for someone to see the problem
Mark
 
Thanks for cleaning that up apmuthu :) Didn't know about the code tag. Do now :)

My problem was that I hadnt enabled masquerading on the host. I couldnt get my head around the fact that outside the VPS but on the same subnet all worked fine. Everythings fine now.
 
You must log in or register to reply here.
Top Bottom