Re: Can´t access a box remotely
me at hexren.net
Wed Jan 19 13:44:06 PST 2005
MB> Thank you for answer so quickly. I discovered that the problem is that
MB> ppp is using tun1 in place of tun0 and I am usin a dyndns deamon that
MB> is configured to update the ip address of tun0 (this is the interface
MB> that I want to use). Why ppp is using tun0??? I gess that something
MB> could be wrong in rc.conf. If I do and ssh to the ip address of tun1,
MB> I can connect normally.
MB> Here is the output of ifconfig:
MB> server:~ $ ifconfig
MB> rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
MB> inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255
MB> inet6 fe80::208:54ff:fe1d:8be5%rl0 prefixlen 64 scopeid 0x1
MB> ether 00:08:54:1d:8b:e5
MB> media: Ethernet autoselect (100baseTX <full-duplex>)
MB> status: active
MB> fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
MB> inet6 fe80::211:11ff:fe85:efa8%fxp0 prefixlen 64 scopeid 0x2
MB> ether 00:11:11:85:ef:a8
MB> media: Ethernet 10baseT/UTP
MB> status: active
MB> plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
MB> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
MB> inet 127.0.0.1 netmask 0xff000000
MB> inet6 ::1 prefixlen 128
MB> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
MB> tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
MB> Opened by PID 212
MB> tun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1492
MB> inet 126.96.36.199 --> 188.8.131.52 netmask 0xffffffff
MB> Opened by PID 230
MB> pflog0: flags=0<> mtu 33208
MB> Thank you for all!!!
MB> On Wed, 19 Jan 2005 22:22:33 +0100, Hexren <me at hexren.net> wrote:
>> >Hi to all!
>> >I can´t access to a box from the internet, using ssh.
>> Please specify your problem.
>> Do you have IP connectivity ? (Do a "ping 184.108.40.206" from the
>> machine of which you are showing logs here)
>> Do you have DNS (Do a "ping www.freebsd.org" )
>> Which error is given out when you try to ssh in from the internet. (try
>> ssh -v or ssh -vv)
Wild guessing here:
Maybe the interface tun0 gets created when it is first called by
something refering to rc.conf. (It is in there isn't it ?). When ppp
the fires up it creates its own tun device, taking the next "free"
name which is tun1 as tun0 already exists and ppp can't know if it is
used by something else.
Try removing all references to tun0 from /etc/rc.conf
Keep in mind that this is only a guess.
Also look at what hides behind PID 212. You can see in th output you
provided that tun0 was created by that PID.
More information about the freebsd-questions