165 reputation
5
bio website
location
age
visits member for 6 months
seen Mar 22 at 9:29
stats profile views 2

This is not about me, and nothing about computers or programming either, but check out the site of a man from a land down under who, going against the academic establishment, has come to what I believe are amazing insights into the history of the mega surface features of Our Planet Earth, adding significant and genuinely new facets to the old theory of Earth Expansion which, while discredited by consensus, will prevail when the current paradigm of Plate Tectonics collapses under its many conundrums: http://www.earthexpansion.blogspot.com/ - Don Findlay's Expanding Earth Blog


Mar
22
accepted How to make sense of an iptables chain configuration
Dec
17
comment How can I tell whether a network interface is physical (device) or virtual (alias)?
Thanks. Note wlan0 would have been present in the device list under /sys/class/net hat it been enabled when I copied the list. :) I have now added it above. I disagree with you on the number of devices, I think there are only two, LAN and WLAN. But that's a minor point … good answer, accepted, thank you!
Dec
17
awarded  Scholar
Dec
17
accepted How can I tell whether a network interface is physical (device) or virtual (alias)?
Dec
17
revised How can I tell whether a network interface is physical (device) or virtual (alias)?
added wlan0 device
Dec
14
comment How can I tell whether a network interface is physical (device) or virtual (alias)?
Thanks. I added similar output to my question. It is not as clear as the output you're showing here, with PCI bus or whatnot showing up there; although I don't really understand the output, I agree it looks like hardware identifiers. In the case of my output posted above, it's the presence of ag71xx that makes me think it's hardware, since it looks like a driver.
Dec
14
awarded  Editor
Dec
14
comment How can I tell whether a network interface is physical (device) or virtual (alias)?
@BatchyX, thanks, first time I hear ifconfig is deprecated. Anyway, this tiny router box doesn't have the ip command, and there's no space left. It uses the busybox binary, which has ifconfig (among others) aliased to it, but not ip. Will keep in mind that ip should be used, though. Thanks.
Dec
14
revised How can I tell whether a network interface is physical (device) or virtual (alias)?
more info
Dec
4
comment How can I tell whether a network interface is physical (device) or virtual (alias)?
@Nils, here you go: wiki.openwrt.org/toh/tp-link/tl-wr941nd - @Nathan, with just 4 MB of flash, the box is rather constrained, and lshw is not in the package list. A knowledgeable and determined guy might succeed in installing dev tools in tmpfs, but would it be worth while? I'm going to further my understanding of Linux networking by means of a standard PC. This is going to be easier. While I don't properly understand this router configuration, it does work fine. Thanks for your help.
Dec
4
comment how come has firebird-superserver stopped and how to prevent from happening again?
Glad to hear. And just cool how I was so wrong about a reboot most definitely not being necessary … :)
Dec
3
comment how come has firebird-superserver stopped and how to prevent from happening again?
Sorry to hear that. Good luck. By the way, I've found the Firebird Support List to be very helpful. Just in case the need should arise for recovery or whatnot. -- M. Ludwig :)
Dec
2
comment How can I tell whether a network interface is physical (device) or virtual (alias)?
@Nils, I don't have a clear grasp of the network configuration on my router device after I flashed OpenWrt onto it. I find it thoroughly confusing. Project docs and forum have provided some help, but not enough, and leaving basic questions unanswered. One of those questions is the one raised here. It now seems to me that my router has only one NIC when I was sure it had two. Clarifying details reduces confusion. That's why.
Dec
1
awarded  Commentator
Dec
1
comment Allow IP packet forwarding from LAN to modem via router
Well, ifconfig is how I'm trying to find out what's going on. :) Looks like there's a convention of naming virtual Interfaces like eth0.1. But it's just a convention, and it is definitely not adhered to on my box. It is not clear to me how to find out whether a Network Interface is physical or virtual. Strange how this is so non-obvious ...
Dec
1
asked How can I tell whether a network interface is physical (device) or virtual (alias)?
Dec
1
comment How to know if a network interface is tap, tun, bridge or physical?
Virtual devices may also have such a device symlink: ls -l /sys/class/net/lan1/device Shows /sys/class/net/lan1/device -> ../../../dsa.0 on a router running OpenWrt (embedded Linux). I found that physical Interfaces have an Interrupt entry in the output of ifconfig. It is strange that such a simple question about an Interface seems so hard to answer. Investigation continues ...
Nov
30
answered how come has firebird-superserver stopped and how to prevent from happening again?
Nov
30
comment Allow IP packet forwarding from LAN to modem via router
I've read up on VLANs and come to the conclusion that (a) my router does support them (via the kmod-8021q kernel module which I would have to install (hardly any space left on that tiny box), the vconfig utility being already present as part of the BusyBox binary), and (b) I do not need VLANs in my home network. VLANs seem to be a very useful configuration option when you need them, but I'm not sure how much they're related to my problems with Netfilter configuration. At least, now that I know about VLANs, I know that I don't need them.
Nov
30
comment Allow IP packet forwarding from LAN to modem via router
I do not seem to have VLANs on that router. No dotted interfaces. There is /proc/net/vlan/config, but it's just two lines, VLAN Dev name | VLAN ID and Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD. Looks unused. Wonder how VLANs would relate to those »zones« that OpenWrt defines (as Shorewall does). - br-lan: Yes, that seems to be bridged Ethernet and WiFi. - Yes, I can telnet to my modem from any computer in the same subnet. The problem here is not with the modem but with the router inbetween.