Hi
This time I configured as simple as possible
with minimal settings, and voila things worked.
I successfully connected to internet in both
cases - DHCP server disabled in adsl modem, and
DHCP server enabled in adsl modem.
Thanks all of you guys for helping. :)
Here are config files:
##
On Sat, 20 Oct 2012 09:42:31 +0530, Jack wrote:
Hi again,
This time I disabled DHCP on my fxp0 interface and
in my adsl modem too.
But the problem still exists.
This time I tried both approaches:
assigned an IP address explicitly to fxp0, and
then no explicit assignment to fxp0.
That
On Sat, 20 Oct 2012 09:42:31 +0530
Jack wrote:
Hi again,
This time I disabled DHCP on my fxp0 interface and
in my adsl modem too.
But the problem still exists.
This time I tried both approaches:
assigned an IP address explicitly to fxp0, and
then no explicit assignment to fxp0.
I'd
On Thu, 18 Oct 2012 20:03:50 +0100, RW wrote:
On Tue, 16 Oct 2012 20:38:47 +0530
Jack wrote:
/etc/resolv.conf
# Generated by resolvconf
nameserver 192.168.1.1
If 192.168.1.1 is the modem, how can it be a proxy nameserver? It
doesn't have an internet connection if it's not
Hi again,
This time I disabled DHCP on my fxp0 interface and
in my adsl modem too.
But the problem still exists.
This time I tried both approaches:
assigned an IP address explicitly to fxp0, and
then no explicit assignment to fxp0.
I still don' get why FreeBSD is having trouble
connecting via
On Tue, 16 Oct 2012 20:38:47 +0530
Jack wrote:
My network schematic is:
PC --- ADSL modem - Internet
192.168.1.2 192.168.1.1
...
/etc/resolv.conf
# Generated by resolvconf
nameserver 192.168.1.1
If 192.168.1.1 is the modem, how can it be a proxy
On Tue, Oct 16, 2012 at 9:19 PM, Mark Blackman m...@exonetric.com wrote:
On 16 Oct 2012, at 16:38, Jack jacks.1...@gmail.com wrote:
I 'll try mpd5. Thanks.
Actually, I was concerned with userland ppp, becoz of the
scenarios where we have a FreeBSD machine and the only
way to connect to
Hi,
Thank you guys for your suggestions, and sharing your
experiences with me.
This time I deleted old /var/log/ppp.log file, and
I did modify /etc/ppp/ppp.conf - just the location
of ifaddr line is changed and some more logging
options set -nothing else is changed.
.
The file is this
On 16 Oct 2012, at 16:08, Jack jacks.1...@gmail.com wrote:
Hi
I'm new as a FreeBSD user, and trying to configure my
pppoe connection.
[snip]
fxp0 is the ethernet interface of my PC via which adsl modem is connected.
Any suggestions ...
Consider using the ports mpd5 daemon for a
On Tue, Oct 16, 2012 at 8:49 PM, Mark Blackman m...@exonetric.com wrote:
On 16 Oct 2012, at 16:08, Jack jacks.1...@gmail.com wrote:
Hi
I'm new as a FreeBSD user, and trying to configure my
pppoe connection.
[snip]
fxp0 is the ethernet interface of my PC via which adsl modem is
On 16 Oct 2012, at 16:38, Jack jacks.1...@gmail.com wrote:
I 'll try mpd5. Thanks.
Actually, I was concerned with userland ppp, becoz of the
scenarios where we have a FreeBSD machine and the only
way to connect to internet is an adsl modem in bridge mode
(assuming the mode in modem, can't
On 16 Oct 2012, at 16:49, Mark Blackman m...@exonetric.com wrote:
On 16 Oct 2012, at 16:38, Jack jacks.1...@gmail.com wrote:
I 'll try mpd5. Thanks.
Actually, I was concerned with userland ppp, becoz of the
scenarios where we have a FreeBSD machine and the only
way to connect to
On Tue 2012-10-16 20:38:47 UTC+0530, Jack (jacks.1...@gmail.com) wrote:
I'm new as a FreeBSD user, and trying to configure my
pppoe connection.
After reading handbook and searching on various forums,
I prepared the ppp.conf file, and tried starting the ppp via
# ppp -ddial adsl
Here
On Tue, 16 Oct 2012 20:38:47 +0530, Jack wrote:
I'm new as a FreeBSD user, and trying to configure my
pppoe connection.
I've been using PPPoE with a DSL modem for many years, using
FreeBSD 4, 5 and 7 with the system's PPPoE tools. The IP
was provided to the computer directly, so no DHCP in the
On Thu, 03 Apr 2008 15:55:05 +1100
Terry Sposato [EMAIL PROTECTED] wrote:
Norberto Meijome wrote:
On Wed, 2 Apr 2008 14:43:20 +0200
Mel [EMAIL PROTECTED] wrote:
I think you'll find that bursts are best counteracted like this:
Hello again:
I solved the problem with the name resolution associated
with installing ports via ftp, portsnap.
1. I found an erroneous entry in routing tables and removed it
and rebooted.
There was no route to the default gateway because there was
another erroneous gateway entry before it. I
On Sat, Oct 27, 2007 at 04:42:02PM -0700, jekillen wrote:
I set up a system with a static ip connection to the internet
I checked inetd.conf and resolv.conf.
Just FYI, inetd.conf shouldn't matter here, as it has to do with
running a server, not accessing one.
look in resolv.conf, there was
Hello:
I have been trying to tame the use of the ports mechanisms.
I set up a system with a static ip connection to the internet
and when I run:
pkg_add -r csup-without-gui (verbatim from the freebsd handbook I
downloaded just a few days ago)
I get this:
Error: FTP Unable to get
On Sat, 27 Oct 2007 16:42:02 -0700
jekillen [EMAIL PROTECTED] wrote:
Hello:
I have been trying to tame the use of the ports mechanisms.
I set up a system with a static ip connection to the internet
and when I run:
pkg_add -r csup-without-gui (verbatim from the freebsd handbook I
On Oct 27, 2007, at 4:54 PM, RW wrote:
On Sat, 27 Oct 2007 16:42:02 -0700
jekillen [EMAIL PROTECTED] wrote:
Hello:
I have been trying to tame the use of the ports mechanisms.
I set up a system with a static ip connection to the internet
and when I run:
pkg_add -r csup-without-gui (verbatim
thank you; your right it is cvsup, but the handbook indicates that I
could use csup in place of cvsup in the command line on v6.2 and up.
But that does not seem to effect the resolver issue (unless I am
mistaken here and the resolver is actually working and it is just the
reference)
Jeff
Sendmail uses the system calls to resolve names. You need to check:
/etc/nsswitch.conf
In that file check the hosts line, this gives the order for hostname
resolution, typically it is files then dns.
Then you should check your /etc/hosts file to be sure that localhost is
there and correct.
On Mar 19, 2007, at 3:17 AM, Derek Ragona wrote:
Sendmail uses the system calls to resolve names. You need to check:
/etc/nsswitch.conf
In that file check the hosts line, this gives the order for hostname
resolution, typically it is files then dns.
Then you should check your /etc/hosts
Hello:
Where does sendmail look to find out who it is?
Resolve.conf?
It keeps throwing up messages that it cannot
resolve the name localhost, or that is the
way I am interpreting the messages.
FreeBSD v6.2 generic
Thanks in advance;
Jeff K
___
the TCP (or at least FTP, WWW Telnet) programs are
having an issue with resolving the name. My guess is that they are
timing out through trying to resolve via one means, and therefore then
try a DNS resolve. Is there a way to determine the order in which the
system currently does name resolution? I
start with your /etc/hosts. it is first looked up then your bind
\jett
I just installed 5.1 and have been playing around with it, but I am
troubled by an issue with my network configuration. I apologize if this
is the wrong list, it seemed to be the most appropriate. I want to at
least
You need to create a resolv.conf file. Your BSD box does not have the
required information to be able to resolve ip addresses with FQDNs and it
needs to have that information.
--charlie
_
Get McAfee virus scanning and cleaning of
(or at least FTP, WWW Telnet) programs are
having an issue with resolving the name. My guess is that they are
timing out through trying to resolve via one means, and therefore then
try a DNS resolve. Is there a way to determine the order in which the
system currently does name resolution? I looked
Hello!
# host localhost
localhost.my.domain is a nickname for my.domain
my.domain has address 202.x.x.x
Someone suggested I check localhost.:
# host localhost.
Host not found.
AFAIK the host command doesn't use /etc/hosts. No matter what is
specified in /etc/host.conf, the host
of the (IPv4) localhost entry, sendmail was
resolving localhost to my internet IP address, rather than 127.0.0.1.
It was suggested to me that the name resolution method that sendmail uses
would not use /etc/hosts anyway and since that matched my own experience I'm
inclined to think it's true, that's
Hi,
In the course of trying to resolve a problem with sendmail (refusing to
deliver even local mail), I saw a note in the sendmail configuration docs
which says host localhost must resolve to 127.0.0.1. However, when I
checked my system I instead found (details obscured):
# host localhost
W. Sierke wrote:
Hi,
In the course of trying to resolve a problem with sendmail (refusing to
deliver even local mail), I saw a note in the sendmail configuration docs
which says host localhost must resolve to 127.0.0.1. However, when I
checked my system I instead found (details obscured):
# host
32 matches
Mail list logo
