Topic: Strange problem with SME 5.5 and 5.6

[Daniel]

My problem is solved!

At installation time I use 192.168.0.0 as server IP. Now I changed the configuration to default and the Win ME clients are working like magic.

It seems to be a problem of ME...

[Nuke]

Thank you, Paul.  I have answered as best as I can below.

Paul wrote:
>
> Is eth0 your internal nic (default setup) or have you got
> them switched in the configuration so that eth1 is your
> interanl?

Yes, about a year ago, I had to switch the set-up because in the auto-configuration or auto-discovery, the sme always finds the NIC card that I want to use as external first.  So eth0 is the external, eth1 is internal.

>
> What brand and model is the ADSL?

It is actually a cable modem.  It is an Ericsson Piperider HM200c.
 
> Is your ADSL set as a bridge or a router with nat inabled
> (hardware firewall)?

I am using the sme as the gateway server.  So if I understand correctly, the sme is my router.  I assume that the modem is a bridge then.  Not sure what a "bridge" means in this context.
 
> Do you have a static or dynamic IP address from your ISP?

I have a dynamic IP address from the ISP
 
> Have you switched your nic cards around?

Yes.  The nic hardwired into the server died and I had to add a new PCI nic card.  This new nic card is supposed to be the internal nic but the sme always discovers it first so I have had to switch them while in the configuration menu.  After I get past the initial 1-2 weeks from a clean install and upgrade, I don't have any problems with this.  I also didn't have any problems running this configuration under sme 5.1.x
 
> Are you using the right kind of connection for your ISP
> (DHCP, PPPoE, Static)?  (This may be where your problem is if
> you are behind a firewall.)

Yes, the ISP wants us to use DHCP.
 
> If you are behind a hardware firewall (your ADSL "modem" may
> act as a firewall), then you will need to change you settings
> accordingly.

No, I don't think the modem is acting as a firewall.  Maybe the ISP does do this, I don't know.  I have tried to understand the DOCSIS standard so I might figure out if my ISP is blocking some ports locally or at the head end.  Unfortunately, I am still a sme hobbiest and so the DOCSIS technical guides are beyond my capacity.

To reiterate, the problems that I am experiencing with the sme losing the external connection only seemed to happen after the clean install and for a week after.  Then for what ever reason, it works flawlessly.  I don't change anything after I have made the initial configuration except perhaps to turn on/off ssh access.
 
> Answer these questions and I might have a couple more.
>
> Best wishes,
> Paul

Thanks again, Paul.  I appreciate any help you or anyone can provide.  I realize that some of these questions or issues might be a no brainer for you guys.  I am learning as I go.  The sme is really excellent.

Nuke

[Paul]

>At installation time I use 192.168.0.0 as server IP. Now I changed the
>cnfiguration to default and the Win ME clients are working like magic.

>It seems to be a problem of ME...

This would explain your reason, x.x.x.0 and x.x.x.255 are not a vaible addresses for any nic.

Great to see your problem fixed, now let's see what we can do for nuke.

Paul

[Paul]

>It is actually a cable modem. It is an Ericsson Piperider HM200c.

Now this is a different story here.

Nuke, You wouldn't happen to be on attbi or comcast would you?

I have had the same problem and here is what I have found,  attbi/comcast (and probably other cable providers) use the nic's MAC address as your id to them.  I changed routers a couple of times (before installing SME as the router/gateway) and it created all kinds of hell.  Now I "cloan" the mac address of the original nic card that the cable company gave me.  I even had to cloan the MAC address on my Linksys router for it to work correctly.

I just removed the cable router from my setup and before I put my SME machine as the new firewall I "cloaned" the nic to the "old" MAC address.  It worked flawlessly but I knew to change the MAC address beforehand.

When I was having simular problems, I didn't even have an SME server.  I was using Linksys cable/dsl routers.  some cable "modems" don't have a MAC address, it passes the ip address directly to the comp or router hooked to the "modem".  do the following from the command prompt:

ifconfig

see what the ip addresses are on each nic and report back to me.  You might want to write down the external nic's MAC address for future reference.

[Daniel]

> This would explain your reason, x.x.x.0 and x.x.x.255 are not
> a vaible addresses for any nic.

Crazy, why does it work with Win XP. Computers are more then strange


> Great to see your problem fixed, now let's see what we can do
> for nuke.

I think, nuke's logfile is describing an network card error, maybe a hardware problem.

Is a cable-modem like a dedicated line? Or does it require PPPOE? If the identification of the user is made with the help of the MAC address of the network card then it schouldn't work at anytime. So, why does it work with SME 5.1.x and sometimes not with SME 5.5/5.6? I'm sorry, but I have no idea.

