Topic: S.O.S - Upgrade from 5.5 to 6.0.1

[lovelln]

I am having major problems around the WAN connection under 6.0.1.  

I installed a fresh release of 5.5 tested all the connections LAN, WAN etc, which worked fine, I could surf the internet, select local files.  I upgraded straight to release 6.0.1, from 5.5, and made no configuration changes whatso ever.  The Lan traffic works fine, but I can no longer access the Internal (WAN).  I am getting really confused, what changes do I need to make to establish internal traffic.  Any help appreciated

[lovelln]

the following is copied from the V5.5 - which works
Server Mode servergateway
Local IP address / subnet mask 192.168.1.1/255.255.255.0
External IP address / subnet mask 192.168.1.1/255.255.255.0
Gateway 192.168.1.254
Additional local networks No additional networks defined
DHCP server disabled
Server names

This is from 6.0.1 - which doesn't work (I have changed the last ip number to 2 so both server could be on at the same time to avoid conflicts with ip addressing)
Server Mode servergateway
Local IP address / subnet mask 192.168.1.2/255.255.255.0
External IP address / subnet mask 192.168.1.2/255.255.255.0
Gateway 192.168.1.254
Additional local networks 192.168.1.0/255.255.255.0
DHCP server disabled

[CharlieBrady]

I am having major problems around the WAN connection under 6.0.1.  

I installed a fresh release of 5.5 tested all the connections LAN, WAN etc, which worked fine, I could surf the internet, select local files.  I upgraded straight to release 6.0.1, from 5.5, and made no configuration changes whatso ever.  The Lan traffic works fine, but I can no longer access the Internal (WAN).

You'll need to look in your log files, probably /var/log/messages, and look for any errors.

You'll get more help here if you post more information about your system, for instance, what type of internet connection do you have?

What do you mean by "so both server could be on at the same time"? Are you trying to access the Intnernet from two different servers?

[lovelln]

Good Call

I shall check the message logs, at the next attempt of moving to 6.0.1

For your information I have one server running v5.5, and a second server that will replace the original 5.5 server, once I can get it working on 6.0.1 successfully

I have two network connections, one to the LAN and the second into a Telecom (NZ) ADSL Router.  The new server has the same network 10/100 cards using the same drivers.

I have installed 5.5 on the new server using the same configuration as the original 5.5 server, same ip addressing, names etc, however a different network card driver is used for both the Local and External networks.  ((Please note that the original 5.5 server is unplugged so I will not get any conflicts with addressing etc.))  The fresh 5.5 serverworks, I can connect locally and externally without any problems.

The problems kick in, when I upgrade this working 5.5 box to 6.0.1, by following the upgrade menu path.  There aren’t a lot of options, so little room for error.

Once I have upgraded to 6.0.1 I can connect locally, but not out to the WAN or WWW.  One of the best features of 5.5, was the internet test, it appears 6.0.1 doesn’t have this feature?

Anyway, this is where I’m at, v5.5 works fine, no problems, upgraded to 6.0.1, I can connect locally, but not externally.  

Confused? I am.

[mdo]

There must be something wrong with your definitions:

Local IP address / subnet mask 192.168.1.2/255.255.255.0
External IP address / subnet mask 192.168.1.2/255.255.255.0
Gateway 192.168.1.254
Additional local networks 192.168.1.0/255.255.255.0

You have THE SAME IP range (class C subnet) internal and external? This cannot work I would say. Your local network has to be different from your external network. Also the additional local network - why?

Regards,
Michael

[chris burnat]

I recall reading something about the need to upgrade from 5.5 to 5.6 first, then upgrade to 6.01...  Just a thought, may pay to check the forum.

[lovelln]

Funny you should say that, after searching the Forums I found a simular issue, and one of the recommendations was you should upgrade to 5.6 then 6.0.1, not straight from 5.5.  The best thing for me, is that I'm not playing with the production box!!!!, well it will be when I get this working.  Thanks for your help.  I will post the result in the next week.

[chris burnat]

5.5 to 5.6 is before my time (i am new at sme and linux..), but I have done a few 5.6 to 6.01 and apart from breaking a few contribs (they can be re-installed - no drama), it was generally straight forward.  So if you can get 5.6 working, you should be home and hosed... Best of luck. cheers. chris

[lovelln]

After much more "playing" the story contiunes ...

Upgraded from 5.5 to 5.6, with no effort what so ever, managed to connect to the WAN and LAN.  Great, things were looking up.

