On Sat, Feb 28, 2009 at 4:30 PM, Derek Ragona <
de...@computinginnovations.com> wrote:
> At 09:40 AM 2/28/2009, Andrei Brezan wrote:
>
>> Hello list,
>>
>>I have a strange problem and I don't know what to relate it to. My
>> ISP
>> changed my IP from (eg) 10.1.1.1 to 15.1.1.1. I have chang
At 09:40 AM 2/28/2009, Andrei Brezan wrote:
Hello list,
I have a strange problem and I don't know what to relate it to.
My ISP
changed my IP from (eg) 10.1.1.1 to 15.1.1.1. I have changed my zone
files to reflect that change.
"dig -t mx domain.com" results in mail.domain.com 3600 IN A
On Saturday 28 February 2009 07:43:13 Andrei Brezan wrote:
> Andrei Brezan wrote:
> > "ping mail.domain.com" it tries to get to 10.1.1.1 the old ip and gets
> > time to live exceeded fro an ip along the route. When i try to ping
> > domain.com it gets all ok as it pings the new ip.
> Disregard my
Andrei Brezan wrote:
> Hello list,
>
> I have a strange problem and I don't know what to relate it to. My ISP
> changed my IP from (eg) 10.1.1.1 to 15.1.1.1. I have changed my zone
> files to reflect that change.
>
> "dig -t mx domain.com" results in mail.domain.com 3600 IN A 15.1.1.1
> (th
Hello list,
I have a strange problem and I don't know what to relate it to. My ISP
changed my IP from (eg) 10.1.1.1 to 15.1.1.1. I have changed my zone
files to reflect that change.
"dig -t mx domain.com" results in mail.domain.com 3600 IN A 15.1.1.1
(the new ip). However when i try:
"pi
On 7/20/06, DSA - JCR <[EMAIL PROTECTED]> wrote:
Hi all again
I have changed the IP with ifconfig and tested it and rebooted my FreeBSD
6.1 amd64 box, but I have errors when I reboot. This are:
-sm-mta[490]:NOQUEUE: SYSERR(root): opendaemon socket
- daemon0: cannot bind: can't assign requested
Hi all again
I have changed the IP with ifconfig and tested it and rebooted my FreeBSD
6.1 amd64 box, but I have errors when I reboot. This are:
-sm-mta[490]:NOQUEUE: SYSERR(root): opendaemon socket
- daemon0: cannot bind: can't assign requested address
- problem creating SMT (error lines overla
On Wed, Jul 28, 2004 at 03:48:17PM +, Daniela wrote:
> On Wednesday 28 July 2004 14:49, Steve Bertrand wrote:
> > >> Also, post the relevant ``natd'' line entries in your /etc/natd.conf
> > >> file.
> > >
> > > natd.conf doesn't exist. Do you mean rc.conf? Here it is:
> > > natd_interface="rl0"
> On Wednesday 28 July 2004 16:18, Steve Bertrand wrote:
>> > On Wednesday 28 July 2004 15:53, Steve Bertrand wrote:
>> >> >> I figured so...what happens if you add 'keep-state' to rules
>> 2,
>> >> >> 20002
>> >> >> and 20003?
>> >> >
>> >> > Nothing.
>> >> > BTW, here we have the problem: The
On Wednesday 28 July 2004 16:18, Steve Bertrand wrote:
> > On Wednesday 28 July 2004 15:53, Steve Bertrand wrote:
> >> >> I figured so...what happens if you add 'keep-state' to rules 2,
> >> >> 20002
> >> >> and 20003?
> >> >
> >> > Nothing.
> >> > BTW, here we have the problem: The initial SYN
> On Wednesday 28 July 2004 15:53, Steve Bertrand wrote:
>> >> I figured so...what happens if you add 'keep-state' to rules 2,
>> >> 20002
>> >> and 20003?
>> >
>> > Nothing.
>> > BTW, here we have the problem: The initial SYN packet isn't matched by
>> > rule
>> > 11700 (setup keep-state). Set
On Wednesday 28 July 2004 15:53, Steve Bertrand wrote:
> >> I figured so...what happens if you add 'keep-state' to rules 2,
> >> 20002
> >> and 20003?
> >
> > Nothing.
> > BTW, here we have the problem: The initial SYN packet isn't matched by
> > rule
> > 11700 (setup keep-state). Setup means t
> On Wednesday 28 July 2004 15:23, Steve Bertrand wrote:
>> > Yes, it works, but of course I can't leave this rule in all the time.
>>
>> The SYN/ACK packet that comes back from the remote server is denied by
>> rule
>>
>> > 01900. But it should be allowed by the check-state rule.
>> >
>> >> Also,
On Wednesday 28 July 2004 15:23, Steve Bertrand wrote:
> > Yes, it works, but of course I can't leave this rule in all the time.
>
> The SYN/ACK packet that comes back from the remote server is denied by
> rule
>
> > 01900. But it should be allowed by the check-state rule.
> >
> >> Also, I know you
> On Wednesday 28 July 2004 15:06, Steve Bertrand wrote:
>> > On Wednesday 28 July 2004 14:49, Steve Bertrand wrote:
>> >> >> Also, post the relevant ``natd'' line entries in your
>> /etc/natd.conf
>> >> >> file.
>> >> >
>> >> > natd.conf doesn't exist. Do you mean rc.conf? Here it is:
>> >> > natd
On Wednesday 28 July 2004 15:06, Steve Bertrand wrote:
> > On Wednesday 28 July 2004 14:49, Steve Bertrand wrote:
> >> >> Also, post the relevant ``natd'' line entries in your /etc/natd.conf
> >> >> file.
> >> >
> >> > natd.conf doesn't exist. Do you mean rc.conf? Here it is:
> >> > natd_interface=
> On Wednesday 28 July 2004 14:49, Steve Bertrand wrote:
>> >> Also, post the relevant ``natd'' line entries in your /etc/natd.conf
>> >> file.
>> >
>> > natd.conf doesn't exist. Do you mean rc.conf? Here it is:
>> > natd_interface="rl0"
>> > natd_enable="YES"
>> >
>> > But I didn't change anything
On Wednesday 28 July 2004 14:49, Steve Bertrand wrote:
> >> Also, post the relevant ``natd'' line entries in your /etc/natd.conf
> >> file.
> >
> > natd.conf doesn't exist. Do you mean rc.conf? Here it is:
> > natd_interface="rl0"
> > natd_enable="YES"
> >
> > But I didn't change anything here, and
On Wednesday 28 July 2004 14:38, Steve Bertrand wrote:
> >> Do you have an ``alias_address'' statement in your natd.conf file?
> >
> > I have no natd.conf file. At least I never touched it. But it always
> > worked
> > like a dream. BTW, natd is started with the command line "natd -n rl0".
>
> Also
> On Wednesday 28 July 2004 14:36, Steve Bertrand wrote:
>> >> Do you have an ``alias_address'' statement in your natd.conf file?
>> >
>> > I have no natd.conf file. At least I never touched it. But it always
>> > worked
>> > like a dream. BTW, natd is started with the command line "natd -n
>> rl0"
On Wednesday 28 July 2004 14:36, Steve Bertrand wrote:
> >> Do you have an ``alias_address'' statement in your natd.conf file?
> >
> > I have no natd.conf file. At least I never touched it. But it always
> > worked
> > like a dream. BTW, natd is started with the command line "natd -n rl0".
>
> Try
> On Wednesday 28 July 2004 14:21, Steve Bertrand wrote:
>> >> Did you actually change the IP on the interface itself? If not:
>> >>
>> >> edit /etc/rc.conf and change the IP/Netmask, then:
>> >>
>> >> # /etc/netstart
>> >
>> > Yes, the IP was changed. I ran /etc/netstart, but it didn't help. As I
>> Do you have an ``alias_address'' statement in your natd.conf file?
>
> I have no natd.conf file. At least I never touched it. But it always
> worked
> like a dream. BTW, natd is started with the command line "natd -n rl0".
Try shutting down natd and load it with:
# natd -a x.x.x.x
where x.x.
On Wednesday 28 July 2004 14:27, Hauan, David wrote:
> > >> Did you actually change the IP on the interface itself? If not:
> > >>
> > >> edit /etc/rc.conf and change the IP/Netmask, then:
> > >>
> > >> # /etc/netstart
> > >
> > > Yes, the IP was changed. I ran /etc/netstart, but it didn't
> >
> >
On Wednesday 28 July 2004 14:21, Steve Bertrand wrote:
> >> Did you actually change the IP on the interface itself? If not:
> >>
> >> edit /etc/rc.conf and change the IP/Netmask, then:
> >>
> >> # /etc/netstart
> >
> > Yes, the IP was changed. I ran /etc/netstart, but it didn't help. As I
> > said,
> -Original Message-
> From: Steve Bertrand [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 28, 2004 7:22 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: Problems after IP change
>
>
> > On Wednesday 28 July 2004 14:03, Steve
> On Wednesday 28 July 2004 14:03, Steve Bertrand wrote:
>> > Hi all!
>> >
>> > I recently got a new IP on my outside interface, and I replaced the
>> old
>> > IP with the new one in my IPFW ruleset, and restarted natd.
>> > Now everything was alright until my network clients (on the inside
>> > in
On Wednesday 28 July 2004 14:03, Steve Bertrand wrote:
> > Hi all!
> >
> > I recently got a new IP on my outside interface, and I replaced the old
> > IP with the new one in my IPFW ruleset, and restarted natd.
> > Now everything was alright until my network clients (on the inside
> > interface)
>
> Hi all!
>
> I recently got a new IP on my outside interface, and I replaced the old IP
> with the new one in my IPFW ruleset, and restarted natd.
> Now everything was alright until my network clients (on the inside
> interface)
> started complaining that they can't connect to remote servers. Ping
Hi all!
I recently got a new IP on my outside interface, and I replaced the old IP
with the new one in my IPFW ruleset, and restarted natd.
Now everything was alright until my network clients (on the inside interface)
started complaining that they can't connect to remote servers. Ping still
wor
In the last episode (Oct 14), Edward Aronyk said:
> I'm somewhat new to FreeBSD, so today when we had to deploy a new
> server to the colo running FreeBSD, I ran into problems.
>
> Basically the server has been in the office running for the last few
> weeks with a DHCP provided IP - but now that i
For the gateway, from the command line as root:
# route add default (ip address of gateway)
you can also configure the networking (as root)from /stand/sysinstall
#/stand/sysinstall
select Configure
select Networking
Follow the prompts from there.
Tim Kellers
CPE/NJIT
On Tue, 14 Oct 2003, Edw
Good day all,
I'm somewhat new to FreeBSD, so today when we had to deploy a new server
to the colo running FreeBSD, I ran into problems.
Basically the server has been in the office running for the last few
weeks with a DHCP provided IP - but now that it's getting a static IP
I'm not totally sure
On Wed, Feb 19, 2003 at 09:43:58AM +, Mark wrote:
>
> I made a DNS change, more than a week ago, changing the IP address of my
> primary domain name. But I still get the FreeBSD list on the old IP. So, who
> do I talk to at FreeBSD to have them update their DNS cache? :)
I'm sure that happens
> Most of the times, when you make a DNS change, it may take up 24 hours
> to replicate to all other servers.
> And during that time is when, you wonder if it's gonna work or not. On
> top of that your carrier may not refresh it's list every 6 to 12 hours.
> I had to talk to a supervisor to have AT
T&T do the refresh it right away.
- Original Message -
From: "Mark" <[EMAIL PROTECTED]>
To: "Giorgos Keramidas" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, February 20, 2003 7:48 AM
Subject: Re: IP-change
> - Ori
U, sorry to intrude on the thread Mark and Giorgos, but does anyone
know why each email to this list arrives in duplicate?? Not that I mind
'cos it's double the BSD goodness...but merely curious is all.
Regards to all,
-Colin
+> > On 2003-02-20 04:30, Mark <[EMAIL PROTECTED]> wrote:
+> > > Gi
- Original Message -
From: "Giorgos Keramidas" <[EMAIL PROTECTED]>
To: "Mark" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, February 20, 2003 2:12 PM
Subject: Re: IP-change
> On 2003-02-20 04:30, Mark <[EMAIL PROTECTED]>
On 2003-02-20 04:30, Mark <[EMAIL PROTECTED]> wrote:
> Giorgos Keramidas <[EMAIL PROTECTED]> wrote:
> > This is more likely to be a setup problem on your end,
>
> Well, the rest of the world has no problem with it. :) All mail
> servers around the globe I receive mail from, picked up on the DNS
> c
- Original Message -
From: "Giorgos Keramidas" <[EMAIL PROTECTED]>
To: "Mark" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, February 19, 2003 5:58 PM
Subject: Re: IP-change
> On 2003-02-19 09:43, Mark <[EMAIL PROTECTED]>
On 2003-02-19 09:43, Mark <[EMAIL PROTECTED]> wrote:
> This may not be the entirely proper location to ask, but private
> questions to the FreeBSD mailing list contacts have not resulted in
> a response. So, let me ask here.
This is more likely to be a setup problem on your end, so the list is
the
This may not be the entirely proper location to ask, but private questions
to the FreeBSD mailing list contacts have not resulted in a response. So,
let me ask here.
I made a DNS change, more than a week ago, changing the IP address of my
primary domain name. But I still get the FreeBSD list on th
Hello,
I recently changed my ISP - DSL provider, a new static IP, and now
having problems ssh'ing in, none before.
My config ==>
ISP[DSL]
|
Modem
|
Router/Gateway
|
==> HubLAN machine(1)
|LAN machine(2)
|
|LAN machine(n)
The LAN si
43 matches
Mail list logo
