well I think you got your internal and external interfaces
both connected to the same network ... so it will indeed be generally confused
about where to route things to ...
If your Internet connection is a typical xDSL or Cable
modem, the Ext Interface will normally gets its IP address and such via DHCP
from the ISP ... so you would want to assign like this ...
under header "External Interfaces", uncomment "EXTIF=eth0"
(or whatever your ETH to the outside is) ... but leave the EXTIP, EXTNM,
EXTGW and DNS commented out ... this tells the system to get these via DHCP
... it will look like this when done ...
##External Interface
##The external interface has a fairly restrictive firewall when not in PBX
##only mode. See the Firewall section in this file for more details.
EXTIF=eth0
##The external interface has a fairly restrictive firewall when not in PBX
##only mode. See the Firewall section in this file for more details.
EXTIF=eth0
##Fancy External interface support
##THIS HAS CHANGED FROM PREVIOUS VERSIONS!!!
##You will still need to set EXTIF to your external interface (wp*).
##If EXTIF=hdlc0, I will start zaptel and run sethdlc.
##If EXTIF=pvc0. I will start zaptel and run sethdlc. You will also need to
##fill in HDLCLMI and HDLCDLCI
##See more options below.
##THIS HAS CHANGED FROM PREVIOUS VERSIONS!!!
##You will still need to set EXTIF to your external interface (wp*).
##If EXTIF=hdlc0, I will start zaptel and run sethdlc.
##If EXTIF=pvc0. I will start zaptel and run sethdlc. You will also need to
##fill in HDLCLMI and HDLCDLCI
##See more options below.
##Use wancfg first!
#EXTIF=wp1chdlc
#EXTIF=wp1chdlc
##Use cisco encapsulation and be
done
#EXTIF=hdlc0
#EXTENC="cisco"
#EXTIF=hdlc0
#EXTENC="cisco"
##Zaptel Data Support
##If you set EXTIF=hdlc0 above, you will probably need to set the
##protocol here. See sethdlc for valid types, but you PROBABLY want
##"cisco". DO NOT USE THIS WITH SANGOMA HARDWARE!!! Use wancfg!!!
#EXTENC="cisco"
##If you set EXTIF=hdlc0 above, you will probably need to set the
##protocol here. See sethdlc for valid types, but you PROBABLY want
##"cisco". DO NOT USE THIS WITH SANGOMA HARDWARE!!! Use wancfg!!!
#EXTENC="cisco"
##Frame relay with LMI and DLCI (will use
hdlc0)
#EXTIF=pvc0
#HDLCLMI=ansi
#HDLCDLCI=100
#EXTIF=pvc0
#HDLCLMI=ansi
#HDLCDLCI=100
##Sometimes it takes a while for the WAN interface to come
up...
##This can happen with frame relay and PPPoE, for example.
##Set this variable in seconds, and I will sleep on startup before
##I attempt to bring up the WAN interface.
#WANDELAY=60
##This can happen with frame relay and PPPoE, for example.
##Set this variable in seconds, and I will sleep on startup before
##I attempt to bring up the WAN interface.
#WANDELAY=60
##If EXTIP is set, the remaining STATIC config is read
instead of the
##default, which is DHCP client on $EXTIF. If you are using a T1/E1
##EXTGW is also the PtP address. You can enter as many DNS servers as
##you wish. They will be added in order.
#EXTIP="192.168.199.11"
#EXTNM="255.255.255.0"
#EXTGW="192.168.199.1"
#DNS="192.168.199.1"
##default, which is DHCP client on $EXTIF. If you are using a T1/E1
##EXTGW is also the PtP address. You can enter as many DNS servers as
##you wish. They will be added in order.
#EXTIP="192.168.199.11"
#EXTNM="255.255.255.0"
#EXTGW="192.168.199.1"
#DNS="192.168.199.1"
then in the section describing your internal interface do
something like this ...
##If you do not define the INTIF, I will not try to start
one.
##If you do not define the INTIF, I will also not start the following services:
##dnsmasq iptables astshape (PBX only mode)
##PBX Only mode is enabled by default from 0.2.8.10
INTIF=eth1
##If you do not define the INTIF, I will also not start the following services:
##dnsmasq iptables astshape (PBX only mode)
##PBX Only mode is enabled by default from 0.2.8.10
INTIF=eth1
##Internal IP address and
netmask
INTIP=192.168.199.1
INTNM=255.255.255.0
INTIP=192.168.199.1
INTNM=255.255.255.0
that
should fix you right up ...
G.Hendershot
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jack
Sent: Monday, October 02, 2006 10:30 AM
To: [EMAIL PROTECTED]
Subject: [Astlinux-users] Static IP config on Astlinux Not able to pingoutside ??
After almost 2 weeks of testing, trying with the development build, I got almost everything to work as I wanted.
But now I am somehow stuck with something I don't understand.
When I configure Astlinux to use a static ip in rc.conf:
## Changed to resolve conflicts...
INTIP=192.168.15.55
INTNM=255.255.255.0
EXTIP="192.168.15.55 "
EXTNM="255.255.255.0"
EXTGW="192.168.15.1"
DNS="192.168.15.1 233.73.255.52 233.132.189.250"
It does somehow resolve the NAME to IP if I do a ping to somewhere but it also gives me Network Unreachable in the end it is not pinging to any internet address
but it is pinging and reaching the local LAN perfectly.
When I set Astlinux to receive an IP, by commenting #EXTIP=", from my local DHCP server everything works as expected. I can ping and resolve any address, YAHOO!
There must be something I am not doing right, I do not see what, I could use some help ;-)
Regards
_______________________________________________ Astlinux-users mailing list [email protected] http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
