Re: Re[2]: Can´t access a box remotely

[Mauricio Brunstein]

Hexren:

The pocess of PID 212 is ppp:

server:~ $ ps auxw|grep 212                                           
      root    212  0.0  0.8  3240 2112  ??  Ss    5:53PM   0:00.43 ppp
-ddial default
mauro   687  0.0  0.4  1472  892  p0  S+    6:48PM   0:00.00 grep 212
server:~ $

My rc.conf has references to tun0:

server:~ $ sudo cat /etc/rc.conf

# -- sysinstall generated deltas -- # Sun Nov 21 13:07:41 2004
# Created: Sun Nov 21 13:07:41 2004
# Enable network daemons for user convenience.
# Please make all changes to this file, not to /etc/defaults/rc.conf.
# This file now contains just the overrides from /etc/defaults/rc.conf.
#
##############################################################

hostname="server.estudio"
netd_enable="YES"
saver="dragon"
scrnmap="NO"
sshd_enable="YES"
sshd_flags="-4 -p 222"
usbd_enable="YES"
network_interfaces="lo0 rl0 fxp0 tun0"
#network_interfaces="lo0 rl0 fxp0"
ifconfig_tun0=" "
ifconfig_rl0="inet 192.168.2.1  netmask 255.255.255.0"
ifconfig_fxp0="media 10baseT/UTP up"

ppp_enable="YES"
ppp_mode="ddial"
ppp_nat="YES"
ppp_profile="my_isp"

router_enable="YES"
gateway_enable="YES"          # Set to YES if this host will be a gateway

pf_enable="YES" # Enable PF (load module if required)
pf_rules="/etc/pf.conf"         # rules definition file for pf
pf_flags="-d"                     # additional flags for pfctl startup
#pflog_enable="YES"              # start pflogd(8)
#pflog_logfile="/var/log/pflog"  # where pflogd should store the logfile
#pflog_flags=""                  # additional flags for pflogd startup

inetd_enable="YES"               # Run the network daemon dispatcher (YES/NO).
inetd_program="/usr/sbin/inetd" # path to inetd, if you want a different one.
inetd_flags="-wW -C 60"         # Optional flags to inetd

#nmbd_enable="YES"
#smbd_enable="YES"
#winbindd_enable="YES"

named_enable="YES"               # Run named, the DNS server (or NO).
named_program="/usr/sbin/named" # path to named, if you want a different one.
named_flags="-u bind"           # Flags for named
named_pidfile="/var/run/named/pid" # Must set this in named.conf as well
named_chrootdir="/var/named"    # Chroot directory (or "" not to auto-chroot it)
named_chroot_autoupdate="YES"   # Automatically install/update chrooted
                                # components of named. See /etc/rc.d/named.
named_symlink_enable="YES"      # Symlink the chrooted pid file
server:~ $


Thank you again,

Mauricio.


On Wed, 19 Jan 2005 22:44:04 +0100, Hexren <me at hexren.net> wrote:
> MB> Hexren:
> 
> 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>         options=8<VLAN_MTU>
> 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>         options=8<VLAN_MTU>
> 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 200.127.126.73 --> 200.32.0.42 netmask 0xffffffff
> MB>         Opened by PID 230
> MB> pflog0: flags=0<> mtu 33208
> 
> MB> Thank you for all!!!
> 
> MB> Mauricio
> 
> 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 216.136.204.117" 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)
> >>
> >> Hexren
> >>
> >>
> 
> 
> ---------------------------------------------
> 
> 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.
> 
> Hexren
> 
>