Tag Info

New answers tagged

1

Hi guys I found out what happened. I ran netstat -aup which shows all the UDP ports and the processes attached to it. The options: a - listen to all sockets (when combined with u listens only to UDP sockets) u - listen to udp ports p - lists the processes attached to the ports I found out that the process attached to port 38854 was pulseaudio. On ...


0

Figured it out (and fortunately the failsafe mode DID work, or I'd be in trouble). The main mistakes I made that were not on http://wiki.openwrt.org/doc/recipes/dumbap were that the vlan was called switch0.1 and not eth0.1; and the wireless radios were disabled for some reason. The necessary changes in /etc/config/wireless: remove the option disabled '1' ...


0

Okay! My problem has been solve. I used this command (like i posted above) iptables -t nat -I PREROUTING -p tcp --dport 80 -j DNAT --to-destination 192.168.11.100 I don't know that is working because i tested on computer has ip address 192.168.11.100. When i use mobile to connect to my network, it works! So thank you guys so much for helping me!


0

You can try: iptables -t nat -A PREROUTING -p tcp -m multiport --dport 80,443 -i eth0 -d 192.168.11.100 -j DNAT --to-destination 192.168.11.100 You have to change interface eth0


0

Use this: iptables -t nat -A PREROUTING -m mac --mac-source xx-xx-xx-xx-xx-xx -j ACCEPT (Host A) iptables -t nat -A PREROUTING -m mac --mac-source xx-xx-xx-xx-xx-xx -j ACCEPT (Host B) iptables -t nat -A PREROUTING -p tcp --dport 80 -j DNAT --to 127.0.0.1:8080 The first two commands ACCEPT packets from A and B, so redirection only happen if the packet is ...


1

Okay, you keep editing your question and changing the scope. Although I'm not sure what you mean by: If a router resides in the same network as the destination host, but cannot resolve the IP, meaning it cannot reach the host itself, then the router should send a host unreachable message. I have a hunch. If the router is on the same network segment, ...


0

For some reason your client is unable to delete the current default route when the tunnel opens, thereby causing two default routes to exist in the routing table. What you are going to have to do is give the current route a lower metric (higher number) before the tunnel comes up. You can see the metric with the route -n command: # route -n Kernel IP ...



Top 50 recent answers are included