[Nuke]

Hi Paul, and thank you again.  My answers are below.

BTW, since about 1:30 pm yesterday, my sme seems to be working OK again.  I haven't a clue what happened to fix this but it seems to be working.  I haven't lost the external internet connection since then.

I would like to understand this problem so I can determine exactly why it happened and what to do in the future.  My answers are below

Paul wrote:
>
> >It is actually a cable modem. It is an Ericsson Piperider
> HM200c.
>
> Now this is a different story here.
>
> Nuke, You wouldn't happen to be on attbi or comcast would you?

No I am on Cogeco.

> I have had the same problem and here is what I have found,
> attbi/comcast (and probably other cable providers) use the
> nic's MAC address as your id to them.  I changed routers a
> couple of times (before installing SME as the router/gateway)
> and it created all kinds of hell.  Now I "cloan" the mac
> address of the original nic card that the cable company gave
> me.  I even had to cloan the MAC address on my Linksys router
> for it to work correctly.

Yes, the cable provider does use the MAC address.  It should be the external pointing nic card. When I switched from the direct connect to my Mac to the sme, the cable provider told me I had to keep the sme disconnected for about 20 min. so that when I restarted, it would pick-up the new MAC address of the new nic card.  This actually worked.

Darn, could that be it?  Because I did a clean install, could the sme lose the MAC address?  Then the ISP would think that the sme isn't the correct connection and kill the internet link?  Is this possible?
 
> I just removed the cable router from my setup and before I
> put my SME machine as the new firewall I "cloaned" the nic to
> the "old" MAC address.  It worked flawlessly but I knew to
> change the MAC address beforehand.

What is 'cloaned' the nic to the MAC address mean?  I presume that you are loaning the MAC address to the new nic.  Is this correct?  How do you do that?

> When I was having simular problems, I didn't even have an SME
> server.  I was using Linksys cable/dsl routers.  some cable
> "modems" don't have a MAC address, it passes the ip address
> directly to the comp or router hooked to the "modem".  do the
> following from the command prompt:
>
> ifconfig

Here goes:
eth0      Link encap:Ethernet  HWaddr 00:04:5A:78:CB:2D  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          EtherTalk Phase 2 addr:65280/145
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13109 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:20534 dropped:0 overruns:0 carrier:41064
          collisions:0
          RX bytes:1451830 (1.3 Mb)  TX bytes:0 (0.0 b)

eth1      Link encap:Ethernet  HWaddr 00:80:5F:26:12:AE  
          inet addr:24.141.xxx.xxx  Bcast:255.255.255.255  Mask:255.255.240.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:829270 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11692 errors:0 dropped:0 overruns:0 carrier:0
          collisions:338
          RX bytes:70022349 (66.7 Mb)  TX bytes:1266260 (1.2 Mb)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          EtherTalk Phase 2 addr:0/0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:365 errors:0 dropped:0 overruns:0 frame:0
          TX packets:365 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:109424 (106.8 Kb)  TX bytes:109424 (106.8 Kb)

>
> see what the ip addresses are on each nic and report back to
> me.  You might want to write down the external nic's MAC
> address for future reference.

It looks like I made a mistake on my earlier posts.  Looks like eth0 is internal and eth1 is external, like the default.  I could have sworn it was the other way around.

Mmmmmh.  Is the MAC address the HWaddr?

Thanks again
Nuke

[Daniel]

> It looks like I made a mistake on my earlier posts.  Looks
> like eth0 is internal and eth1 is external, like the
> default.  I could have sworn it was the other way around.
>
> Mmmmmh.  Is the MAC address the HWaddr?

Yes, your eth1 is external. And yes, the HWaddr is your MAC address. So the HWaddr of eth1 must be successfully registered at your provider (however it will be registered ).

A MAC address is unique and your SME couldn't change it. But if you swapped eth0 and eth1 with the fresh install of SME then your server goes with the wrong MAC address online.

[Nuke]

Thank you Daniel and Paul.

I'll make a note of the MAC address and check next time I make an update.  

Can you direct me to info about the 'cloan' or 'cloaned'?

Cheers and thanks
Nuke

[Birger Koopmann]

We have had a lot of problems with Realtech-chipset-NICs. It sems they give problems if used in an server for the internal (faster) network. It makes the netconnections hang on heavy loads. On the external side of the server (slover), we had no problems with these cards. Try flipping the cards.

[Paul]

>A MAC address is unique and your SME couldn't change it. But if you swapped >eth0 and eth1 with the fresh install of SME then your server goes with the wrong >MAC address online

