Router not routing!?
Hello
I've succesfully configured a tiny LAN of two Solaris 10 PCs. I've also tried to set up a router for ip-forwarding and NAT between the LAN and internet, according to many explanations on the net. However, my router doesn't seem to be forwarding packets from non-router: traceroute from non-router to internet shows packet stucking on the LAN's router interface. At the same time I can directly traceroute internet interface of the router from non-router. I'm connected to internet using DHCP by a cable modem, and connection works nice on the router machine. I enclose the files of the router understood important as well as some outputs of commands, so can anyone see what is wrong? Any help is highly appreciated!
::::::::::::::
/etc/nodename
::::::::::::::
Taavi
I have an empty /etc/dhcp.rtls0.
My /etc/hostname.rtls0 is empty, for DHCP to work correctly.
::::::::::::::
/etc/hostname.rtls1
::::::::::::::
taavetti
::::::::::::::
/etc/inet/hosts
::::::::::::::
127.0.0.1localhostloghost
192.168.0.1taavetti
192.168.0.2Pohjoisneula
82.181.141.54Taavi# Added by DHCP
::::::::::::::
/etc/inet/ipnodes
::::::::::::::
::1localhost
127.0.0.1localhost loghost
192.168.0.1taavetti
192.168.0.2Pohjoisneula
82.181.141.54Taavi# Added by DHCP
I don't have /etc/defaultrouter, for DHCP to set the default router.
I don't have /etc/notrouter
::::::::::::::
/etc/inet/netmasks
::::::::::::::
192.168.0.0255.255.255.0
::::::::::::::
/etc/ipf/ipnat.conf
::::::::::::::
map rtls0 192.168.0.0/24 -> 0/32 proxy port ftp ftp/tcp
map rtls0 192.168.0.0/24 -> 0/32 proxy port 7070 raudio/tcp
map rtls0 192.168.0.0/24 -> 0/32 portmap tcp/udp auto
map rtls0 192.168.0.0/24 -> 0/32
::::::::::::::
/etc/ipf/ipf.conf
::::::::::::::
pass in all
pass out all
::::::::::::::
/etc/ipf/pfil.ap
::::::::::::::
rtls-10pfil
::::::::::::::::::
netstat -rn
::::::::::::::::::
Routing Table: IPv4
DestinationGatewayFlags Ref Use Interface
- -
192.168.0.0192.168.0.1U10rtls1
82.181.136.082.181.141.54 U13rtls0
224.0.0.082.181.141.54 U10rtls0
default 82.181.136.1UG 141rtls0
127.0.0.1 127.0.0.1 UH4111 lo0
::::::::::::::::::
routeadm
::::::::::::::::::
ConfigurationCurrent Current
OptionConfigurationSystem State
-
IPv4 forwardingenabled enabled
IPv4 routing enabled enabled
IPv6 forwardingdisabled disabled
IPv6 routing disabled disabled
[2748 byte] By [
Pneula] at [2007-11-26 10:54:23]
# 1
Anybody? Gurus, please?
I'm becoming hopeless with this. Thus far I've even tried to set up my router as a DHCP server, without success. The problem remains the same: traceroute from the non-router to internet stucks in the router.
snooping router's modem interface when trying to traceroute www.google.com from the non-router shows just this repeating(dns3.pp.htv.fi and lahna.pp.htv.fi are my nameservers):
Pohjoisneula -> dns3.pp.htv.fi DNS C www.google.com. Internet AAAA ?
UNKNOWN.pp.htv.fi -> (broadcast) ARP C Who is 82.181.180.227, 82.181.180.227 ?
Pohjoisneula -> lahna2.pp.htv.fi DNS C www.google.com. Internet AAAA ?
Taavi -> UNKNOWN.pp.htv.fi RIP R (2 destinations)
Pohjoisneula -> dns3.pp.htv.fi DNS C www.google.com. Internet AAAA ?
UNKNOWN.pp.htv.fi -> (broadcast) ARP C Who is 82.181.148.216, 82.181.148.216 ?
Taavi -> dns3.pp.htv.fi DNS C 216.148.181.82.in-addr.arpa. Internet PTR ?
Formerly I thought that setting up a LAN and connecting it into internet might be a relatively simple and straightforward task with Solaris. Ceased to think that these days. Please make my belief in Solaris to return!
# 2
> I'm becoming hopeless with this. Thus far I've even
> tried to set up my router as a DHCP server, without
> success. The problem remains the same: traceroute
> from the non-router to internet stucks in the
> router.
Without success? Where does:
> 82.181.141.54Taavi# Added by DHCP
come from then?
You need to add a default route entry to your DHCP setup on the router. The router will then tell the client which default router to use when it sends it the IP Address to use.
> Pohjoisneula -> dns3.pp.htv.fi DNS C www.google.com.
> Internet AAAA ?
AAAA means that it's looking for an IPv6 address. Is that correct?
alan
# 3
Thank you very much for your reply, Alan!
> Without success? Where does:
>
> > 82.181.141.54Taavi# Added by DHCP
>
> come from then?
From my ISP's DHCP server, completely correctly. Those settings files were the router's ones.
> You need to add a default route entry to your DHCP
> setup on the router. The router will then tell the
> client which default router to use when it sends it
> the IP Address to use.
Yes, if I used my router as DHCP server. It didn't work, and currently I''ve turned back to trying to set up LAN by local files and connecting it to internet. Corresponding to the original files, I've set the router as the default route of the non-router. For the router, I haven't set a default route, because ISP's DHCP server provides it and the router sets it up fine, as the routing table shows.
> Pohjoisneula -> dns3.pp.htv.fi DNS C
> www.google.com.
> Internet AAAA ?
>
> AAAA means that it's looking for an IPv6 address. Is that correct?
Really? Weird. For simplicity, I didn't configure any IPv6 interfaces!
What would you propose to do?
Best regards,
Pneula
# 4
> What would you propose to do?
If you could:
Just tell us your current configuration only! Now what you did in the past or how your got here, just "Here's what I got." After that, add here's what I want to happen.
Right now it''s a bit confusing to read through and try to process who's doing what and what's coming from where.
thanks,
alan
# 5
OK.
My current configuration is exactly what you see in my first message, but I try to clear it up a bit.
I have a router with two physical interfaces:
-rtls0 to ISP's DHCP via cable modem
-rtls1 to LAN: IP 192.168.0.1
/etc/dhcp.rtls0 exists to make DHCP configure
/etc/nodename contains my hostname Taavi
/etc/hostname.rtls0 is empty
/etc/hostname.rtls1 contains router's LAN hostname taavetti
/etc/notrouter doesn't exist
/etc/defaultrouter doesn't exist for DHCP to set the default route
::::::::::::::
/etc/inet/hosts
::::::::::::::
127.0.0.1 localhost loghost
192.168.0.1 taavetti
192.168.0.2 Pohjoisneula
82.181.141.54 Taavi # Added by DHCP
::::::::::::::
/etc/inet/ipnodes
::::::::::::::
::1 localhost
127.0.0.1 localhost loghost
192.168.0.1 taavetti
192.168.0.2 Pohjoisneula
82.181.141.54 Taavi # Added by DHCP
::::::::::::::
/etc/inet/netmasks
::::::::::::::
192.168.0.0 255.255.255.0
++++++++++
# netstat -rn
++++++++++
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
--
192.168.0.0 192.168.0.1 U 1 0 rtls1
82.181.136.0 82.181.141.54 U 1 3 rtls0
224.0.0.0 82.181.141.54 U 1 0 rtls0
default 82.181.136.1 UG 1 41 rtls0
127.0.0.1 127.0.0.1 UH 4 111 lo0
++++++++++
# routeadm
++++++++++
Configuration Current Current
Option Configuration System State
-
IPv4 forwarding enabled enabled
IPv4 routing enabled enabled
IPv6 forwarding disabled disabled
IPv6 routing disabled disabled
THE PROBLEM: I can't contact internet, for example my nameserver, from a non-router which belongs to my LAN. Traceroute from there stucks on the router's LAN interface. Using or not NAT doesn't change the situation.
# 6
> 82.181.141.54 Taavi # Added by DHCP
> 82.181.141.54 Taavi # Added by DHCP
> default 82.181.136.1 UG 1 41 rtls0
Can you post ifconfig -a?
Where does the default route come from. You said from the ISP, but it looks like they're giving you a 141 address and asking you to route through 136?
alan
# 7
> Can you post ifconfig -a?
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
rtls0: flags=1104843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,ROUTER,IPv4> mtu 1500 index 2
inet 82.181.141.54 netmask fffff800 broadcast 82.181.143.255
ether 0:10:a7:f:4:51
rtls1: flags=1100803<UP,BROADCAST,MULTICAST,ROUTER,IPv4> mtu 1500 index 3
inet 192.168.0.1 netmask ffffff00 broadcast 192.168.0.255
ether 0:50:fc:2f:7:b3
> Where does the default route come from.
I don't know how DHCP gets it, but as the routing table shows the default route is set up correctly. And it works fine for the router itself.
> You said
> from the ISP, but it looks like they're giving you a
> 141 address and asking you to route through 136?
Isn't it because of the netmask? Now that you mentioned, I began to wander why the inet and broadcast network IPs differ for rtls0.
Keeping listening. Thanks thus far!
# 8
> I have a router with two physical interfaces:
>-rtls0 to ISP's DHCP via cable modem
> -rtls1 to LAN: IP 192.168.0.1
Ok, this is where I"m getting confused. Or maybe it's just me.
Your router has two NIC's. You call them rtls0 and rtls1. Ok, so in my head the Solaris box is box one and the router box is box two. The router's NIC's do not correspond to the Solaris box at all, right?
> /etc/dhcp.rtls0 exists to make DHCP configure
> /etc/nodename contains my hostname Taavi
> /etc/hostname.rtls0 is empty
> /etc/hostname.rtls1 contains router's LAN hostname
> taavetti
Ok, this says that the Solaris box also has two NIC's. Again, like the router they are called rtls0 and rtls1. Am I correct so far?
To me it looks something like:
Internet
|
|
Cable Modem
|
| rtls0
Router
|rtls1 192.168
|
| rtls0 for Solaris
Solaris
|
|
rtls1
Did I even come close?
alan
# 9
Almost,but without the separated router. I'm trying to set up my first Solaris box (rtls0 and rtls1) as a router between the two interfaces. That's the problem. Do you know how to solve it?
