Re: linux routing
Well apparently my art career wasnt as promsing as I thought. I'll try again: internet ->eth0 -> 38.185.233.175 -> eth1 -> box1 (38.185.233.176) and box2 (38.185.233.177) -Kevin
Re: potato on Compaq 1600?
Thanks to all who responded - potato appears to be happily running on this box now :-) No special arrangements were required - we just ran the automagic setup software and selected "other" for the o/s. regarding: > Now I have a specific query: the onboard ethernet is identified in > /proc/pci as "Compaq Netelligent 10/100 ProLiant (rev 16)". Anyone know > what chipset might be under the hood here? As suggested, it's a ThunderLAN chip (at least ours is, sounds like some might have an intel chip). Thanks, Neale.
running without portmapper, inetd
Does anyone have any experience with hacking Debian's scripts to get a system happily running networking without portmapper, or even without inetd? Any issues to be wary of in this area? The motivations: * portmapper: I can't see what need I have for it - therefore it just becomes a security liability * inetd: with all esential services (e.g. postfix, ssh) running as daemons, what need is ther for this too (I'll admit to being not entirely convinced on thi one yet)? Thanks, Neale.
ipchains and aliases
Hi list! I have an NIC with 3 ip aliases on it. How can I setup ipchains rules to account all traffic moving throw this aliase NOT interface. Im trying to use such rule(in test purpose), but it simply does not work. ipchains -I input -j ACCEPT -l -i eth0:2 Best regards, Ant mailto:[EMAIL PROTECTED]
Re: linux routing
On Tue, Apr 25, 2000 at 05:00:31PM -0700, Kevin wrote: > Well apparently my art career wasnt as promsing as I thought. I'll try > again: > > internet ->eth0 -> 38.185.233.175 -> eth1 -> box1 (38.185.233.176) and box2 > (38.185.233.177) Assuming you've been assigned a subnet and not a few static IPs this should be relatively straightforward. However, if the IPs you give are accurate I'm not sure you've been assigned a subnet. Let's assume that you have, and the subnet in question is 38.185.233.160/27 (unlikely, since that's a 32 address subnet; however it's the only one I could think of that contains your addresses). In that case you'd set up your router like this: eth0 -> whatever the external IP is eth1 -> 38.185.233.175 routing table on router: default route gw [next hop for eth0] box1 and box2 would list 38.185.233.175 as their default gw. The next hop at the ISP also needs a route for network 38.185.233.160/27 pointing to the IP for eth0. I suspect that the above is all smoke and you've actually been assigned three IP addresses. You naturally want to place two of them behind a linux firewall. To do this you're going to have to configure bridging. In this scenario eth0 has IP address 38.185.233.175, but it also performs proxy ARP for 38.185.233.176 and 38.185.233.177. router then forwards all packets out eth1 so box 1 and box2 can communicate with the world. I have never set up bridging in linux; I'm ashamed to admit I'm all to familiar with bridging using "real" routers like Bay or Cisco gear ... I don't want to say more until I have a clearer idea of what you are trying to do and what your situation is. -- Nathan Norman "Eschew Obfuscation" Network Engineer GPG Key ID 1024D/51F98BB7http://home.midco.net/~nnorman/ Key fingerprint = C5F4 A147 416C E0BF AB73 8BEF F0C8 255C 51F9 8BB7 pgpJmqyfDxgwd.pgp Description: PGP signature
Re: linux routing
Kevin wrote: > > Well apparently my art career wasnt as promsing as I thought. I'll try > again: > > internet ->eth0 -> 38.185.233.175 -> eth1 -> box1 (38.185.233.176) and box2 > (38.185.233.177) Just to get clear: do you have three boxes (router, box1, box2) with ips 38.185.233.175 to 38.185.233.177 and router having a second ip for the internet connection on eth0 or do you have two boxes (box1, box2) with ips 38.185.233.176 to 38.185.233.177 for internal traffic and box1 is the router with the ip 38.185.233.175 for the internet connection? In the first case you need the second ip to create a rouleset for your routing table. In the second case all subnet masks for every ip should be one of these: 255.255.255.240, 255.255.255.248, 255.255.255.252 or 255.255.255.254 So you only have to configure box2's gateway as 38.185.233.176 and add the default route for mask 0.0.0.0 to 38.185.233.175. And don't forget to configure your kernel for ip forwarding. See NET3-4-HOWTO. Juergen
Re: linux routing
On Tue, 25 Apr 2000, Kevin wrote: > Well apparently my art career wasnt as promsing as I thought. I'll try > again: > > internet ->eth0 -> 38.185.233.175 -> eth1 -> box1 (38.185.233.176) and box2 > (38.185.233.177) > > -Kevin > > I'm not sure why you need the router. Your two machines are on the same IP subnet, which is an Ethernet LAN (I'm assuming this, you haven't provided the netmask of the network which is necessary to determine this). Normally, in an IP network, each network has a separate IP network address (which is defined by the netmask). The router forwards IP datagrams between the two networks. In setting up your network, you should have two separate IP network addresses for the two networks in the router machine. Its two interfaces are 38.185.233.175 and 38.185.233.176 which appear to be in the same IP network address space. The second interface (eth1) should be in another IP address space. I could help a little more if you were to explain a little more the details of the 'internet' and why you don't want to put both machines on that LAN.
WU IMAP default mailfolder
Hi Does somebody know how I can change the default mailfolder from $HOME to $HOME/mail ? That's because some mailclients (Lotus Notes) can't change the default mail folder, so I have to change this at the server I use University of Washington IMAP Server 4rev1 Tnx Patrick --- Encryption: A powerful algorithmic encoding technique employed in the creation of computer manuals.
Re: linux routing
The subnet is 255.255.255.224, I just gave those ips as an example. I need the router because it is being used with wireless equipment, and as far as I know they dont make any kind of wireless wic for a cisco. The "router (38.185.233.175)" is connected to our hub which then goes to our cisco and the t1. I need to route wireless clients ips through the 38.185.233.175 router. - Original Message - From: "Stephen A. Witt" <[EMAIL PROTECTED]> To: "Kevin" <[EMAIL PROTECTED]> Cc: Sent: Wednesday, April 26, 2000 9:01 AM Subject: Re: linux routing I'm not sure why you need the router. Your two machines are on the same IP subnet, which is an Ethernet LAN (I'm assuming this, you haven't provided the netmask of the network which is necessary to determine this). Normally, in an IP network, each network has a separate IP network address (which is defined by the netmask). The router forwards IP datagrams between the two networks. In setting up your network, you should have two separate IP network addresses for the two networks in the router machine. Its two interfaces are 38.185.233.175 and 38.185.233.176 which appear to be in the same IP network address space. The second interface (eth1) should be in another IP address space. I could help a little more if you were to explain a little more the details of the 'internet' and why you don't want to put both machines on that LAN.
Re: linux routing
Quoting Kevin <[EMAIL PROTECTED]>: > The subnet is 255.255.255.224, I just gave those ips as an example. I > need > the router because it is being used with wireless equipment, and as far > as I > know they dont make any kind of wireless wic for a cisco. The "router > (38.185.233.175)" is connected to our hub which then goes to our cisco > and > the t1. I need to route wireless clients ips through the 38.185.233.175 > router. Cisco just recently purchased Aironet Communications, which produces a wireless bridge, which is exactly what it says: a bridge. Ethernet (10BaseT) on one end, antenna on the other. At the remote location you'd have another wireless bridge. No messy routing to worry about, unless you wanted to throw a 2-nic router in somewhere. I've worked with the Aironet devices and they do a fairly nice job. I've also worked with ciscos running over microwave gear. Just v.35 between the wireless and the cisco. What is the interface to the wireless unit? If you want to route, you could break your 255.255.255.224 subnet into two subnets of 255.255.255.240, one for each location. You would lose two IP addresses, though. Another option is using masquerading/network address translation/port address translation. -- John Kramer [EMAIL PROTECTED]
Re: linux routing
Well my main question is how I do it at all. Even if it's not the best way or the only way. Just humor me. I can't find any kind of docs on how to actually do it. -Kevin