A MAC address is unique to a piece of hardware BUT you can tell the machine to use a different one if needed.

It seems that you might have been swapping nic cards and MAC addresses when connecting to your ISP.  This will cause all kinds of problems.

To change or "cloan" your MAC address you will have to make a custom template and assign the mac address that you want to the nic.  Don't bother trying to change it back now that it seems your current eth1 is registered with your ISP.  But in the future, if you have to change nic's you will need to know how to assign the MAC address to the nic if necessary.  

I will put together a small how-to and post it here in the next couple of days if one does not allready exist.  This will be helpful to anyone with a cable modem as this seems to be a common problem with cable service.  Linksys updated their firmware to include MAC cloaning for this very reason about 1 year ago.

One more thing, if you have set up your machine to switch eth0 and eth1 then you are going to have more problems because your cards are connected wrong.  Let's doublecheck your setup.

1-Log on to your server at the server or thru a ssh terminal as admin to bring up the server console (NOT the web browser server-manager).

2-Arrow down to #3 Review Configuration and see if the "Ethernet Assignment" is norrmal or swapped.

We need to make sure you have everything connected right.  DO NOT change anything just yet or you will loose your MAC registration at your ISP and you will have to start all over with a bad connection...

[Nuke]

Hi Paul et al.

thanks for the help. I have answered below.

Paul wrote:
...cut...
> I will put together a small how-to and post it here in the
> next couple of days if one does not allready exist.  This
> will be helpful to anyone with a cable modem as this seems to
> be a common problem with cable service.  Linksys updated
> their firmware to include MAC cloaning for this very reason
> about 1 year ago.
 
I look forward to reading this HowTo.  Please let me know when you post it.

> One more thing, if you have set up your machine to switch
> eth0 and eth1 then you are going to have more problems
> because your cards are connected wrong.  Let's doublecheck
> your setup.
...
> 2-Arrow down to #3 Review Configuration and see if the
> "Ethernet Assignment" is norrmal or swapped.

It looks OK.  Tlan is external (eth1) ethernet driver 2, Linksys (eth0) is internal, ethernet driver 1.  The menu doesn't indicate switched but after going and checking the physical connection, it looks to be correct.

> We need to make sure you have everything connected right.  DO
> NOT change anything just yet or you will loose your MAC
> registration at your ISP and you will have to start all over
> with a bad connection...

Thanks again.  The sme seems to have stabilized.  It has been running 1 day 6 hours ++ without incident. Now to get hylafax running.....

[Paul]

I know I've seen this HOW-TO somewhere but I just can't locate it so here is my first attempt at a HOW-TO.

This will "cloan" the MAC address on ethX with the desired MAC address (replace X with 0 or 1 depending on your needs).

Make a directory for your new template:

# mkdir -p /etc/e-smith/templates-custom/etc/sysconfig/network-scripts/ifcfg-ethX

Change to the directory just created:

# cd /etc/e-smith/templates-custom/etc/sysconfig/network-scripts/ifcfg-ethX

Create your custom template

# pico 10macaddress

Type the following in the template replacing XX:XX:XX:XX:XX:XX with your desired MAC address.

MACADDR=XX:XX:XX:XX:XX:XX

Then press CTRL-O to write the file and CTRL-X to exit.

Then expand the template to rewrite ifcfg-ethX

# /sbin/e-smith/expand-template etc/sysconfig/network-scripts/ifcfg-ethX

At this point you should be able to shut down and restart the network.  Unfortuanatly I couldn't get that to work for me so I had to reboot.  

# /sbin/e-smith/signal-event reboot

Now check you with ifconfig and see if your MAC address is now cloaned.

[Nuke]

Paul et. al.

It started again.  More problems with the SME losing its external IP address.

I think I may have an idea about why it is happening.  But, since I am still learning, I'm not 100% sure. Could you perhaps answer some more questions and help me?  Even if my supposition is correct, I don't know what to do to fix this exept perhaps to reboot.

Here is what I think is happening.  (my interpretation of log)

I think that the ISP has changed my IP address.  I think the SME doesn't want to accept the new IP address and is trying to connect to the old IP address.  Is this correct?

The SME tries to get its' old IP address, calls DYNDNS to update the old IP, after trying a number of times, the SME gives a system error and the Internet connection is terminated.

It started last night around 1am.  I have put the first part of the log.  This part repeated itself every hour until 10 am when the external IP was lost and the system error starts.  The last part of the log is found after the comment: Then this and the system error.

What exactly is happening and how do I ensure it doesn't happen again.

