-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Confused by the new network configuration (GBPC1 & 5.1.4) #9
Comments
Oh, and could we have an example of |
Yes, that is all normal. I have
in my interfaces file. A "kernel that supports swconfig" is a 4.4 or maybe 4.8 kernel with openWRT patches that provide internal switch support as developed by ralink. Newer kernels has DSA (Distributed Switch Architecture) which is more transparent and gives different names to things. Now that we have working DSA support, we should move away from swconfig. |
Ok. Thanks for the clarification. This could worth a note in the README. |
Wait... all seemed clear and all. But when I try to configure my network with:
I think I miss something to bring eth0 up, but I am not sure how to do so. |
Ok, for some reason eth0 is not activated before ethblue, which causes Edit: if I manually use "ifconfig eth0 up" then "ifconfig ethblue up", things seem to work. But I cannot get ifup to work. |
The initramfs should be setting eth0 "up" - there should be no need for you to do anything to eth0.
suggest that the address, or maybe a route, is already in use. |
1/ Right after booting:
Then:
BTW, should I be concerned with two ethbl* interfaces having the same MAC address ? |
Adding
I am wondering if all this could be related to #10. |
I just tried a new firmware built using this repository and your version 5.1.4 of linux for the GPC1 and the network is broken.
Using the serial console,
ip link s
gives me this:As I did not follow every episodes of the story about the support of the network switch, I am a bit confused:
swconfig
: What is a "kernel that supports swconfig" ? Should I try to build one ? How ? How will it affect the name of the network interfaces ?Thanks for your help.
The text was updated successfully, but these errors were encountered: