AH, I think I get what you are saying. You have a linux doing NAT, 1 public IP on the outside and 1 private on the inside. You also have a spare public IP which you want to put on a client so they can do some funky things which requires them having a real IP address. 1 question about your statement. Where you say "carrier expects traffic to come from one WAN IP" kinda goes against what you implied by "public IP 2". If you have 2 pubic IPs, they they cannot expect your traffic to come from 1 WAN IP. Even if you NAT a private address explicitly to the 2nd public IP address that counts as 2. Do you have 1 or 2 public IP addresses? If you are given 2, then you should be able to do the config mentioned, putting the client on the same side as the router's public IP (since they are both in the same class C). If you have 1, well you are SOL. --- Carlos Fernandez Sanz <cfs-netfilter@xxxxxxxxxx> wrote: > > > > > > Before you ask: I can't connect this special > computer to the same place > I > > > connect the linux box (which would be the > obvious solution) because the > > > carrier expects traffic to come from one WAN IP, > owned by the linux box. > > > > How do they expect you to use any of the other IPs > in the pool they have > given > > you? > > I do use them by redirecting traffic from the linux > box to the destination > boxes (such as all trafic for public IP 2 goes to > 192.168.21.2, for > example). This works fine, *except* in this > particular case, where any > NATing is not an option. I need the computer behind > the linux box to > actually own the public address, because it signs > packets with it. > > __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html