Mar 29 01:12:13 main syslogd 1.4.1: restart.
Mar 29 01:12:13 main e-smith[29506]: S65reload-syslogd=action|Event|logrotate|Action|S65reload-syslogd|Start|1048918332 234264|End|1048918333 500781|Elapsed|1.266517
Mar 29 01:12:13 main e-smith[29506]: Running event handler: /etc/e-smith/events/logrotate/S65restart-httpd-graceful
Mar 29 01:12:14 main e-smith[29506]: S65restart-httpd-graceful=action|Event|logrotate|Action|S65restart-httpd-graceful|Start|1048918333 501469|End|1048918334 694522|Elapsed|1.193053
Mar 29 01:12:14 main e-smith[29506]: Running event handler: /etc/e-smith/events/logrotate/S70reload-httpd-admin
Mar 29 01:12:17 main httpd-e-smith: httpd -USR1 succeeded
Mar 29 01:12:18 main e-smith[29506]: S70reload-httpd-admin=action|Event|logrotate|Action|S70reload-httpd-admin|Start|1048918334 695230|End|1048918338 478831|Elapsed|3.783601
Mar 29 01:12:18 main e-smith[29506]: Running event handler: /etc/e-smith/events/logrotate/S75purge-old-logs
Mar 29 01:12:19 main e-smith[29506]: S75purge-old-logs=action|Event|logrotate|Action|S75purge-old-logs|Start|1048918338 479502|End|1048918339 275122|Elapsed|0.79562
Mar 29 01:12:20 main httpd-admin: httpd-admin -USR1 succeeded
Mar 29 01:12:20 main e-smith-bg: Gracefully reloading e-smith httpd-admin: [   OK   ]^M
Mar 29 01:12:22 main e-smith-bg: Gracefully reloading httpd: [   OK   ]^M
Mar 29 01:40:39 main dhcpcd[1021]: sending DHCP_REQUEST for 24.144.xxx.xxx to 24.144.yyy.yyy
Mar 29 01:40:39 main dhcpcd[1021]: DHCP_ACK received from  (24.144.yyy.yyy)
Mar 29 02:10:39 main dhcpcd[1021]: sending DHCP_REQUEST for 24.144.xxx.xxx to 24.144.yyy.yyy
Mar 29 02:33:09 main dhcpcd[1021]: broadcasting DHCP_REQUEST for 24.144.xxx.xxx
Mar 29 02:40:39 main dhcpcd[1021]: broadcasting DHCP_DISCOVER
Mar 29 02:40:39 main kernel: TLAN: eth1: Starting autonegotiation.
Mar 29 02:40:39 main e-smith[29599]: Processing event: ip-change 24.144.xxx.xxx
Mar 29 02:40:39 main e-smith[29599]: Running event handler: /etc/e-smith/events/ip-change/S15set-external-ip
Mar 29 02:40:40 main e-smith[29599]: S15set-external-ip=action|Event|ip-change|Action|S15set-external-ip|Start|1048923639 522244|End|1048923640 683186|Elapsed|1.160942
Mar 29 02:40:40 main e-smith[29599]: Running event handler: /etc/e-smith/events/ip-change/S16adjust-masq
Mar 29 02:40:41 main kernel: TLAN:  Giving autonegotiation more time.
Mar 29 02:40:41 main kernel: TLAN:  Please check that your adapter has
Mar 29 02:40:41 main kernel: TLAN:  been properly connected to a HUB or Switch.
Mar 29 02:40:41 main kernel: TLAN:  Trying to establish link in the background...
Mar 29 02:40:43 main e-smith[29599]: S16adjust-masq=action|Event|ip-change|Action|S16adjust-masq|Start|1048923640 683932|End|1048923643 402115|Elapsed|2.718183
Mar 29 02:40:43 main e-smith[29599]: Running event handler: /etc/e-smith/events/ip-change/S47proftpd-conf
Mar 29 02:40:46 main e-smith[29599]: S47proftpd-conf=action|Event|ip-change|Action|S47proftpd-conf|Start|1048923643 402794|End|1048923646 89423|Elapsed|2.686629
Mar 29 02:40:46 main e-smith[29599]: Running event handler: /etc/e-smith/events/ip-change/S50conf-security
Mar 29 02:40:49 main kernel: TLAN: eth1: Autonegotiation complete.
Mar 29 02:40:49 main kernel: TLAN:  Starting internal PHY with HALF-DUPLEX
Mar 29 02:40:49 main kernel: TLAN: eth1: Link active
Mar 29 02:40:49 main e-smith[29599]: S50conf-security=action|Event|ip-change|Action|S50conf-security|Start|1048923646 90166|End|1048923649 469241|Elapsed|3.379075
Mar 29 02:40:49 main e-smith[29599]: Running event handler: /etc/e-smith/events/ip-change/S80pptpd-conf
Mar 29 02:40:50 main e-smith[29599]: S80pptpd-conf=action|Event|ip-change|Action|S80pptpd-conf|Start|1048923649 469918|End|1048923650 624530|Elapsed|1.154612
Mar 29 02:40:50 main e-smith[29599]: Running event handler: /etc/e-smith/events/ip-change/S85update-dns
Mar 29 02:40:51 main dhcpcd[1021]: dhcpT1value option is missing in DHCP server response. Assuming 1800 sec
Mar 29 02:40:51 main dhcpcd[1021]: dhcpT2value option is missing in DHCP server response. Assuming 3150 sec
Mar 29 02:40:51 main dhcpcd[1021]: broadcasting second DHCP_DISCOVER
Mar 29 02:40:51 main dhcpcd[1021]: DHCP_OFFER received from  (24.144.yyy.yyy)
Mar 29 02:40:51 main dhcpcd[1021]: broadcasting DHCP_REQUEST for 24.144.xxx.xxx
Mar 29 02:40:51 main dhcpcd[1021]: DHCP_ACK received from  (24.144.yyy.yyy)
Mar 29 02:40:52 main e-smith[29698]: Processing event: ip-change 24.144.xxx.xxx
Mar 29 02:40:52 main e-smith[29698]: Running event handler: /etc/e-smith/events/ip-change/S15set-external-ip
Mar 29 02:40:52 main dyndns.org: IP Address 24.144.xxx.xxx already in database.
Mar 29 02:40:52 main e-smith[29599]: S85update-dns=action|Event|ip-change|Action|S85update-dns|Start|1048923650 625197|End|1048923652 912128|Elapsed|2.286931
Mar 29 02:40:52 main e-smith[29599]: Running event handler: /etc/e-smith/events/ip-change/S90pptpd-restart
Mar 29 02:40:53 main e-smith[29599]: S90pptpd-restart=action|Event|ip-change|Action|S90pptpd-restart|Start|1048923652 912800|End|1048923653 133475|Elapsed|0.220675
Mar 29 02:40:53 main e-smith[29599]: Running event handler: /etc/e-smith/events/ip-change/S90restart-ntpd
Mar 29 02:40:54 main e-smith[29698]: S15set-external-ip=action|Event|ip-change|Action|S15set-external-ip|Start|1048923652 80904|End|1048923654 501636|Elapsed|2.420732
Mar 29 02:40:54 main e-smith[29698]: Running event handler: /etc/e-smith/events/ip-change/S16adjust-masq
Mar 29 02:40:55 main e-smith[29599]: S90restart-ntpd=action|Event|ip-change|Action|S90restart-ntpd|Start|1048923653 134985|End|1048923655 336483|Elapsed|2.201498
Mar 29 02:40:55 main dhcpcd[1021]: sending DHCP_REQUEST for 24.144.xxx.xxx to 24.144.yyy.yyy
Mar 29 02:40:55 main dhcpcd[1021]: DHCP_ACK received from  (24.144.yyy.yyy)
Mar 29 02:40:56 main ntpd: ntpd shutdown failed
Mar 29 02:40:56 main e-smith-bg: Shutting down ntpd: [ FAILED ]^M
Mar 29 02:40:58 main e-smith[29698]: S16adjust-masq=action|Event|ip-change|Action|S16adjust-masq|Start|1048923654 502383|End|1048923658 608473|Elapsed|4.10609
Mar 29 02:40:58 main e-smith[29698]: Running event handler: /etc/e-smith/events/ip-change/S47proftpd-conf
Mar 29 02:41:01 main e-smith[29698]: S47proftpd-conf=action|Event|ip-change|Action|S47proftpd-conf|Start|1048923658 609161|End|1048923661 276471|Elapsed|2.66731
Mar 29 02:41:01 main e-smith[29698]: Running event handler: /etc/e-smith/events/ip-change/S50conf-security
Mar 29 02:41:04 main e-smith[29698]: S50conf-security=action|Event|ip-change|Action|S50conf-security|Start|1048923661 277149|End|1048923664 595713|Elapsed|3.318564
Mar 29 02:41:04 main e-smith[29698]: Running event handler: /etc/e-smith/events/ip-change/S80pptpd-conf
Mar 29 02:41:05 main e-smith[29698]: S80pptpd-conf=action|Event|ip-change|Action|S80pptpd-conf|Start|1048923664 596409|End|1048923665 755934|Elapsed|1.159525
Mar 29 02:41:05 main e-smith[29698]: Running event handler: /etc/e-smith/events/ip-change/S85update-dns
Mar 29 02:41:07 main dyndns.org: IP Address 24.144.xxx.xxx already in database.
Mar 29 02:41:07 main e-smith[29698]: S85update-dns=action|Event|ip-change|Action|S85update-dns|Start|1048923665 756613|End|1048923667 141352|Elapsed|1.384739
Mar 29 02:41:07 main e-smith[29698]: Running event handler: /etc/e-smith/events/ip-change/S90pptpd-restart
Mar 29 02:41:07 main e-smith[29698]: S90pptpd-restart=action|Event|ip-change|Action|S90pptpd-restart|Start|1048923667 142020|End|1048923667 426725|Elapsed|0.284705
Mar 29 02:41:07 main e-smith[29698]: Running event handler: /etc/e-smith/events/ip-change/S90restart-ntpd
Mar 29 02:41:08 main e-smith[29698]: S90restart-ntpd=action|Event|ip-change|Action|S90restart-ntpd|Start|1048923667 428241|End|1048923668 604769|Elapsed|1.176528
Mar 29 02:41:08 main dhcpcd[1021]: sending DHCP_REQUEST for 24.144.xxx.xxx to 24.144.yyy.yyy
Mar 29 02:41:08 main dhcpcd[1021]: DHCP_ACK received from  (24.144.yyy.yyy)

