SOLVED]HORRIBLY slow network speeds, and can't ping anything inside the network.

[FutureTechSys]

So now I can access my Zarafa from the outside world... but now I can't get machines to see each other with Samba or even ping.

My current setup:

eth0 -> 192.168.1.20 internal
eth1 -> 192.168.1.22 external

Did away with the wireless completely, just using two wired connections.  Have my windows pc, which is .100, added to every list in the firewall settings I can find.  I can't ping either interface from my windows machine, and can't ping my windows machine from the Zentyal machine.

I'm not sure if it's just me, or if this is par for the course, but everything I fix seems to break 10 other things.

Also, when I browse the web from the Zentyal machine, DNS lookups seem to take FOREVER.  I have my router (192.168.1.1) set as a default gateway, on both Zentyal and my windows machine.  Some pages don't load at all, or I have to take 3 or 4 tries at it to get it to work.  Something is definitely wrong; it wasn't doing this before.

Also, my router no longer shows the host name of the machine under attached devices; just it's IP address.

Please help!

[FutureTechSys]

Also, the router reports both .20 and .22 as having the same MAC address.  When I do ifconfig -a on the Zentyal machine, as well as from the web administration page, it shows (correctly) that they are in fact 2 separate mac addresses.

[DobleIT]

Hi FutureTechSys

This might sound like a silly question but are eth0 and eth1 connected to the same switch?

Also, if your PC is 'behind' the Zentyal machine, then it needs to be set to use Zentyal as the gateway in order for it to 'find' its way to the internet.

To help with some more troubleshooting, can you do an ipconfig /all on your windows PC, and run an ifconfig on the zentyal machine, and post the results here? Some info on the router's networking setup would help too, like IP address, DNS setting, etc

Cheers
James

[FutureTechSys]

I tried with them connected to the same switch, as well as different switches.

This also worked fine in every sense until 2 days ago.  One thing I'm noticing is the router isn't properly detecting the host name and it thinks both NICs have the same MAC address.  I am sort of leaning towards it being an issue with the router at this point.


