Home Page › Forums › Network Management › ZeroShell › Why can’t I ping properly?
- This topic is empty.
-
AuthorPosts
-
April 15, 2009 at 5:30 pm #41634
alank2
MemberHi,
I setup a test zeroshell and it only has one interface.
I changed the interface IP to 192.168.110.75/24.
I clicked the gateway button and put a gateway in of 192.168.110.254.
I can ping any local devices, and the gateway, but I can’t ping beyond it for some reason. Is there something else I need to configure? This is a default Zeroshell other than the above changes.
Thanks,
Alan
April 15, 2009 at 6:21 pm #48018alank2
MemberHi,
If I enabled DHCP for the ETH00, then it can get out.
What is the DHCP enabled ETH00 doing that the static one isn’t ???
Thanks,
Alan
April 16, 2009 at 8:27 am #48019ppalias
MemberYou shouldn’t need to configure anything else.
Some possible scenarios are:
1) This is not the correct router
2) There is arp inspection, that allows traffic that is binded with dhcpIt would be helpful to paste here a copy of “route -n” and “ifconfig -a” commands on the ZS shell.
April 16, 2009 at 12:13 pm #48020alank2
MemberHi,
Here are the commands requests when using DHCP for ETH00 (and it works and can ping the outside world):
root@zeroshell root> route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.110.0 0.0.0.0 255.255.255.0 U 0 0 0 ETH00
192.168.250.0 0.0.0.0 255.255.255.0 U 0 0 0 VPN99
0.0.0.0 192.168.110.254 0.0.0.0 UG 0 0 0 ETH00
root@zeroshell root> ifconfig -a
DEFAULTBR Link encap:Ethernet HWaddr 56:03:01:08:5C:38
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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)ETH00 Link encap:Ethernet HWaddr 00:30:1B:81:F8:AD
inet addr:192.168.110.132 Bcast:192.168.110.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:134 errors:0 dropped:0 overruns:0 frame:0
TX packets:117 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20078 (19.6 Kb) TX bytes:17144 (16.7 Kb)
Interrupt:17VPN99 Link encap:Ethernet HWaddr 00:FF:22:CE:6A:F1
UP BROADCAST RUNNING 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)VPN99:00 Link encap:Ethernet HWaddr 00:FF:22:CE:6A:F1
inet addr:192.168.250.254 Bcast:192.168.250.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1dummy0 Link encap:Ethernet HWaddr 1E:0C:68:2C:E8:3A
inet addr:192.168.141.142 Bcast:192.168.141.255 Mask:255.255.255.0
BROADCAST NOARP 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)dummy1 Link encap:Ethernet HWaddr 22:54:35:5E:7B:79
inet addr:192.168.142.142 Bcast:192.168.142.255 Mask:255.255.255.255
UP BROADCAST RUNNING NOARP 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:203 errors:0 dropped:0 overruns:0 frame:0
TX packets:203 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:22790 (22.2 Kb) TX bytes:22790 (22.2 Kb)root@zeroshell root>
Here are the commands requests when NOT using DHCP for ETH00 (and it DOES NOT work and CAN’T ping the outside world):
root@zeroshell root> route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.250.0 0.0.0.0 255.255.255.0 U 0 0 0 VPN99
192.168.110.0 0.0.0.0 255.255.255.0 U 0 0 0 ETH00
0.0.0.0 192.168.110.254 0.0.0.0 UG 0 0 0 ETH00
root@zeroshell root> ifconfig -a
DEFAULTBR Link encap:Ethernet HWaddr 2A:4F:22:B5:01:29
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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)ETH00 Link encap:Ethernet HWaddr 00:30:1B:81:F8:AD
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:437 errors:0 dropped:0 overruns:0 frame:0
TX packets:696 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:45632 (44.5 Kb) TX bytes:119837 (117.0 Kb)
Interrupt:17ETH00:00 Link encap:Ethernet HWaddr 00:30:1B:81:F8:AD
inet addr:192.168.110.75 Bcast:192.168.110.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:17VPN99 Link encap:Ethernet HWaddr 00:FF:19:DD:A0:D5
UP BROADCAST RUNNING 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)VPN99:00 Link encap:Ethernet HWaddr 00:FF:19:DD:A0:D5
inet addr:192.168.250.254 Bcast:192.168.250.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1dummy0 Link encap:Ethernet HWaddr 4E:44:04:EE:F9:8A
inet addr:192.168.141.142 Bcast:192.168.141.255 Mask:255.255.255.0
BROADCAST NOARP 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)dummy1 Link encap:Ethernet HWaddr 7A:DB:BE:38:E4:63
inet addr:192.168.142.142 Bcast:192.168.142.255 Mask:255.255.255.255
UP BROADCAST RUNNING NOARP 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:196 errors:0 dropped:0 overruns:0 frame:0
TX packets:196 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:22353 (21.8 Kb) TX bytes:22353 (21.8 Kb)root@zeroshell root>
What do you think?
Alan
April 16, 2009 at 12:54 pm #48021alank2
MemberHi,
Nevermind – I figured it out. The upstream router from the zeroshell had a IP/MAC binding that was restricting access and dropping packets. Not the zeroshell’s fault at all…
Thanks,
Alan
-
AuthorPosts
- You must be logged in to reply to this topic.