Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: mike mattos on December 05, 2003, 04:25:29 PM

Title: how to restart just internet access
Post by: mike mattos on December 05, 2003, 04:25:29 PM

My service provider ( TELUS, Toronto area ) has some problems today, I started the day with two servers having no internet acess.  Both are "dsl" with fixed IP linked to MAC addresses. ( Don't know the technicalities of IP assignments, it has been a nightmare to set up the sites since the TELUS routers never seem to be configured in advance,   but after teething pains has been fast, reliable, and cheap.)

Their advice was to reboot the server, which DID resolve the problem, but made me wonder if I could restart just the components relating to the global ethernet card without shutting down the whole system.

One "symptom" was that the console "Test Internet Access" returned an error IMMEDIATELY, not the normal 20 second delay.


Thanks

[%sig%]

Title: Re: how to restart just internet access
Post by: Byte on December 05, 2003, 05:18:47 PM

could try at command line ifdown eth1

Then...

ifup eth1

HTH

Byte

Title: Re: how to restart just internet access
Post by: Darrell May on December 05, 2003, 06:14:15 PM

Might be preferable to issue:

/sbin/e-smith/signal-event remoteaccess-update

Darrell

Title: Re: how to restart just internet access
Post by: RayG on December 05, 2003, 07:23:12 PM

ifdown/ifup seems to leave the iptables rules in tact. The remoteaccess-update method seems to restart masq which drops any "temporary" rules created by things like Guardian. This is the expected behavior isn't it ?

Title: Re: how to restart just internet access
Post by: mike mattos on December 05, 2003, 07:32:13 PM

thank you, I'll try them and post the results

m

Title: Re: how to restart just internet access
Post by: mike mattos on December 08, 2003, 10:13:55 PM

/sbin/e-smith/signal-event remoteaccess-update

was tried, gave no indication of an error, but failed to restart internet access.

restarting ( fairly up to date sme 6 ) successfully restored access, same problem and results on a 5.5 system

mike