----

Then this and the system error

Mar 29 08:12:09 main dhcpcd[1021]: sending DHCP_REQUEST for 24.144.xxx.xxx to 24.144.yyy.yyy
Mar 29 08:34:39 main dhcpcd[1021]: broadcasting DHCP_REQUEST for 24.144.xxx.xxx
Mar 29 08:42:09 main dhcpcd[1021]: broadcasting DHCP_DISCOVER
Mar 29 08:42:10 main kernel: TLAN: eth1: Starting autonegotiation.
Mar 29 08:42:10 main e-smith[30720]: Processing event: ip-change 24.144.xxx.xxx
Mar 29 08:42:10 main e-smith[30720]: Running event handler: /etc/e-smith/events/ip-change/S15set-external-ip
Mar 29 08:42:11 main e-smith[30720]: S15set-external-ip=action|Event|ip-change|Action|S15set-external-ip|Start|1048945330 364032|End|1048945331 519051|Elapsed|1.155019
Mar 29 08:42:11 main e-smith[30720]: Running event handler: /etc/e-smith/events/ip-change/S16adjust-masq
Mar 29 08:42:12 main kernel: TLAN:  Giving autonegotiation more time.
Mar 29 08:42:12 main kernel: TLAN:  Please check that your adapter has
Mar 29 08:42:12 main kernel: TLAN:  been properly connected to a HUB or Switch.
Mar 29 08:42:12 main kernel: TLAN:  Trying to establish link in the background...
Mar 29 08:42:14 main e-smith[30720]: S16adjust-masq=action|Event|ip-change|Action|S16adjust-masq|Start|1048945331 519783|End|1048945334 216254|Elapsed|2.696471
Mar 29 08:42:14 main e-smith[30720]: Running event handler: /etc/e-smith/events/ip-change/S47proftpd-conf
Mar 29 08:42:16 main e-smith[30720]: S47proftpd-conf=action|Event|ip-change|Action|S47proftpd-conf|Start|1048945334 216919|End|1048945336 917855|Elapsed|2.700936
Mar 29 08:42:16 main e-smith[30720]: Running event handler: /etc/e-smith/events/ip-change/S50conf-security
Mar 29 08:42:20 main kernel: TLAN: eth1: Autonegotiation complete.
Mar 29 08:42:20 main kernel: TLAN:  Starting internal PHY with HALF-DUPLEX
Mar 29 08:42:20 main kernel: TLAN: eth1: Link active
Mar 29 08:42:20 main e-smith[30720]: S50conf-security=action|Event|ip-change|Action|S50conf-security|Start|1048945336 918533|End|1048945340 378880|Elapsed|3.460347
Mar 29 08:42:20 main e-smith[30720]: Running event handler: /etc/e-smith/events/ip-change/S80pptpd-conf
Mar 29 08:42:21 main e-smith[30720]: S80pptpd-conf=action|Event|ip-change|Action|S80pptpd-conf|Start|1048945340 379552|End|1048945341 541935|Elapsed|1.162383
Mar 29 08:42:21 main e-smith[30720]: Running event handler: /etc/e-smith/events/ip-change/S85update-dns
Mar 29 08:42:22 main dhcpcd[1021]: dhcpT1value option is missing in DHCP server response. Assuming 1800 sec
Mar 29 08:42:22 main dhcpcd[1021]: dhcpT2value option is missing in DHCP server response. Assuming 3150 sec
Mar 29 08:42:22 main dhcpcd[1021]: broadcasting second DHCP_DISCOVER
Mar 29 08:42:22 main dhcpcd[1021]: DHCP_OFFER received from  (24.144.yyy.yyy)
Mar 29 08:42:22 main dhcpcd[1021]: broadcasting DHCP_REQUEST for 24.144.xxx.xxx
Mar 29 08:42:22 main dhcpcd[1021]: DHCP_ACK received from  (24.144.yyy.yyy)
Mar 29 08:42:22 main e-smith[30819]: Processing event: ip-change 24.144.xxx.xxx
Mar 29 08:42:22 main e-smith[30819]: Running event handler: /etc/e-smith/events/ip-change/S15set-external-ip
Mar 29 08:42:23 main dyndns.org: IP Address 24.144.xxx.xxx already in database.
Mar 29 08:42:23 main e-smith[30720]: S85update-dns=action|Event|ip-change|Action|S85update-dns|Start|1048945341 542605|End|1048945343 972346|Elapsed|2.429741
Mar 29 08:42:23 main e-smith[30720]: Running event handler: /etc/e-smith/events/ip-change/S90pptpd-restart
Mar 29 08:42:24 main e-smith[30720]: S90pptpd-restart=action|Event|ip-change|Action|S90pptpd-restart|Start|1048945343 973001|End|1048945344 378258|Elapsed|0.405257
Mar 29 08:42:24 main e-smith[30720]: Running event handler: /etc/e-smith/events/ip-change/S90restart-ntpd
Mar 29 08:42:25 main e-smith[30819]: S15set-external-ip=action|Event|ip-change|Action|S15set-external-ip|Start|1048945342 822201|End|1048945345 302685|Elapsed|2.480484
Mar 29 08:42:25 main e-smith[30819]: Running event handler: /etc/e-smith/events/ip-change/S16adjust-masq
Mar 29 08:42:26 main e-smith[30720]: S90restart-ntpd=action|Event|ip-change|Action|S90restart-ntpd|Start|1048945344 378927|End|1048945346 370083|Elapsed|1.991156
Mar 29 08:42:26 main dhcpcd[1021]: sending DHCP_REQUEST for 24.144.xxx.xxx to 24.144.yyy.yyy
Mar 29 08:42:26 main dhcpcd[1021]: DHCP_ACK received from  (24.144.yyy.yyy)
Mar 29 08:42:28 main last message repeated 2 times
Mar 29 08:42:28 main last message repeated 2 times
Mar 29 08:42:29 main e-smith[30819]: S16adjust-masq=action|Event|ip-change|Action|S16adjust-masq|Start|1048945345 303436|End|1048945349 578305|Elapsed|4.274869
Mar 29 08:42:29 main e-smith[30819]: Running event handler: /etc/e-smith/events/ip-change/S47proftpd-conf
Mar 29 08:42:32 main e-smith[30819]: S47proftpd-conf=action|Event|ip-change|Action|S47proftpd-conf|Start|1048945349 578982|End|1048945352 249761|Elapsed|2.670779
Mar 29 08:42:32 main e-smith[30819]: Running event handler: /etc/e-smith/events/ip-change/S50conf-security
Mar 29 08:42:35 main e-smith[30819]: S50conf-security=action|Event|ip-change|Action|S50conf-security|Start|1048945352 250485|End|1048945355 546056|Elapsed|3.295571
Mar 29 08:42:35 main e-smith[30819]: Running event handler: /etc/e-smith/events/ip-change/S80pptpd-conf
Mar 29 08:42:36 main e-smith[30819]: S80pptpd-conf=action|Event|ip-change|Action|S80pptpd-conf|Start|1048945355 546742|End|1048945356 795463|Elapsed|1.248721
Mar 29 08:42:36 main e-smith[30819]: Running event handler: /etc/e-smith/events/ip-change/S85update-dns
Mar 29 08:42:38 main dyndns.org: IP Address 24.144.xxx.xxx already in database.
Mar 29 08:42:38 main e-smith[30819]: S85update-dns=action|Event|ip-change|Action|S85update-dns|Start|1048945356 796147|End|1048945358 158745|Elapsed|1.362598
Mar 29 08:42:38 main e-smith[30819]: Running event handler: /etc/e-smith/events/ip-change/S90pptpd-restart
Mar 29 08:42:38 main e-smith[30819]: S90pptpd-restart=action|Event|ip-change|Action|S90pptpd-restart|Start|1048945358 159417|End|1048945358 411602|Elapsed|0.252185
Mar 29 08:42:38 main e-smith[30819]: Running event handler: /etc/e-smith/events/ip-change/S90restart-ntpd
Mar 29 08:42:39 main e-smith[30819]: S90restart-ntpd=action|Event|ip-change|Action|S90restart-ntpd|Start|1048945358 413108|End|1048945359 577337|Elapsed|1.164229
Mar 29 08:42:39 main dhcpcd[1021]: sending DHCP_REQUEST for 24.144.xxx.xxx to 24.144.yyy.yyy
Mar 29 08:42:39 main dhcpcd[1021]: DHCP_ACK received from  (24.144.yyy.yyy)
Mar 29 09:12:39 main dhcpcd[1021]: sending DHCP_REQUEST for 24.144.xxx.xxx to 24.144.yyy.yyy
Mar 29 09:12:39 main dhcpcd[1021]: DHCP_ACK received from  (24.144.yyy.yyy)
Mar 29 09:41:15 main kernel: eth0: (1652710) System Error occured (0)
Mar 29 09:41:15 main kernel: eth0: (1652719) System Error occured (0)
Mar 29 09:41:16 main kernel: eth0: (1652811) System Error occured (0)
Mar 29 09:42:26 main kernel: eth0: (1652982) System Error occured (0)
Mar 29 09:42:39 main dhcpcd[1021]: sending DHCP_REQUEST for 24.144.xxx.xxx to 24.144.yyy.yyy
Mar 29 09:42:39 main dhcpcd[1021]: DHCP_ACK received from  (24.144.yyy.yyy)
Mar 29 09:42:42 main kernel: eth0: (1653052) System Error occured (0)
Mar 29 09:42:42 main kernel: eth0: (1653141) System Error occured (0)
Mar 29 09:44:51 main kernel: eth0: (1654277) System Error occured (0)
Mar 29 09:44:54 main kernel: eth0: (1654680) System Error occured (0)
Mar 29 09:44:55 main kernel: eth0: (1654827) System Error occured (0)
Mar 29 09:44:59 main kernel: eth0: (1654945) System Error occured (0)
Mar 29 09:45:04 main kernel: eth0: (1655428) System Error occured (0)
Mar 29 09:45:46 main kernel: eth0: (1655842) System Error occured (0)
Mar 29 09:45:57 main kernel: eth0: (1655943) System Error occured (0)
Mar 29 09:45:59 main kernel: eth0: (1656024) System Error occured (0)
Mar 29 09:48:44 main kernel: eth0: (1656594) System Error occured (0)
Mar 29 09:48:47 main kernel: eth0: (1656704) System Error occured (0)
Mar 29 09:48:55 main kernel: eth0: (1656995) System Error occured (0)
Mar 29 09:49:26 main kernel: eth0: (1657063) System Error occured (0)
Mar 29 09:49:28 main kernel: eth0: (1657192) System Error occured (0)
Mar 29 09:49:28 main kernel: eth0: (1657300) System Error occured (0)
Mar 29 09:49:35 main kernel: eth0: (1657496) System Error occured (0)
Mar 29 09:49:37 main kernel: eth0: (1657602) System Error occured (0)
Mar 29 09:49:37 main kernel: eth0: (1657645) System Error occured (0)
Mar 29 09:50:35 main kernel: eth0: (1657811) System Error occured (0)
Mar 29 09:50:35 main kernel: eth0: (1657871) System Error occured (0)
Mar 29 10:03:28 main kernel: eth0: (1658396) System Error occured (0)
Mar 29 10:03:28 main kernel: eth0: (1658404) System Error occured (0)
Mar 29 10:03:28 main kernel: eth0: (1658458) System Error occured (0)
Mar 29 10:03:30 main kernel: eth0: (1658557) System Error occured (0)
Mar 29 10:03:31 main kernel: eth0: (1658594) System Error occured (0)
Mar 29 10:03:31 main kernel: eth0: (1658658) System Error occured (0)
Mar 29 10:03:51 main kernel: eth0: (1658956) System Error occured (0)
Mar 29 10:06:43 main kernel: eth0: (1659058) System Error occured (0)
Mar 29 10:06:43 main kernel: eth0: (1659178) System Error occured (0)
Mar 29 10:12:39 main dhcpcd[1021]: sending DHCP_REQUEST for 24.144.xxx.xxx to 24.144.yyy.yyy
Mar 29 10:34:57 main kernel: eth0: (1659874) System Error occured (0)
Mar 29 10:35:04 main kernel: eth0: (1659945) System Error occured (0)
Viewed at Sat Mar 29 10:35:04 2003.