Windows:

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ether
net Controller
   Physical Address. . . . . . . . . : E0-CB-4E-0F-F6-2E
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.125(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Zentyal:

eth0      Link encap:Ethernet  HWaddr 00:18:f3:67:68:0e 
          inet addr:192.168.1.20  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::218:f3ff:fe67:680e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6951 errors:0 dropped:0 overruns:0 frame:0
          TX packets:709 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:969430 (969.4 KB)  TX bytes:79525 (79.5 KB)
          Interrupt:22 Base address:0xe000

eth1      Link encap:Ethernet  HWaddr 00:18:f3:70:2e:28 
          inet addr:192.168.1.22  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::218:f3ff:fe70:2e28/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:111836 errors:0 dropped:0 overruns:0 frame:0
          TX packets:56746 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:142853790 (142.8 MB)  TX bytes:34413814 (34.4 MB)
          Interrupt:21 Base address:0xe000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1678010 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1678010 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:278439372 (278.4 MB)  TX bytes:278439372 (278.4 MB)

wlan0     Link encap:Ethernet  HWaddr 00:15:af:05:83:1f 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Router uses my ISP's DNS servers, and is set with a static IP.

[DobleIT]

I should have spotted this to begin with but I didn't ..

You need to change the subnets

You can't have both adapters in Zentyal running on the same subnet, because when it receives a packet it has no way of knowing which adaptor to route it through to get where it needs to go.

Try something like this

PC - 192.168.0.10
Zentyal eth0 192.168.0.1
Zentyal eth1 192.168.1.1 (tick "external" box in zentyal configuration)
Router 192.168.1.254

Note that the subnets are different, this way it is obvious to Zentyal which adaptor to route packets through depending upon the destination and source.

Don't forget to configure the 'gateway' section of Zentyal under Networking as the router's IP address.

Your PC should use Zentyal as its DNS and Gateway. (192.168.0.1)

Let me know how you go with this!

James

[FutureTechSys]

normally I'd try something like that, but it was working fine until 2 days ago... also it should know which adapter to route it to based on the destination IP, shouldn't it?

The router not recognizing the MAC address has got me bothered too.  I think im going to replace the router (its time anyway - its not BRAND NEW anymore  ) with a Buffalo and load DD-WRT on it.

I may still try this though just to see... but if anybody else has any other thoughts feel free to chip in.

[DobleIT]

it should know which adapter to route it to based on the destination IP, shouldn't it?

No, as far as Zentyal is concerned, both NICs are connected to the same network - and whats more, it isn't aware of what hosts are on each subnet, it'll just send a packet off to the subnet and its up to the switch to sort it out.

The router not recognizing the MAC address has got me bothered too.  I think im going to replace the router (its time anyway - its not BRAND NEW anymore  ) with a Buffalo and load DD-WRT on it.

I don't think this is related - its likely due to you having both NICs connected to the same switch, Zentyal would probably have been sending its packets from its primary NIC. Either way, I don't think its related to your problems if your setup is similar to the one I gave above

Cheers
James

[FutureTechSys]

Yeah, but I tried it on a separate switch as well... that's the weird thing.

And the MAC address/not showing the host name on the router just started happening.

What about if I unhooked the external connection, so its just one NIC connected?

[FutureTechSys]

Try something like this

PC - 192.168.0.10
Zentyal eth0 192.168.0.1


Don't forget to configure the 'gateway' section of Zentyal under Networking as the router's IP address.

Your PC should use Zentyal as its DNS and Gateway. (192.168.0.1)

Let me know how you go with this!

James

Wouldn't I want to use the external interface as the DNS and gateway?  And would I add the new router IP as a gateway address on the external interface in Zentyal?

[DobleIT]

Firstly:

would I add the new router IP as a gateway address on the external interface in Zentyal?

Yes, that's right. However the internal interface doesn't need a gateway address - as zentyal will know to route it to the interface with the 'external' checkbox ticked.

Wouldn't I want to use the external interface as the DNS and gateway?

I think you might be getting confused a bit when it comes to the way a packet is transmitted on the network, and how that packet passes from network to network.

Please forgive me if I've misunderstood, but I think the easiest way to explain this is through a diagram with a few different scenarios.

I think best in pictures! haha

First off, here's one configuration of zentyal - using it as a router. This is how I have my network set up in fact:



Now lets examine the path of a packet on this network:



But if the PC is misconfigured with the wrong gateway settings ...



Another scenario is two computers trying to talk to eachother on different subnets:



Now lets look at another possible network configuration for Zentyal - as an internal server. This is mostly when you just want Zentyal to be a file server / domain controller / email server, and you have a firewall on your router or gateway device instead.



Now lets look at the path of a packet here - note that Zentyal doesn't have anything to do with the packet.



Try to think of the 'path' that a packet has to make to get where its going.

Here's a good analogy to summarize:

Routers are like the postal service. In order for you to send a letter from Australia to number 10 York Street in New York, USA, you need to put on the envelope that the address is located in the USA, so that when the postal service picks up your letter, it knows to send it onto the USA, where another postal service that is more familliar with the local area can then send it to new york, where another postal service can then give it to a postman who services York Street, and who knows where number 10 is.

Switches are like postmen. If they pick up a letter they can only take it to the places they service in their post run - they aren't going to take a plane to the USA and deliver your letter personally!

I hope this helps!

James

[FutureTechSys]

The last two diagrams are how I have it set up.  I need zentyal/my network to be able to do the following:

-Send and receive email
-Hardware router does the routing
-All PCs (including Zentyal and PC) can ping each other
-File sharing

That's it.  Maybe I disable one of the two NICs, and get rid of the firewall piece and turn off external?  I thought, perhaps mistakenly, that I needed two NICs, with one of them set as external, to be able to get access to and from the internet to Zentyal.

[FutureTechSys]

Here's anothing thought... my NICs are two onboard NICs.  Previously (when this was working) I was using 1 wired and 1 wireless.  What do you think the chances are that it is only correctly detecting one of my two NICs, and that its trying to assign two different IP addresses to the same physical nic?

in ifconfig -a and the dashboard, it shows the separate mac addresses... but who knows.  Just trying to figure out why the F I can't seem to get this working the way I want it to.

[DobleIT]

If you have Zentyal set up as in the last 2 diagrams, then having 2 NICs will only complicate things, there's no real benefit. Zentyal simply acts as an internal server and doesn't do any routing or firewall processing.

You don't need to turn off the firewall, but you can if you want. When Zentyal knows an interface is internal it should allow the majority of network traffic that is required to run a network - like SMB etc.

Regarding your two NICs - I think its more likely that Zentyal is just getting its routing confused because you have told it that a single subnet is both an internal and an external network

Also, in the case of the last 2 diagrams, its up to you as to wether or not Zentyal acts as an internal DNS relay as well - but your gateway must be the router.

[FutureTechSys]

Can I have just one NIC and have it process both local network stuff as well as receive email, or is it required to have a separate internal and external interface?

One thing I've noticed through tinkering is that when I CANT ping it or see its hostname on the local network, sending and receiving email via the domain works fine, and when I CAN ping it, the outside world can't get to it.

So let's say I want 192.168.1.* to be my local network, and 192.168.0.* to be my external.

Correct me where I'm wrong:

192.168.1.20 Zentyal internal NIC
192.168.1.100 Windows PC

192.168.0.20 Zentyal external NIC
192.168.0.1 Internet router
192.168.0.1 Default Gateway

If it's right so far, what do I set the gateway to on my Windows PC?

And what if I just plugged the cable modem in to the external NIC, and had the wireless router behind it on the local network?

I've also got a new router on the way to install DD-WRT on as well.  Looking forward to that

[FutureTechSys]

Actually I think that last one may work best...

I just unhooked the second NIC, and set the first to internal, and now I can see it on the local network and also access webmail externally.

Appreciate the help!  We can mark this one as solved I think.