Prev: Cat 5E order of wires?
Next: Wait for infinity .. What is at fault, the browser or the proxy?
From: Bit Twister on 9 Apr 2010 06:45
On Fri, 09 Apr 2010 12:20:36 +0200, Tamer Higazi wrote:
> My config:
>
> # This network configuration was written by net-setup

Sorry, I have not seen that kind of configuration file.
What Linux Distribution are you running?


> config_eth0=("192.168.1.2 broadcast 192.168.1.255 netmask 255.255.255.0")
> config_eth3=("192.168.2.1 broadcast 192.168.2.255 netmask 255.255.255.0")
>
> dns_domain_lo="heimnetzwerk"

I need to install your distribution. What is it?

> and if i configure a client behind eth3 let us say with:
>
> 192.168.2.2, gw: 192.168.2.1 and nameserver: 192.168.2.1

You might want to consider using a known working dns server while
testing. Do a
cat /etc/resolv.conf
on the 192.168.1.2 machine and use same dns values on 192.168.2.2 machine.

> i stil even can't jump with the client in the internet. Ip forwarding is
> activated and masquerading too

Double check that, on the 192.168.1.2 machine, do a
cat /proc/sys/net/ipv4/ip_forward
if 1, then you are correct.

We need to see routing from both machines. The command is
route -n


> Here te firehol (firewall) script:

snip

When working a network problem, I find it helpful to have a spare
terminal open, watching the log file. I run shorewall as my firewall
and it's output can be seen in /var/log/messages. So the command is

tail -f /var/log/messages

Then I run my tests in another terminal.

> however, I can't jump with the client in the internet. I can ping to the
> other machine, but not in the internet. The hell I know why :(

To keep trouble shooting simple, I would ping the WAN/internet gateway
ip address from 192.168.1.2. If works, then ping the same ip address
from 192.168.2.2 (LAN machine).
From: Tamer Higazi on 9 Apr 2010 08:07
It's working!


Am 09.04.2010 12:45, schrieb Bit Twister:
> On Fri, 09 Apr 2010 12:20:36 +0200, Tamer Higazi wrote:
>> My config:
>>
>> # This network configuration was written by net-setup
>
> Sorry, I have not seen that kind of configuration file.
> What Linux Distribution are you running?
>
>
>> config_eth0=("192.168.1.2 broadcast 192.168.1.255 netmask 255.255.255.0")
>> config_eth3=("192.168.2.1 broadcast 192.168.2.255 netmask 255.255.255.0")
>>
>> dns_domain_lo="heimnetzwerk"
>
> I need to install your distribution. What is it?
>
Gentoo Linux with Kernel: 2.6.30-r5

>> and if i configure a client behind eth3 let us say with:
>>
>> 192.168.2.2, gw: 192.168.2.1 and nameserver: 192.168.2.1
>
> You might want to consider using a known working dns server while
> testing.

I have set up on the x.1.2 machine the tool "dnsmasq":
http://www.thekelleys.org.uk/dnsmasq/doc.html

which should forward the DNS Servers listet in the /etc/resolv.conf.
But of course I will make a retry with fixed values.

Do a
> cat /etc/resolv.conf
> on the 192.168.1.2 machine and use same dns values on 192.168.2.2 machine.
>
>> i stil even can't jump with the client in the internet. Ip forwarding is
>> activated and masquerading too
>
> Double check that, on the 192.168.1.2 machine, do a
> cat /proc/sys/net/ipv4/ip_forward

I tripple checked now, it is, even now i looked if the value in:

/proc/sys/net/ipv4/ip_forward

was set to 1.

However, after setting the DNS Servers directly at the client, it was
working. Why dnsmasq didn't make it, is for me still a riddle.

> if 1, then you are correct.
>
> We need to see routing from both machines. The command is
> route -n



>
>
>> Here te firehol (firewall) script:
>
> snip
>
> When working a network problem, I find it helpful to have a spare
> terminal open, watching the log file. I run shorewall as my firewall
> and it's output can be seen in /var/log/messages. So the command is
>
> tail -f /var/log/messages
>
> Then I run my tests in another terminal.
>
>> however, I can't jump with the client in the internet. I can ping to the
>> other machine, but not in the internet. The hell I know why :(
>
> To keep trouble shooting simple, I would ping the WAN/internet gateway
> ip address from 192.168.1.2. If works, then ping the same ip address
> from 192.168.2.2 (LAN machine).

Thank you all for your kind support. However, if you still have the
sollution for the DNS problem, i kindly thank you.



Tamer
From: Bit Twister on 9 Apr 2010 08:39
On Fri, 09 Apr 2010 14:07:30 +0200, Tamer Higazi wrote:

> I have set up on the x.1.2 machine the tool "dnsmasq":
> http://www.thekelleys.org.uk/dnsmasq/doc.html
>
> which should forward the DNS Servers listet in the /etc/resolv.conf.
> But of course I will make a retry with fixed values.

Hmmm, in my opinion, your dhcp client would have fetched your ISP's
dns server ip and some how dnsmasq learns about that.

Your /etc/resolv.conf on the 192.168.1.2 should be pointing to your
dns resolver/service on 192.168.1.2.

Here is mine:
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.132
search home.test
#*********** end resolv.conf ***********************



$ hostname --ip-address
192.168.1.132



> However, after setting the DNS Servers directly at the client, it was
> working. Why dnsmasq didn't make it, is for me still a riddle.

Going to guess the client ip address is static. If so, client's dnsmasq
has to be told about an up line dns server for non-local requests.

Now, if you are not running a dns server on the client, you should have used
the client's gateway ip as the client's dns server ip.
That assumes 192.168.1.2 is running a dns service/daemon.

First  |  Prev  | 
Pages: 1 2
Prev: Cat 5E order of wires?
Next: Wait for infinity .. What is at fault, the browser or the proxy?