Re: Can't access aliased ip address
On 2002.01.02 18:29 Jason M. Harvey wrote:
> hello,
>
> if this person wants to use pcanywhere from home... which ip address is
> he using for pcanywhere to connect to? unless he's using some sort of
> vpn setup between home and work, he won't get to his office pc.
> are you running masquerading on the pc 216.86.213.93? if the 196.168
> network is translated to that ip, you'll need to forward ports 5631 and
> 5632 from 216.86.213.93 back to his ip (192.168.y.z). once you've done
> that, he will be able to pcanywhere to 216.86.213.93.... and invisible
> to him will be the forwarding of pcanywhere to his private ip.
>
This is actually a better idea for my worst case scenario of having to add
another NIC if I can't get the aliased address to work.
However, there is someone else that has been toying with the pcanywhere
idea as well and I'm pretty sure once it is working for this guy the other
one will want it too.
I don't use pcanywhere so I don't know if you can manually specify a
different port. If you can I guess I could give everyone that wants it a
different port on the *.93 address but not using the defaults could create
some unique support situations when people forget their assigned port or
don't know how to change the defaults and I'd like to avoid that.
> i've configured many routers that run NAT and needed to do the same
> thing. i've never done port forwarding with ipchains/iptables but i'm
> positive that it can be done.
>
I haven't setup the port forwarding yet since traffic to the address I
wanted to use wasn't getting there anyway.
I was planning on using ipmasqadm to do the port fowarding once I can
forward traffic on the address that I would like to use.
Thanks,
Chad
> it sounds like what i'm advising is a little off-track of what you were
> looking at before... if someone else has better suggestion, listen to
> them! the port-forwarding will work, but it may be a little more for you
> to set up...
>
> good luck,
> jason
>
> On Wed, Jan 02, 2002 at 06:19:46PM -0800, Chad Morgan wrote:
> | I have a gateway to share a dsl line with about 20 users that all use
> win
> | 9x or a more recent windows product. One of the users wants to be able
> to
> | setup pcanywhere so he can access his office computer using his cable
> modem
> | at home instead of the phone line.
> |
> | This is the output of ifconfig:
> |
> | eth0 Link encap:Ethernet HWaddr 00:A0:CC:23:A3:AC
> | inet addr:216.86.213.93 Bcast:216.86.213.255
> Mask:255.255.255.0
> | UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> | RX packets:241367 errors:0 dropped:0 overruns:0 frame:0
> | TX packets:260291 errors:0 dropped:0 overruns:0 carrier:0
> | collisions:41 txqueuelen:100
> | Interrupt:10 Base address:0x6000
> |
> | eth0:1 Link encap:Ethernet HWaddr 00:A0:CC:23:A3:AC
> | inet addr:216.86.213.94 Bcast:216.86.213.255
> Mask:255.255.255.0
> | UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> | Interrupt:10 Base address:0x6000
> |
> | eth1 Link encap:Ethernet HWaddr 00:A0:CC:5A:CB:A2
> | inet addr:192.168.0.1 Bcast:192.168.0.255
> Mask:255.255.255.0
> | UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> | RX packets:191550 errors:0 dropped:0 overruns:0 frame:0
> | TX packets:233023 errors:0 dropped:0 overruns:0 carrier:0
> | collisions:0 txqueuelen:100
> | Interrupt:11 Base address:0x6100
> |
> | lo Link encap:Local Loopback
> | inet addr:127.0.0.1 Mask:255.0.0.0
> | UP LOOPBACK RUNNING MTU:3924 Metric:1
> | RX packets:38940 errors:0 dropped:0 overruns:0 frame:0
> | TX packets:38940 errors:0 dropped:0 overruns:0 carrier:0
> | collisions:0 txqueuelen:0
> |
> | And this is the output of route:
> |
> | Kernel IP routing table
> | Destination Gateway Genmask Flags Metric Ref Use
> | Iface
> | adsl-gte-la-216 * 255.255.255.255 UH 0 0 0
> | eth0
> | adsl-gte-la-216 * 255.255.255.255 UH 0 0 0
> | eth0
> | 192.168.0.0 * 255.255.255.0 U 0 0 0
> | eth1
> | 216.86.213.0 * 255.255.255.0 U 0 0 0
> | eth0
> | default adsl-gte-la-216 0.0.0.0 UG 1 0 0
> | eth0
> |
> | Note: the the first two entires are the hosts associated with eth:0 and
> | eth0:1
> |
> | Now, I'm a remote location but when logged into this machine I can ping
> all
> | ip addresses.
> |
> | >From my machine I get no responce when I try and ping the address
> | associated with eth0:1 however when I use tcpdump host 216.86.213.94 I
> get
> | the following result while pinging that address from my machine so it
> looks
> | like it is getting something but not answering.
> |
> | 11:31:07.232889 ca-brea2a-102.stmnca.adelphia.net >
> | adsl-gte-la-216-86-213-94.mminternet.com: icmp: echo request (DF)
> |
> | Also, it is not possible for me to ask someone at the site to try to
> ping
> | the eth0:1 address from a machine on the 192.168.0 segment, however
> I'll be
> | in the area tomorrow (only 15-20 minutes out of my way) and can swing
> by
> | and see if it is working from there if absolutely necessary.
> |
> | This is also a repost, I've incorporated all of the advice from my
> original
> | post but more important priorities forced me to put this on the back
> | burner. That always catches up with me since now this is a fire that I
> need
> | to put out.
> |
> | If I can't get the aliasing to work the way I want it to, I'll have to
> go
> | down there tomorrow and throw in another NIC for the second address but
> I
> | don' really want to do that because it is possible that more people
> will
> | want the same and I don't want to have to keep adding cards. Space and
> | maintenance are more of issues than cost.
> |
> | Also, it isn't practical to just give that computer an external ip
> address
> | because it is behind another hub on the 192 segment.
> |
> | Any assistance or advice would be greatly appreciated.
> |
> | Chad Morgan
> |
> |
> | --
> | To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> | with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> |
>
> --
> registered linux user #202942
> http://counter.li.org/
> ----------------------------
> http://www.theigloo.dhs.org
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
Reply to: