[CLOSED] Vs 22.03 keeps missing the gateway

Installing and Using OpenWrt
28
  • Why do you have metrics? (you only described one gateway to us via the ISP modem upstream, so I don't understand this)
  • Why is eth0.2 incorrectly configured for both LAN and WAN?
  • Why is radio0 incorrectly assigned to 2 interfaces?
  • What is wlan?

:spiral_notepad: These could be the issue. I'm curious, where are you getting these configs from?

(You have more networks specified than you noted - I understand you may not be that savyy, but likewise, we cannot guess why you're making such configurations unless you [clearly] explain. Hope this helps.)

Can you describe why you keep calling this an issue with a "missing gateway"?

Perhaps knowing that, we will be able to assist you better.

I'll try again, please try to follow the steps and provide the answers - we need to know in order to help you. Please try to focus:

You responded:

Please run tcpdump with -n and provide this answer - we need to know this IP in order to troubleshoot the tcpdump output. Thanks.

1 Like
29

I have already answered all of this. Because I don't know what I'm doing when it comes to configuring the network file. You are asking a lot of questions I cannot answer. I'm just looking on the net for ideas, configurations to try.

I'm not sure what you keep asking for, we need to know this IP, what IP?
The enagent was just something I called the device, a random name.

but likewise, we cannot guess why you're making such configurations unless you [clearly] explain.

That's why I said maybe it's time to delete this question. It keeps getting more and more complicated as we keep discussing. I just need to fix my network/wireless files. That's what seems to be the issue.

I keep calling it a missing gateway only because 'ICMP time exceeded in-transit' messages seem to indicate that one or both of the upstream devices become unreachable for a few seconds at a time.

Who are these 2 hosts?
What two hosts? I've shared all there is. The enagent is not a host, it's the router itself and just a hostname I threw on it some time back.

The -n option doesn't provide anything more than I've shared. What is it you expect to show? I can just give you that information.

I'm pretty focused but we seem to be all over the place. I think all I need to do is to fix the network and wireless files and you're asking a lot of things I cannot answer or have but you don't take them as valid.
I'm just playing with all this stuff and trying to learn while doing so :).

30

In terms of the pings, it's possible that this ICMP time exceeded message is a result of the routing or bridging configuration on my device.

The TTL value of a packet is decremented by each hop it traverses, and if it reaches zero, it is discarded, and the router generates an ICMP time exceeded message back to the source.

Not sure if this is my case but I'll try using a custom ping for a while and see what happens.

31

I was trying to help with that issue, but it seems you may not understand the questions.

Also, it seems you may not understand the tcpdump output, or why I'm asking you to run the command with the argument -n, as to see the IP for the device named "engaget". Then we'd know what IP received the exceeded in transit message you displayed.

I hope the best for your setup and hope you find out why your issue occurs.

This is what I was attempting to help you with, but you seem you might not understand the basis of the inquires asked - whose answers are needed to help you.

It should show the IP address of "engaget" instead of the name. Do you have that information avaliable?

32

I of course understand your questions and am answering them as best as I can.
Here is the output with -n. Rather than the name it's showing the IP but I'm not sure why this has been so important since I've provided that.

# tcpdump -n host 192.168.1.1 or host 192.168.0.1 or host 4.2.2.2
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
21:16:09.833089 ARP, Reply 192.168.1.1 xx-xx xx:xx:xx:xx:xx:xx, length 46
21:16:30.653529 IP 192.168.1.1 > 192.168.1.5: ICMP time exceeded in-transit, length 46
21:16:30.653712 IP 192.168.1.1 > 192.168.1.5: ICMP time exceeded in-transit, length 46
21:16:30.654066 IP 192.168.1.1 > 192.168.1.5: ICMP time exceeded in-transit, length 46
21:16:30.659615 IP 192.168.0.1 > 192.168.1.5: ICMP time exceeded in-transit, length 46
21:16:30.660573 IP 192.168.0.1 > 192.168.1.5: ICMP time exceeded in-transit, length 46
21:16:30.661170 IP 192.168.0.1 > 192.168.1.5: ICMP time exceeded in-transit, length 46

This is what I was attempting to help you with, but you seem you might not understand the
basis of the inquires asked - whose answers are needed to help you.

It simply doesn't always come across well in text. I am trying to provide what is needed.

33

This was helpful!

You never identified 192.168.1.5 as engaget and that it is the OpenWrt (you merely said you weren't sure and thay you'd disable something), my apologies if I missed that.

No worries.

Unfortunately this time you ran on a different interface, so I'll refrence the other one.

:bulb: think I found your problem!

You ran the first one and got responses from 192.168.0.1 :x: and 192.168.1.1 :white_check_mark:

Engaget's SRC IP is 192.168.1.5

The issue is: when running on br-lan, you shouldn't have seen packets from 192.168.0.1. It should be on another network/interface/VLAN.

Again I misunderstood your technical savvy, the proper wording is "you need to fix this".

You'll need to fix this as well.

One of these incorrect confogs are likely causing some routing loop.

I noticed again, you didn't take opportunity to answer the inquiries. I apologize if my questions are not coming across well in text too.

34

I also noticed; and you're not clearly answering a very important question - then it appears again.

Since we already noted that this syntax is invalid - where is your configuration syntax coming from?

Particularly, where are you being told to add the radio PHY into the network config?

35

Hi, I've not had the chance to work on this and I'm out of town for a couple of days, leaving shortly.
I absolutely will get back to this as soon as I return.

Thank you very much for your help.

36

Back and this is interesting.

The first network file is constantly showing the problem;

19:14:05.959620 IP 192.168.1.1 > 192.168.1.130: ICMP time exceeded in-transit, length 46
19:14:05.959802 IP 192.168.1.1 > 192.168.1.130: ICMP time exceeded in-transit, length 46
19:14:05.960158 IP 192.168.1.1 > 192.168.1.130: ICMP time exceeded in-transit, length 46
19:14:05.965875 IP 192.168.0.1 > 192.168.1.130: ICMP time exceeded in-transit, length 46
19:14:05.966827 IP 192.168.0.1 > 192.168.1.130: ICMP time exceeded in-transit, length 46
19:14:05.967299 IP 192.168.0.1 > 192.168.1.130: ICMP time exceeded in-transit, length 46

$ cat /etc/config/network

config interface 'loopback'
    option device 'lo'
    option proto 'static'
    option ipaddr '127.0.0.1'
    option netmask '255.0.0.0'

config globals 'globals'
    option ula_prefix 'fd21:c667:49ef::/48'

config device
    option name 'br-lan'
    option type 'bridge'
    list ports 'eth0.1'
    list ports 'eth0.2'

config interface 'lan'
    option device 'br-lan'
    option proto 'dhcp'
    option ip6assign '60'
    option metric '20'

config interface 'wan'
    option device 'eth0.2'
    option proto 'dhcp'
    option metric '10'

config interface 'wwan'
    option device 'radio0'
    option metric '30'
    option proto 'none'

config interface 'wlan'
    option device 'radio0'
    option metric '40'
    option proto 'none'

However, this one, is not showing them at all since I've changed it slightly for testing. This is how it looks now.

# cat /etc/config/network

config interface 'loopback'
    option device 'lo'
    option proto 'static'
    option ipaddr '127.0.0.1'
    option netmask '255.0.0.0'

config device
    option name 'br-lan'
    option type 'bridge'
    list ports 'eth0.1'
    list ports 'eth0.2'

config interface 'lan'
    option device 'br-lan'
    option proto 'dhcp'
    option ip6assign '60'
    option ifname 'br-lan wlan0'

config interface 'wan'
    option device 'eth0.2'
    option proto 'dhcp'
    option metric '10'
    option ifname 'wlan0'

config interface 'wwan'
    option device 'radio0'
    option proto 'none'
    option metric '30'

config interface 'wlan'
    option device 'radio0'
    option proto 'none'
    option metric '40'

While I understand that the files may not be correct, it is interesting that the slight differences are showing a very different result.

Both routers are connected to the same switch.

37

Not one single 'time exceeded' using the second version.

1 Like
38

Since you're not explaining why you're making these configs or why you're creating invalid ones (perhaps you're not aware that we've been telling you that or the wording of my questions is not conveying the confusion about them) - saying that you're not receiving Time Exceeded messages doesn't really edify the community. You also failed to say where you're getting this invalid syntax, especially to specify radio PHYs in the network config file.

Since it was also asked why you have metric settings, I surmise you know and don't wish to share?

Also, it's still not clear why you incorrectly added eth0.2 to both LAN and WAN.

Nonetheless, I'm glad you got it working.

If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.

39

I have explained all of what you just asked. I'm not sure why you are writing as if I'm trying to be less than helpful or appreciative if the help I'm getting.

It's working but as we said above, it's not the correct method of the files. This is what you told me.

I've told you over and over, I got this stuff from posts, articles, all kind of stuff I found on the net because I do not know how to build this network or wireless file.

I also got the files from the default build and thought I was starting to go in the correct direction but apparently I'm not.

What would you like me to do since I thought I've been providing and testing everything as you've asked me to but it seems I'm missing something.

40

OK, well no biggie. Feel free to post your URLs as reference - so others can see them too. I know it would likely end my confusion.

Again, glad it's working - that's the important part! :+1:

Just to be sure you have it, here's a link to docs in the official Wiki:

That cannot be the case, unless you're not using official OpenWrt firmware.

I know that learning can be frustrating - but likewise, we cannot guess you read an unofficial website and decide to make a config - so we're unsure. I indeed read the description of your use case - someone provided a link to the official Wiki for Dumb AP, but the configs you added aren't listed there, don't need metrics, etc.

If it's working, feel free to mark the topic as solved. :grinning:

EDIT: Just to be clear, you didn't test/correct anything I asked/suggested you fix - I noted the fixes in 2 posts.

Post No. 1 with questions/fix suggestions

Post No. 2 with questions/fix suggestions - where I actually said " 'you need to fix this' "

41

BTW - this is why it was advised to install/use the LuCI web GUI (i.e. so you don't have to guess syntax).

Your decision not to use LuCI implies you know/understand correct OpenWrt syntax, but then you subsequently note here that you do not.

That's somewhat confusing.

1 Like
42

I'm sorry, I am overwhelmed with things in life while trying to understand this at the same time. I'll review again and try to provide the things I didn't provide.

43

I do not use the gui so there is no point in installing it. I'd like to better understand what I'm doing from the command line. There's nothing confusing. I said I'm not familiar with the wording (I called it syntax) of the network and wireless files since I've never had to touch those.

There aren't any specific urls to share, it's just stuff I found over the Internet and in the forums that I was trying to learn from, obviously all wrong for this version of openwrt. That's the problem with so much information on the net and not doing something like this on a regular basis.

This is the original file I got from the downloaded build off of the openwrt site.


config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd17:78ff:5e34::/48'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0.1'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config interface 'wan'
        option device 'eth0.2'
        option proto 'dhcp'

config interface 'wan6'
        option device 'eth0.2'
        option proto 'dhcpv6'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '1 6t'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '0 6t'

And this one is the one I'm running right now.


config interface 'loopback'
    option device 'lo'
    option proto 'static'
    option ipaddr '127.0.0.1'
    option netmask '255.0.0.0'

config device
    option name 'br-lan'
    option type 'bridge'
    list ports 'eth0.1'
    list ports 'eth0.2'

config interface 'lan'
    option device 'br-lan'
    option proto 'dhcp'
    option ip6assign '60'
    option ifname 'br-lan wlan0'

config interface 'wan'
    option device 'eth0.2'
    option proto 'dhcp'
    option metric '10'
    option ifname 'wlan0'

config interface 'wwan'
    option device 'radio0'
    option proto 'none'
    option metric '30'

config interface 'wlan'
    option device 'radio0'
    option proto 'none'
    option metric '40'

Why do you have metrics?

I used metrics because I wanted the wireless to become the default route/gateway if I activated it.

Why is eth0.2 incorrectly configured for both LAN and WAN?

Lack of knowledge in this which is why I posted.
As mentioned, what I shared are where I left off, one of many tries to get this right.

That cannot be the case, unless you're not using official OpenWrt firmware.

As I mentioned before, I was testing and lost track of things and since this configuration is not something I know much about, ended up with a mess. Comparing the two, I can see some differences of course.

I'm not sure what to do about this since I got it from another device. I'm not sure this is something you can copy from one device to another.

config globals 'globals'
        option ula_prefix 'fd17:78ff:5e34::/48'

Why is radio0 incorrectly assigned to 2 interfaces?
What is wlan?

Again, just stuff I found while searching, things I was trying.

This is the original wireless file.


config wifi-device 'radio0'
        option type 'mac80211'
        option path 'platform/10300000.wmac'
        option channel '1'
        option band '2g'
        option htmode 'HT20'
        option disabled '1'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'OpenWrt'
        option encryption 'none'

This post keeps getting longer and longer and I'm not sure what I've missed at this point that I should have provided. Maybe I need to find someone like a freelancer to help me since I obviously have gotten confused over time from all the mistakes I made. I would like to delete this question as useless to anyone that finds it.

44

Cool, if you insist.

What about the original file in your router by default?

I would have adviseed you start from there.

Yes you can. If you're not clear why, there's a Wikipedia entry on ULA.

BTW, you answered but your responses didn't make clear if you intended to fix it.

Ummmm, OK. Without details it's hard to suggest/know - but that makes sense. :+1:

Sure. Just mark your post as solved and it will close in 10 days.

45

I don't understand the passive aggressive manner but I give up. I guess I'll have to keep searching the Internet until I can understand and figure this out.

46

I apologize, I wasn't attempting to be.

I was just suggesting to use the default files (since you said the files came form elsewhere and not the default files), and telling you how to close the topic. I'm not even exactly sure which statement you took as passive aggressive, but there was no intention.

Lastly, I again suggest you to use the WIki - and I wish you the best.

I'll just mark the topic - so it'll close, in the future, it's common we ask users do this themselves (See How to mark a topic as [Solved] for a short how-to). Perhaps that's what you took as passive aggressive - again apologies.

1 Like
47

I suppose I could be wrong but as the person that is struggling to get this working, it just feels like you're being very nice and at the same time, constantly telling me what I'm doing wrong as I'm actually trying to be responsive. However, I seem to be missing questions and other points here and there which would frustrate someone helping.

It seems this post will go on and on and I just have to figure this out on my own, without asking for help or hire someone that will help me. You keep asking me to clarify what I'm up to which I did early on or in the first thread. I don't know, I've lost track at this point.

The main clue you've given me is that my files were wrong. The network file had interfaces in the wrong place etc and had wireless interfaces which should be in the wireless file.

I've updated the two files and think I'm on the right track now so thank you for that.