However the next step continues to cause trouble.  The upgrade progress itself from 5.6 to 6.0.1 is successful.  However I can no longer connect to the LAN. (in the past it was the WAN)  I noticed during the start up process of the 6.0.1 server my client PC actually connects (using ping -T) then drops (Request Timed Out) about 6 seconds later.  As I can no longer connect my client PC, I can't copy the log files here.

It must be a configuration issue, however 5.5 and 5.6 worked fine.  I have run out of time now, will have another go tomorrow, anybody else got any suggestions?

[chris burnat]

You should be able to check your log file from a terminal: cat  /var/log/messages | less may assist.  You can also check your settings via the server-manager included in the server-console.    Its a text-mode browser, but you will get the hang of it in no time at all - remember that the q key is used to get out of it... The other thing I would try is to swop the LAN cards in server-manager configuration menu - what happen?  All the best.

[lovelln]

This is still not a happening thing?, I have copied some of the log files.

The setup of my network is

WWW - ASDL connection <-> (203.###.###.###)Firewall/Router (ports 25, 80 and 443 are open, rest are blocked) (192.168.1.254) <-> (192.168.1.1) WAN Network (192.168.1.1) LAN Network <-> Hub <-> Local PCs/MACs

Configuration Review Section under Server-Manager Console

Networking Parameters
Server Mode servergateway
Local IP address / subnet mask 192.168.1.1/255.255.255.0
External IP address / subnet mask 192.168.1.1/255.255.255.0
Gateway 192.168.1.254
Additional local networks 192.168.1.0/255.255.255.0
DHCP server disabled


Working through the logs and noticed this
Mar 25 07:39:03 internal network: Setting network parameters:  succeeded
Mar 25 07:39:03 internal network:
Mar 25 07:39:03 internal network: Bringing up loopback interface:  
Mar 25 07:39:04 internal network: Bringing up loopback interface:  succeeded
Mar 25 07:39:04 internal network:
Mar 25 07:39:04 internal network: Bringing up interface eth0:  
Mar 25 07:39:07 internal network: Bringing up interface eth0:  succeeded
Mar 25 07:39:07 internal network:
Mar 25 07:39:07 internal network: Bringing up interface eth1:  
Mar 25 07:39:11 internal network: Bringing up interface eth1:  succeeded
Mar 25 07:39:11 internal network:
Mar 25 07:39:11 internal rc: Starting network:  succeeded
Mar 25 07:39:11 internal rc: Starting nut:  succeeded
Mar 25 07:39:12 internal random: Initializing random number generator:  
Mar 25 07:39:12 internal random: Initializing random number generator:  succeeded


A Small piece of the Messages Log, concerning network type stuff

Mar 29 07:01:22 internal network: Setting network parameters:  
Mar 29 07:01:22 internal sysctl: kernel.sysrq = 0
Mar 29 07:01:22 internal sysctl: net.ipv4.conf.all.rp_filter = 1
Mar 29 07:01:22 internal sysctl: net.ipv4.conf.default.rp_filter = 1
Mar 29 07:01:22 internal sysctl: net.ipv4.ip_dynaddr = 1
Mar 29 07:01:22 internal sysctl: net.ipv4.ip_forward = 1
Mar 29 07:01:22 internal sysctl: net.ipv4.tcp_keepalive_time = 300
Mar 29 07:01:22 internal sysctl: net.ipv4.tcp_syncookies = 1
Mar 29 07:01:22 internal network: Setting network parameters:  succeeded
Mar 29 07:01:22 internal network:
Mar 29 07:01:22 internal network: Bringing up loopback interface:  
Mar 29 07:01:23 internal network: Bringing up loopback interface:  succeeded
Mar 29 07:01:23 internal network:
Mar 29 07:01:23 internal network: Bringing up interface eth0:  
Mar 29 07:01:24 internal kernel: dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
Mar 29 07:01:24 internal kernel: PCI: Found IRQ 9 for device 00:09.0
Mar 29 07:01:24 internal kernel: PCI: Sharing IRQ 9 with 00:04.2
Mar 29 07:01:24 internal kernel: PCI: Sharing IRQ 9 with 00:06.0
Mar 29 07:01:24 internal kernel: divert: allocating divert_blk for eth0
Mar 29 07:01:24 internal kernel: eth0: Davicom DM9102 at pci00:09.0, 00:08:a1:13:03:28, irq 9.
Mar 29 07:01:26 internal network: Bringing up interface eth0:  succeeded
Mar 29 07:01:26 internal network:
Mar 29 07:01:26 internal network: Bringing up interface eth1:  
Mar 29 07:01:27 internal kernel: PCI: Found IRQ 10 for device 00:0a.0
Mar 29 07:01:27 internal kernel: 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
Mar 29 07:01:27 internal kernel: See Documentation/networking/vortex.txt
Mar 29 07:01:27 internal kernel: 00:0a.0: 3Com PCI 3c905 Boomerang 100baseTx at 0xb400. Vers LK1.1.18-ac
Mar 29 07:01:27 internal kernel:  00:60:08:e3:64:08, IRQ 10
Mar 29 07:01:27 internal kernel:   product code 4b4b rev 00.0 date 12-23-97
Mar 29 07:01:27 internal kernel:   Internal config register is 16302d8, transceivers 0xe040.
Mar 29 07:01:27 internal kernel:   8K word-wide RAM 3:5 Rx:Tx split, autoselect/MII interface.
Mar 29 07:01:27 internal kernel:   MII transceiver found at address 24, status 7849.
Mar 29 07:01:27 internal kernel:   Enabling bus-master transmits and whole-frame receives.
Mar 29 07:01:27 internal kernel: 00:0a.0: scatter/gather enabled. h/w checksums disabled
Mar 29 07:01:27 internal kernel: divert: allocating divert_blk for eth1
Mar 29 07:01:30 internal network: Bringing up interface eth1:  succeeded

The only error I could find in the messages log?

Mar 25 07:52:46 internal slapd[2195]: daemon: socket() failed errno=97 (Address family not supported by protocol

[lovelln]

If your running v6.0.1 and have two networks cards, one Wan and one LAN traffic, could you be so kind and paste the results of a IFCONFIG, so I have something to compare with my server.

I have compared between 5.5 and 6.0.1 and noticed that I'm missing Interrupt:?? and Base Address settings.  Not sure if this is normal under 6.0.1 or not.

Thanks in advance

[chris burnat]

eth0      Link encap:Ethernet  HWaddr 00:50:BF:EE:32:27
          inet addr:192.168.0.10  Bcast:192.168.0.255  Mask:255.255.255.0
          EtherTalk Phase 2 addr:65280/9
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:228 errors:0 dropped:0 overruns:0 frame:0
          TX packets:125 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:22747 (22.2 Kb)  TX bytes:16702 (16.3 Kb)

eth1      Link encap:Ethernet  HWaddr 00:A0:24:0A:F0:31
          inet addr:203.37.55.181  Bcast:203.37.55.183  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1025 errors:0 dropped:0 overruns:0 frame:0
          TX packets:793 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0
          RX bytes:108979 (106.4 Kb)  TX bytes:75026 (73.2 Kb)

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:28 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:3093 (3.0 Kb)  TX bytes:3093 (3.0 Kb)

Note1:  This is a test system, Wan is 203.37.55.181 and LAN is 192.168.0.10.  I use a router in front of the server with IP 203.37.55.177 at the output of the router.  My ISP has allocated 8 IP addresses for my own use.

Note2: Please consider the fact that the IP address on the WAN side (203.37.55.181) is different to the IP adress on the LAN side (192.168.0.10).  It may be relevant to your present challenge, and may be worth additional investigation.  As a result, summary of configuration for this server is:

Local IP address/subnet mask 192.168.0.10/255.255.255.0
External IP address/subnet mask 203.37.55.181/255.255.255.248
Gateway   203.37.55.177
Additional local networks 192.168.0.0/255.255.255.0

All the best.  chris.

[lovelln]

Well to cut a long story short, I have finally managed to achieve a result, not the desired result, but a result none the less.

I installed a new network card (different drivers) so I could determine what was external and what was internal network links.  Contiune with the setup as reported previously in this post.  I still could connect to the LAN but not the WAN.  So just for fun, I plugged the WAN connection into the switch, and bugger me it worked straight away.  So both cards are configurated, appear to work (under the messages report), but don't work???.

My setup now is WWW router plugged into the LAN switch along with all the desktops and server.  I'm guessing holes are all over the place, but it proves that my configuration is wrong.

Can I have the same IP address for the both internal and external network cards, current 192.168.1.1 for both?

[mdo]

NO

as I have already explained on 20.3.05.

Michael

[raem]

What is your server configuration, Server & gateway or Server only ?

You say you have an external modem that is a router and provides Firewall services, so therefore your sme box should be setup as Server only (not as Server & gateway).

Does that make sense in your situation ?

[lovelln]

Thanks to all the people who offered help in this matter, as Michael pointed out I needed an external and Internal IP address (which are different from each other).

I think I was getting confused (well I know I was) by the fact that SME 5.5 worked fine using 1 IP address for both network cards.

Thanks again to all concerned.
Nick