Traffic re-routing problem on M25

Hi,
I have a N8 on Anna, when I use the traffic option in drive it routes me around the M25 junction 18 as it seems to think the motorway is blocked. The map has a black line on it and the no-entry icon. The motorway is not blocked, If I drive on the route is re-calculated and I find no blockage.
It has been like this for a few days now, I connected to my PC and found 3.08 release and updated my maps, but the problem still exists.
Help!
Thanks
Stephen

If by "re-route" you mean an HTTP redirect is occurring, then that would most likely be either your script or a mod_rewrite rule doing that. You should look at the transactions and your logs carefully.

Similar Messages

  • TV Guide fails - router problem?

    When the guide failed on our main TV is the family room, I tried trouble-shooting it -- no luck.  Then I "chatted" online with Verizon's "Raul" for two hours, trying everything he asked, including swapping the box with the one in the bedroom -- Raul thought it was the biox and gave me an 800 number to call to get a swap in boxes.  However, before the weekend is over, all but one TV has the same problem.  Right now, we get the guide on one TV and no guide on four TVs.
    I've worked on this all day so far today.  Verizon's In-Home Agent reports that none of the TVs have connectivity with the router.  So I've concentrated on that, I've unplugged the router and the boxes, reset the router, accessed the router's control panel to see it seems to be working well.  The only thing I can see wrong is this:  The router's "WAN Ethernet" light stays dark, though its "WAN Coax" light stays lit.  I wonder if this could be the problem; and, if so, how could I fix that?
    One thing worries me about a router problem, though: Why would I still have the guide on one of the six TVs?
    Anyone have a clue if I'm on the right track?
    Thanks,
    George

    Yes, sounds like a router problem.
    The STB has to download the program guide via the router. Each box should download 10 days worth of programing. So when the router goes out it could take as much as 10 days before the guide disappears. So the one box that still has the guide, was the last one to update and had more guide data stored than the others. It will go as well just given time.
    If you have rebooted and reset the router, then the problem is either you have a bad router or possibly a bad splitter. Either way, you need to call tech support so they can get a tech out.
    ====================================================================================
    Error exists between keyboard and chair.

  • Router problems how can I connect direct

    I am continually having router problems from my service provider. How can i connect my printer directly to my computer? Thanks

    Hi,
    You need a printer which supports this first and then use the following instructions:
         http://www8.hp.com/au/en/campaigns/wireless-printing-center/wireless-direct.html
    Regards.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

  • Mysterious routing problem / interface determination

    Hi,
    I have a very very strange routing problem with XI.
    A message is sent from R/3 to XI and then send via adapter to an external party. The routing is configured well. But sometimes I have the following problem:
    A message is received by XI (from R/3). The receiver is determinated. Although an interface determination and receiver agreement is configured, the trace shows "no interface determination fpr party xyz and service abc found". The very strange thing is that finally the receiver interface DELINS.DELFOR01 with namespace urn:sap-com:document:sap:idoc:messages is set!!
    Finally, the error message is "no receiver agreement found for "... DELINS.DELFOR01, urn:sap-com:document:sap:idoc:messages", which is reasonable because this receiver interface has never ever been configured!
    Any idea why the interface determination cannot be found and nevertheless a completely wrong receiver interface is set?
    This error occurs just sometimes for certain partners, but not always with all messages for these partners!
    Help appreciated!
    Christopher

    Hi,
    all routing objects are 100% correct. Particularly the receiver service has definitely no DELINS.DELFOR01 interface, but nevertheless the Integration Runtime tries to send the message to this interface. Another strange thing is that in the trace there is the warning "no interface determination for party xxx and service xxx found".
    By the way: The Receiver Determination was configured to terminate message processing when no receiver can be found.
    CHRIS

  • On the continuing saga of third party router problems......

    I got an Apple TV which works great with my wireless Airport WDS, but then I was looking into any problems people could be having with it and ran into this:
    http://discussions.apple.com/thread.jspa?threadID=901401&tstart=0
    Check the third party router problems where Airports worked great.
    Networking is ...networking, but you also get what you pay for.

    Hi mgrant,
    The information at the bottem of the article in in Keith_Beddoe's personal website may help. Link: Using your own router for Infinity
    The MTU Size needs to be set as 1492
    Cheers
    jac_95 | BT.com Help Site | BT Service Status
    Someone Solved Your Question?
    Please let other members know by clicking on ’Mark as Accepted Solution’
    Try a Search
    See if someone in the community had the same problem and how they got it resolved.

  • E2000 + WAG160N routing problem?

    Hi all,
    I have a new E2000 router with address 192.168.0.1 connected to a WAG160N Modem router with address 192.168.1.1
    and several computers at each router.  All have DHCP activated and wifi active and working.
    The cascading connection between both devices seems working well only in one direction.
    All seems ok as I can access to internet from any computer. Also, computers connected to E2000 have accces 
    to computers on WAG160N modem BUT computers connected at modem do NOT have access to computer at router.
    In fact from a computer connected to the E2000 I can configure the web interface of the E2000 and also the WAG160N
    but from a computers connected at WAG160N I have access only to this interface but not to the E2000 interface.
    I don't know if could be a routing problem. Any help will be appreciated.
    Thanks in advance,
    Marti

    The E2000 is configured to do NAT and thus protects the LAN from the internet side. If it was easily accessible your WAG LAN would be easily accessible from the internet.
    You want to set up the E2000 as simple access point:
    Unplug the E2000 from the WAG160N and open the web interface of the E2000 from a computer wired to the E2000.
    On the main setup page
    1. change the internet connection type to Automatic/DHCP (in case you have changed it).
    2. change the LAN IP address from 192.168.0.1 to 192.168.1.2.
    3. Disable the DHCP server.
    4. Save settings.
    Unplug the computer.
    Now wire one of the numbered LAN ports of the E2000 to the WAG160N. Don't use the internet port on the E2000.
    That's the best setup you can do with your two routers... The E2000 is only used as simple access point and ethernet switch.

  • Route problem

    Hi all,  I am new to this forum and also new to Archlinux. I have been using SuSE for 4 years and learned how to use that gui. I never learned the grassroot of linux though. I completed the install on my TPad 600e without any problem at all. I am using a old orinoco gold that has been my standby forever. I have googled and searched this forum for several hours and tried all the suggestions I came across. My problem seems to be the same as many others have had. I had originally thought it was a route problem, but the output or netstat -nr is exactly the same as the output on my SuSE computer. I am not good with words, but let me try a description.
    I cannot connect to my home lan at all. I have assigned a static ip and the output of iwconfig verifies that it is correct as I have assigned. When I try to ping my router the system returns the famous "Destination Host Unreachable" As mentioned I have tried to setup my default gateway and it is identical to the the output from my SuSE computer. When I try a dhcp setup and do a network restart the restart always fails. I have gone over and over my conf files looking for a fatfinger mistake but all looks exactly the way the examples I have searched up and I cannot see any typos. I would like to get this figured out for myself but I am out of clues on where to look and would appreciate new ideas.
    It is as if there is a firewall in place, but this is a straight from the CD basic install to which I have installe the network section.
    I really need to be pointed in a new direction.
    David

    ralvez wrote:Here ... my IP is 192.168.1.21 try to reach me 
    Gotcha!
    PING 192.168.1.21 (192.168.1.21) 56(84) bytes of data.
    64 bytes from 192.168.1.21: icmp_seq=1 ttl=64 time=5.21 ms
    64 bytes from 192.168.1.21: icmp_seq=2 ttl=64 time=3.62 ms
    64 bytes from 192.168.1.21: icmp_seq=3 ttl=64 time=7.20 ms
    64 bytes from 192.168.1.21: icmp_seq=4 ttl=64 time=4.03 ms
    64 bytes from 192.168.1.21: icmp_seq=5 ttl=64 time=5.38 ms
    64 bytes from 192.168.1.21: icmp_seq=6 ttl=64 time=5.31 ms
    64 bytes from 192.168.1.21: icmp_seq=7 ttl=64 time=5.33 ms
    64 bytes from 192.168.1.21: icmp_seq=8 ttl=64 time=5.31 ms
    64 bytes from 192.168.1.21: icmp_seq=9 ttl=64 time=4.83 ms
    64 bytes from 192.168.1.21: icmp_seq=10 ttl=64 time=4.84 ms
    64 bytes from 192.168.1.21: icmp_seq=11 ttl=64 time=4.12 ms
    64 bytes from 192.168.1.21: icmp_seq=12 ttl=64 time=8.28 ms
    64 bytes from 192.168.1.21: icmp_seq=13 ttl=64 time=5.25 ms
    64 bytes from 192.168.1.21: icmp_seq=14 ttl=64 time=5.24 ms
    64 bytes from 192.168.1.21: icmp_seq=15 ttl=64 time=4.21 ms
    64 bytes from 192.168.1.21: icmp_seq=16 ttl=64 time=5.20 ms
    64 bytes from 192.168.1.21: icmp_seq=17 ttl=64 time=4.19 ms
    64 bytes from 192.168.1.21: icmp_seq=18 ttl=64 time=6.17 ms
    --- 192.168.1.21 ping statistics ---
    18 packets transmitted, 18 received, 0% packet loss, time 17096ms
    rtt min/avg/max/mdev = 3.624/5.212/8.288/1.101 ms
    OK - fun's over. Spotslayer, can you post the output of ifconfig and iwconfig? (and don't mind ralvez - hide anything you want )

  • Another routing problem

    I just replaced a FreeBSD box with Solaris 10 x86 U5.
    I want my Windows boxes to reach internet thru Solaris. At the moment windows clients are able to ping both NICs on the Solaris. However, they can not ping default gateway of Solaris box. There is no problem on Solaris. I can reach internet without any problem.
    Before posting, I used routeadm and (1) I enabled only ipv4-forwarding (did not work), (2) I enabled only ipv4-routing (did not work), (3) I enabled both ipv4-forwarding & ipv4-routing (did not help)
    I also read about 5 pages of similar routing problems in forums. No clear solution is provided in any of them. I am posting this with the hope to find a solution.
    Some information about my network is as follows:
    bash-3.00# ifconfig -a
    lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
    inet 127.0.0.1 netmask ff000000
    bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
    inet 192.168.2.2 netmask ffffff00 broadcast 192.168.2.255
    ether 0:1c:c4:31:5:fd
    e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
    inet 192.168.1.3 netmask ffffff00 broadcast 192.168.1.255
    ether 0:1b:21:15:15:29
    bash-3.00#
    bash-3.00# netstat -rn
    Routing Table: IPv4
    Destination Gateway Flags Ref Use Interface
    default 192.168.2.1 UG 1 15658
    192.168.1.0 192.168.1.3 U 1 177 e1000g0
    192.168.2.0 192.168.2.2 U 1 8 bge0
    127.0.0.1 127.0.0.1 UH 4 58 lo0
    bash-3.00#
    bash-3.00# routeadm
    Configuration Current Current
    Option Configuration System State
    IPv4 routing disabled disabled
    IPv6 routing disabled disabled
    IPv4 forwarding disabled disabled
    IPv6 forwarding disabled disabled
    Routing services "route:default ripng:default"
    Routing daemons:
    STATE FMRI
    disabled svc:/network/routing/legacy-routing:ipv4
    disabled svc:/network/routing/legacy-routing:ipv6
    disabled svc:/network/routing/ndp:default
    disabled svc:/network/routing/zebra:quagga
    disabled svc:/network/routing/rip:quagga
    disabled svc:/network/routing/ripng:default
    disabled svc:/network/routing/ripng:quagga
    disabled svc:/network/routing/ospf:quagga
    disabled svc:/network/routing/ospf6:quagga
    disabled svc:/network/routing/bgp:quagga
    disabled svc:/network/routing/rdisc:default
    disabled svc:/network/routing/route:default
    bash-3.00#
    bash-3.00# ndd -get /dev/ip ip_forwarding
    0
    bash-3.00#

    kucukoglu wrote:
    I just replaced a FreeBSD box with Solaris 10 x86 U5.
    I want my Windows boxes to reach internet thru Solaris. At the moment windows clients are able to ping both NICs on the Solaris. However, they can not ping default gateway of Solaris box. There is no problem on Solaris. I can reach internet without any problem.Does the outside world know how to route to the clients behind Solaris? I'll bet they do not.
    If that's true, then routing/forwarding isn't useful. You'll have to set up the Solaris box as a NAT gateway instead. Ipfilter can do that. There are several cookbooks for it.
    Before posting, I used routeadm and (1) I enabled only ipv4-forwarding (did not work), (2) I enabled only ipv4-routing (did not work), (3) I enabled both ipv4-forwarding & ipv4-routing (did not help)
    I also read about 5 pages of similar routing problems in forums. No clear solution is provided in any of them. I am posting this with the hope to find a solution.Your solution is fine for outbound packets (the clients use Solaris as a gateway and then it forwards them on to the internet). But for the return packet, that's not possible. There's no route published.
    Darren

  • S2S VPN - ASA 5505 to ASA 5540 - Routing Problems

    I'm a software developer (no doubt the issue) trying to setup my remote office (5505) to the main office (5540). No problem getting the S2S VPN up, but I definitely have problems with the routing. Using tracert, it shows it going into the remote network for a couple of hops, but then timing out. Packet tracer shows everything is fine. Using my client VPN credentials to the remote network, same on the return path...does a few hops, then gets lost. I've stripped down the config to the basics and ensured it isn't security settings on both ends, but still doesn't work. I've spent A LOT of hours trying to get this to work, so thanks for any assistance!
    Current running config:
    ASA Version 8.2(5)
    hostname asa15
    enable password XXXXX encrypted
    passwd XXXXX encrypted
    names
    name 10.0.0.0 remote-network
    interface Ethernet0/0
    switchport access vlan 2
    interface Ethernet0/1
    interface Ethernet0/2
    interface Ethernet0/3
    interface Ethernet0/4
    interface Ethernet0/5
    interface Ethernet0/6
    interface Ethernet0/7
    interface Vlan1
    nameif inside
    security-level 100
    ip address 172.16.5.1 255.255.255.0
    interface Vlan2
    nameif outside
    security-level 0
    ip address dhcp setroute
    ftp mode passive
    access-list outside_1_cryptomap extended permit ip 172.16.5.0 255.255.255.0 remote-network 255.0.0.0
    access-list inside_nat0_outbound extended permit ip 172.16.5.0 255.255.255.0 remote-network 255.0.0.0
    access-list inside_access_in extended permit ip 172.16.5.0 255.255.255.0 remote-network 255.0.0.0
    access-list inside_nat0_outbound_1 extended permit ip 172.16.5.0 255.255.255.0 remote-network 255.0.0.0
    pager lines 24
    logging enable
    logging asdm informational
    mtu outside 1500
    mtu inside 1500
    icmp unreachable rate-limit 1 burst-size 1
    asdm location remote-network 255.0.0.0 inside
    no asdm history enable
    arp timeout 14400
    global (outside) 1 interface
    nat (inside) 0 access-list inside_nat0_outbound_1
    nat (inside) 1 0.0.0.0 0.0.0.0
    access-group inside_access_in in interface inside
    route outside 0.0.0.0 0.0.0.0 99.X.X.7 1
    timeout xlate 3:00:00
    timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
    timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
    timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
    timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
    timeout tcp-proxy-reassembly 0:01:00
    timeout floating-conn 0:00:00
    dynamic-access-policy-record DfltAccessPolicy
    http server enable
    http 172.16.5.0 255.255.255.0 inside
    no snmp-server location
    no snmp-server contact
    snmp-server enable traps snmp authentication linkup linkdown coldstart
    crypto ipsec transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac
    crypto ipsec transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac
    crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
    crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
    crypto ipsec transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
    crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
    crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
    crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
    crypto ipsec transform-set ESP-DES-SHA esp-des esp-sha-hmac
    crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac
    crypto ipsec security-association lifetime seconds 3600
    crypto ipsec security-association lifetime kilobytes 4608000
    crypto map outside_map 1 match address outside_1_cryptomap
    crypto map outside_map 1 set peer 99.X.X.7
    crypto map outside_map 1 set transform-set ESP-AES-128-SHA
    crypto map outside_map 1 set reverse-route
    crypto map outside_map interface outside
    crypto isakmp enable outside
    crypto isakmp policy 10
    authentication pre-share
    encryption aes
    hash sha
    group 2
    lifetime 28800
    vpn-addr-assign local reuse-delay 5
    telnet timeout 5
    ssh timeout 5
    console timeout 0
    dhcpd auto_config outside
    dhcpd address 172.16.5.100-172.16.5.130 inside
    dhcpd auto_config outside interface inside
    dhcpd enable inside
    threat-detection basic-threat
    threat-detection statistics access-list
    threat-detection statistics tcp-intercept rate-interval 30 burst-rate 400 average-rate 200
    webvpn
    tunnel-group 99.X.X.7 type ipsec-l2l
    tunnel-group 99.X.X.7 ipsec-attributes
    pre-shared-key XXXXX
    class-map inspection_default
    match default-inspection-traffic
    policy-map type inspect dns preset_dns_map
    parameters
    message-length maximum client auto
    message-length maximum 512
    policy-map global_policy
    class inspection_default
    inspect dns preset_dns_map
    inspect ftp
    inspect h323 h225
    inspect h323 ras
    inspect rsh
    inspect rtsp
    inspect esmtp
    inspect sqlnet
    inspect skinny
    inspect sunrpc
    inspect xdmcp
    inspect sip
    inspect netbios
    inspect tftp
    inspect ip-options
    service-policy global_policy global
    prompt hostname context
    no call-home reporting anonymous
    : end

    just out of curiosity, why do you have
    route outside 0.0.0.0 0.0.0.0 99.X.X.7 1
    You already set your default route through DHCP setroute under the interface. this could be the issue.
    If your VPN config is ok and you are seeing encaps/decaps, it is likely a routing issue.
    Does the remote device have the correct default gateway?
    May be a Natting issue if you have a one-way tunnel (usually send but no receive)...
    Patrick

  • 3750 as a router and a switch. sub-optimal routing problem

    Objective: To limit the traffic on Vlan8. We are seeing traces from K1 or T1 to 192.168.1.4 like this:
    1- 10.10.10.5
    2- 10.10.20.1
    3- 192.168.1.4
    then
    1- 10.10.10.4
    2- 10.10.30.1
    3- 192.168.1.4
    or
    1- 10.10.10.5
    2- 10.10.200.1
    3- 192.168.1.4
    this causes the packets to travers vlan8 once to get routed by P61B then switched back across to reach the next hop 20.1 or vice versa.
    How can we avoid this behavior?
    Study the attached drawing carefully. Vlan 8 has 4 routers on it and the 3750s have routes to the 4 networks above them. packets are not routed between the 3750's

    Hello Todd,
    Could set up a debug ip icmp on the router 192.168.1.4 and ping it from both T-1 and K-1, I think this problem would be more clear to everyone.
    If not mabybe you could provide the output of "show ip route" on the routes on this issue,at least on the routers/switch 192.168.1.2 , 192.168.1.3 and 10.10.10.4 and 10.10.10.5 and T-1, K-1.
    for routes like 192.168.1.4, 10.10.10.2-5 and 20.20.20.2-3
    Hope thats not to much info.
    Thanks,
    Vlad

  • [SOLVED] Routing problems with ssh server and openvpn client

    My current setup is an arch box behind my wireless router.  My wireless router is running scripts to update the dynamic dns for my internet connection and forwarding incoming requests to port 22 on the arch box.  Simple so far.
    Now I'd like to setup OpenVPN on the arch box to connect to a 3rd party vpn service but still listen for ssh connections.  This way I can have my arch box always connected to the vpn but be able to access it from anywhere.  I believe the problem is that openvpn sets up a default route to send all outgoing traffic out over the tunnel, but I don't know enough about routing to make this work.  I saw another solution in the forum was running virtualbox and I find that so inelegant.  I'm planning on eventually learning more about ip route and iptables but I was also hoping that a networking guru could help me get this set up quickly in the meantime.
    ip route while not connected to vpn
    default via 192.168.1.1 dev eth0 metric 202
    192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.11 metric 202
    ip route while connected to vpn
    0.0.0.0/1 via 10.120.62.9 dev tun0
    default via 192.168.1.1 dev eth0 metric 202
    10.120.62.1 via 10.120.62.9 dev tun0
    10.120.62.9 dev tun0 proto kernel scope link src 10.120.62.10
    23.29.126.102 via 192.168.1.1 dev eth0
    128.0.0.0/1 via 10.120.62.9 dev tun0
    192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.11 metric 202
    Last edited by ricka (2012-11-05 17:14:48)

    First, meop, thanks for your reply.  I did not use that method to solve the issue, but I'm going to do some more research into it (I'll speak to why I went another direction after the solution).
    My solution so far has come from this resource http://forum.linode.com/viewtopic.php?t=8737
    Since my server is behind a router, I do not have to worry about the public IP address changing and I was able to use the private IP in the route statements.  Therefore, in my case, the solution was these three lines:
    ip rule add from 192.168.1.11 table 128
    ip route add table 128 to 192.168.1.0/24 dev eth0
    ip route add table 128 default via 192.168.1.1
    Keep in mind, as the article states, that applies to all ports (not just ssh).  If you want to block other traffic, you need some extra iptables entries.
    This also solves my end goal: Being able to connect to this 3rd party VPN with a simple ssh redirect from my always connected server.  I can now ssh -D <port> <myhost>, set up chrome to use <port> as a proxy, and have everything redirecting over this VPN connection without any hassle.
    meop, this setup is connecting to a 3rd party VPN service and they provided the config scripts for the client.  I considered tinkering with that, but found this solution to work and I'm going to do some more reading about each solution to figure out which is the best overall.
    enovak, I grepped dmesg and did not see any entries about martian source.
    Now another question that comes to mind:  What if this server were actually NOT behind a firewall and it's public IP changed?  I think you'd somehow have to have a script to check to see if your Dynamic IP address changed and also have a route that only that script would use (send everything else out the VPN route).  Then, if your IP address changed, you'd have to change these routes around.  I'll leave that solution to someone else :-)

  • SRP527w Traffic stops routing when multiple PVC's are active

    Hi,
    I am currently experiencing two incredibly annoying bugs with the srp527w, if anyone could help me at all it would be much appreciated:
    I am using firmware version                 1.01.19 (004).
    Problem 1:
    I have my srp527w setup with the following:
    PVC0 - VPI = 0 VCI = 35, this is setup with RFC1483 bridge, the interface is then added to the one and only vlan I have active on this device.
    This interface is used for IGMP traffice for my providers IPTV service.
    I then have PVC1 VPI=8 VCI=35, setup as PPPoE and set as my default gateway for internet traffic.
    This setup works fine for a random amount of time, or until the device is rebooted, or until a change is made such as dhcp being turned on or off, which should not affect routes at all.
    PVC1 will stay connected but just stop routing internet traffic at all. It is definitely set as the default route for the vlan. The router is configured with 3 VPN endpoints, I can still access these remote sites, just not the internet. PVC0 / IGMP traffic still works fine.
    Problem 2:
    Even though the vocie ports are on the same VLAN as my VPN endpoints, they will not register to a sip server on the VPN endpoint - an ATA will register fine if connected to the ethernet port.
    Paul

    Hi Paul,
    Could you send me a copy of your configuration (http://192.168.15.1/admin/config.xml) please?  I'm wondering if there is some issue with the way that you are associating the PVCs with your VLAN.
    The second point is expected I'm afraid.  It is not possible to route traffic from the internal voice ports over an IPSec tunnel.
    Regards,
    Andy

  • Skype can't connect - most likely router problem, ...

    Lately I can't connect to Skype at home. I've tried a lot of different solutions but none of them work.
    The problem started a few months ago when I just couldn't sign into Skype (can't connect). At that time I had no change in any network settings on my computer nor my router. Interestingly enough, I could connect to Skype on Ubuntu (I have dualboot). Though even Ubuntu eventually failed to connect back then (just can't sign in) - still no changes in my network. I couldn't be bothered at the time with the problem so I just didn't use Skype.
    However after some time (some weeks or a month or two), when I tried to connect to Skype again, it worked (on Win 7 as well as Ubuntu). Again, no changes to my network have been done in the mean time (Skype might of been updated, but I doubt it was on both platforms at the same time).
    So Skype worked for a while until about a month ago, when the problem reoccurred. This time I said I'm going to get to the bottom of this so here is the situation:
    I can connect to Skype at work no problem (on my desktop as well as my Android phone)
    I can't connect to Skype at home (just won't sign in) on my desktop nor my phone
    I have tried:
    Reinstalling Skype with cleaning everything that Skype might have left behind
    Installing an (a bit) older version 6.9 (because even the latest 6.11 didn't work). Though these two attempts I've come to see are in vain once I figured out that I can't connect to Skype on my phone as well.
    Resetted my router a couple of times.
    Reset my router settings to default.
    Opened/forwarded Skype ports to my (local) IP. I even enabled DMZ to redirected all traffic to my desktop computer (although I'm not 100% sure that that worked as I imagine it should work).
    Tried some proxy settings in Skype (Connection options) I found on your forum.
    None of the above worked in any way...
    My router is a TP-Link TL-WR1043ND with (I think the latest) firmware version 3.13.13 Build 130428 Rel.58290n (hardware is v1).
    TLDR:
    I can't sign in to Skype at home. It works when I'm at work. I can connect to Skype on my phone if I'm at work (over WiFi) or if I'm on 3G, but not if I'm on my home WiFi. That said, no software firewall can be the problem here, but my router. However I have no more ideas as to what else I can try. This forum is my last hope for finding a solution.
    Please help.
    Solved!
    Go to Solution.

    I do not know the makeup of Skype's internal security policies when it comes to this as they are not too open about this. Most companies are not. These are the only reasons I believe a block would occur based off any company's security policy.
    1. A proactive measure - A blacklist of IPs is constantly obtained/updated to include anonymizer services that might harm the network.
    2. An active/counteractive measure -
    I. Someone uses an anonymizer to SPAM people on the Skype network:
    a. Users complain using the abuse option. Users get the IP Auto-banned.
    b. The company (Skype) receives the complaints or notices a trend and Manual/Auto bans the IP.
    II. Too many people (connections) sign on with the same IP (due to an exit relay/proxy). Due to this being very suspicious, (maybe even DDos-like behavior) the IP is Auto-banned.
    I tend to lean more towards the counteractive measure since I don't believe many proactive measures are needed to limit abuse. There is always at least one rotten apple that engages in illegal activity using anonymizers, proxies, etc. that ruin it for everybody. In reality I believe it is a combination/balance of the two. Not to be prejudice against anonymizers, just blacklists to protect the network from known attacks. For whatever reason once the threshold is met, the IP is banned.  If I had to guess how long it would be in intervals of 30 days (30, 60, 90, 120, etc.). The whole Internet is not going to banned so the security policies in effect can't be too strict. It's goal is probably just to limit the majority of bad behavior that causes problems for their customers.
    Skype is not the only service that reacts this way. Even ISPs will receive notices and in turn will send notices to their customer that since illegal activity (RIAA notices, etc.) is occurring due to a Tor exit relay or some other anonymizer, the ISP will terminate services with that customer if they don't cease (due to breach of contract).
    I don't know whether you can limit an exit relay so it can't be used to access Skype. It may be a lost cause. If I made the choice to run a similar service it would be with a whitelist of people I knew who wouldn't use it to perform illegal activity, just remain anonymous when online.
    You shouldn't have any issues running a non exit relay since in doing so your IP is not being broadcast all over the Internet like a calling card which an exit relay does. Changing your modem's MAC address is something you need to call your ISP for. However changing your router's MAC address generally does not require that. All that is required is a reboot of the modem, router, and possibly computer if you run into issues. You will probably continue to run into the same problem as long as you attempt to run an exit relay.
    Be aware that for every IP that get's banned on your ISP is another IP a person could get issued for 24 hours to a week + after it gets released. Some people then visit this community and complain how they can't connect when it worked not too long ago and how Skype "sucks". So sometimes things like this create a ripple effect for other customers.

  • Real-time traffic, static routes, ports, filters, EIGRP.

    I am trying to send realtime traffic to a host device using a specific port on that end device. The path between the two devices currently consists of two EIGRP gigabit hops.
    I will be adding a single hop 100Mb link between the originating router and the destination router. I want only the specific host to host realtime traffic to cross this 100Mb link, ie. no EIGRP traffic should cross it.
    Using this 100Mb link, if you set up a static route from the source router to the destination router then you can't control who uses that route ie 100Mb link. If you use EIGRP and do a route filter, you end up with another problem, EIGRP traffic crossing the link.
    Suggestions?

    Bruce
    If I understand your requirements correctly then the solution you are looking for is Policy Based Routing. PBR can alter (or over-ride) the routing decision that would be made in the routing table. You configure PBR with a route map. Frequently the route map uses a access list to identify the traffic to be treated differently. So you could create an access list that would identify the specific host to host traffic and then in the route map you can set the next hop to use the special link.
    In this solution you would not run any routing protocol over the special link. Only the Policy Routed traffic would use the link.
    HTH
    Rick

  • Snow not Bridging Properly or Routing Problem?

    Hi All, I have a network consisting of Snow and Netgear Base-stations both configured as Bridges (i.e., no NAT/DHCP) connecting back to a Netgear RP114 router out to a cable modem.
    The Snow defines a network called "vegetables" and the Netgear a network called "fastVegetables", operating on different, correctly spaced, channels.
    I can connect to either wireless network with my laptop and thence out to the internet via the router and cable modem - this all works fine.
    I also have a Cannon IP4000r wireless printer that is connected to the "vegetables" wireless network (Snow). If my laptop is connected to the same wireless network I can see the printer and print quite happily to it. I can also see (both ping and connect to web servers on) the Netgear router and the Netgear access point.
    Now the problem - if I connect my laptop to the other wireless network ("fastVegetables") operated by the Netgear access point I cannot see the printer at all - neither ping nor print nor access its config web server.
    I can ping the Snow and connect to it using the Airport Admin utility; the printer gets it ip address from the Netgear router using DHCP - so the router should know of its existence.
    So what I cannot figure out is whether the traffic for the printer isn't even reaching the Snow to be bridged to the "vegetables" wireless network segment; or whether it is reaching the Snow but for some reason isn't being bridged from the lan side to the wireless side?
    Has anyone experience of this or similar setup and whether the Snow has any Bridging problems?
    Regards...jeremy

    Great to hear. Please flag your last post as '''Solved Problem''' so
    that others will know what to do.
    Happy Computing.

Maybe you are looking for