Jakob Posted September 17, 2010 Share Posted September 17, 2010 Hello Greetings from the cold Scandinavia. Been watching this show since season 01, and still enjoys it! I have some questions regarding a Debian / Linux server acting as gateway / router, and having "2 ISP's." To describe my setup. As said before, I run a server with Debian 5 (kernel 2.6.26-1-86). This acts as a gateway and router to the internet, and also I run other services like samba on it for the LAN clients. Here a quick paint to illustrate it all: Uploaded with ImageShack.us So it its equipped with 3 NICs, 1 for WAN (eth1), 1 for IPTV(eth3) which runs on my ISP closed network (ip 10.xx) and ofc 1 for LAN(eth2). The server is running as we speak perfectly, with just the WAN <-> LAN, NATing with iptables and dnsmasq running for local DHCP. What I want to accomplish is the following; Connect the IPTV NIC to the box, so I can run a tvheadend(TV streaming), to serve for my XBMC HTPC and other LAN clients. Heres a guide I've found so far, which I think could solve this problem, but Im not sure. http://lartc.org/howto/lartc.rpdb.multiple-links.html Heres my interfaces; # LAN NIC auto eth2 allow-hotplug eth2 #iface eth2 inet dhcp iface eth2 inet static address 192.168.1.1 network 192.168.1.0 netmask 255.255.255.0 broadcast 192.168.1.255 # WAN NIC auto eth1 allow-hotplug eth1 iface eth1 inet dhcp # IPTV NIC auto eth3 allow-hotplug eth3 iface eth3 inet dhcp And my route and ip route table(Without eth3/IPTV enabled); sudo route -N Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 89.*.*.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 0.0.0.0 89.*.*.* 0.0.0.0 UG 0 0 0 eth1 ip route list table main 192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.1 89.*.*.0/24 dev eth1 proto kernel scope link src 89.*.*.148 default via 89.*.*.254 dev eth1 And with eth3/IPTV enabled ip route list table main 192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.1 89.*.*.0/24 dev eth1 proto kernel scope link src 89.*.*.148 10.*.*.0/21 dev eth3 proto kernel scope link src 10.*.*.75 default via 10.*.*.254 dev eth3 default via 89.*.*.254 dev eth1 So what happens when i enable eth3 is, that I no longer have connection to WAN, can't ping google or browse the web. I presume its because suddenly 10.xx is now also default gateway. How do I fix this ? I wanna have the IPTV source available on this box, so I can serve it to LAN, but at the same time this box acts as gateway to WAN. I hope you guys understand my situation, and maybe are able to help. Feel free to ask, if you need more information. Thank you! Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.