Hi Daria,
On Sun, 11 Feb 2007 at 13:17 +0100, Daria Morgendorffer wrote:
>
> Hi,
> excuse me for stupid question, but I got totally confused...
>
> LAN1 connected to a PC, IP 192.168.1.213
> WiFi received by a notebook, IP 192.168.3.213
> (IP's succesfully assigned by dnsmasq)
> WAN connected to SMC Barricade, its LAN port is 192.168.2.1, WAN is
> a.b.c.238 (it is probably so stupid that I want to hide details, it is a
> public IP address)
>
> When I log as [EMAIL PROTECTED], I can ping to PC (from 192.168.1.1), I
> can ping to notebook, I can ping to 192.168.2.1, I can ping to a machine
> on the Internet.
>
> When I run ping at the PC, I can ping to notebook, I can ping
> 192.168.2.1, but when I ping a machine on the Internet, I get
>
> From 192.168.2.1: icmp_seq=1 Redirect Host(New nexthop: a.b.c.237)
>
> and I can't seriously connect (SSH and so) to any machine on The
> Information Superhighway.
Your SMC router does not know anything about your 192.168.1.0/24
network your PC is connected. You either need to create a static
route on your SMC router 192.168.1.0/24 -> 192.168.2.222, because
only your FreeWRT router knows about 192.168.1.0/24.
The other possibility is to use iptables masquerading feature, so
that your SMC router just thinks, he get all packets from
192.168.2.222.
> NTP doesn't want to work (everything unreachable), but strangely I can
May be the Firewall on SMC blocks stuff? Is /etc/resolv.conf
correct? You need to rmeove the symlink and create a new file and
commit the change.
> SSH to the Asus 192.168.2.222 from yet another machine connected to
> SMC's another port (192.168.2.154).
>
> Syslog was willing to send something (one message during its restart
> though) to an external machine.
>
> Also, when I do S40network restart, the lines
> vconfig add eth0 0
> vconfig add eth0 1
> produce:
> vconfig: socket or ioctl error for add: Invalid argument
Uncritical.
> No clue why this is happening and how to fix it.
> ...and BTW: why syslogging is so silent?
Because routing problems are not logged. Try to restart dnsmasq and
you should get more logging. Try logread locally on FreeWRT.
good luck
Waldemar
--
don't open your wrt, free it
http://www.freewrt.org
_______________________________________________
freewrt-users mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-users
