| 1 |
Hi, |
| 2 |
|
| 3 |
On Sun, 14 Jan 2007 20:27:11 +0100 "Daniel Pielmeier" |
| 4 |
<daniel.pielmeier@××××××××××.com> wrote: |
| 5 |
|
| 6 |
> I can connect from the router to the internet. |
| 7 |
> I can log in from the router to the desktop per ssh and back. |
| 8 |
> I have set up an rsync on the router and rsync works from the desktop. |
| 9 |
> I have set up dnsmasq on the server and dns is working on the desktop. |
| 10 |
> I can ping between router and desktop and from the router to the |
| 11 |
> internet |
| 12 |
> [...] |
| 13 |
> I can't ping from the desktop to the internet. |
| 14 |
|
| 15 |
OK, so forwarding is broken. |
| 16 |
|
| 17 |
> route |
| 18 |
> |
| 19 |
> Kernel IP routing table |
| 20 |
> Destination Gateway Genmask Flags Metric Ref Use Iface |
| 21 |
> dslb-088-067-01 * 255.255.255.255 UH 0 0 0 ppp0 |
| 22 |
> localhost * 255.255.255.0 U 0 0 0 eth0 |
| 23 |
> loopback * 255.0.0.0 U 0 0 0 lo |
| 24 |
> default dslb-088-067-01 0.0.0.0 UG 0 0 0 ppp0 |
| 25 |
|
| 26 |
Looking at this, I wouldn't even expect it to work at all, since the |
| 27 |
only route via eth0 is for "localhost". But since you can connect |
| 28 |
between router and desktop, I think you borked your /etc/hosts. |
| 29 |
"localhost" clearly doesn't seem to be assigned to 127.0.0.1. So fix |
| 30 |
your hostnames! |
| 31 |
|
| 32 |
|
| 33 |
This here: |
| 34 |
|
| 35 |
> /etc/hosts |
| 36 |
> |
| 37 |
> 127.0.0.1 localhost |
| 38 |
> 192.168.0.1 gentoo-vdr.linux gentoo-vdr |
| 39 |
> 192.168.0.2 gentoo.linux gentoo |
| 40 |
> ::1 localhost |
| 41 |
|
| 42 |
just can't be true if the routes above are the complete routes and you |
| 43 |
can connect to your desktop from the router. |
| 44 |
|
| 45 |
Another option than /etc/hosts may be a seriously broken dnsmasq config. |
| 46 |
|
| 47 |
> > For those who are not familiar with shorewall here are the |
| 48 |
> > generated iptables on the router. |
| 49 |
> |
| 50 |
> iptables -L -t filter |
| 51 |
> |
| 52 |
> Chain FORWARD (policy DROP) |
| 53 |
> target prot opt source destination |
| 54 |
|
| 55 |
Empty FORWARD chain and policy DROP means everything not going to the |
| 56 |
router itself is gonna be dropped. |
| 57 |
|
| 58 |
Note that you made yourself a hard time since there's DROP and REJECT |
| 59 |
(built-in targets) and you also reference "Drop", "drop", "Reject" and |
| 60 |
"reject" targets. I never used shorewall, but if that naming is from |
| 61 |
them, they are clearly freaks. |
| 62 |
|
| 63 |
-hwh |
| 64 |
-- |
| 65 |
gentoo-user@g.o mailing list |
Archives